Setup LuckPerms plugin for Minecraft Server

minecraft_server_luckperms.md

#2 | LuckPerms plugin setup for Minecraft Server

📚 Index

1. minecraft_server_crossplay.md

2. ➡ minecraft_server_luckperms.md

3. minecraft_server_authme.md

4. minecraft_server_easycommandblocker.md

---

Using PaperMC as backend server (version 1.14.4) and Velocity as proxy with "modern" forwarding.

NOTE: Permissions between proxy and backend are independent. If you want to set permissions to proxy commands like /linkaccount from Floodgate, LuckPerms must be installed on proxy too.

Config

• 🔀 /velocity/plugins/luckperms/config.yml:

  server: global                      # Share context with backend.
  
  allow-invalid-usernames: true       # Enable if using GeyserMC/Floodgate.

• 📃 /paper/plugins/luckperms/config.yml:

  server: global                      # Share context with proxy.
  
  enable-ops: false                   # Disable vanilla OP management.
  auto-op: false                      # Disable vanilla OP management.
  commands-allow-op: false            # Disable LuckPerms for OPs.
  
  allow-invalid-usernames: true       # Enable if using GeyserMC/Floodgate.

TIP: You may want to share permissions settings between proxy and backend. See this.

• Permissions: Commands that can be enabled or disabled.
  Syntax: plugin.command.[...]

  • All commands: *

  • All Minecraft commands: minecraft.*

  • All Bukkit commands: bukkit.*

  • Help command from Minecraft: minecraft.command.help

If you want to manage permissions of backend server commands like /ban, you must install LuckPerms on backend.

If you want to manage permissions of proxy commands like /linkaccount (from Floodgate), you must install LuckPerms on proxy.

• Groups: Collection of permissions. Assigned to players. All players start with the "default" group.
  Example: "default", "moderator", "operator", "owner", etc.

  • Parent: Group from whom inherits all permissions.
    Example: "operator" with parent "moderator" moderator → operator
    (Group "operator" will have all permissions from "moderator" too.)

• Tracks: Collection of groups ordered in a hierarchical way.

  • Groups must be parented with previous lower level permission.
    Example: "default" → "moderator" → "operator" → "owner"

Common commands

• Main: /lp for server, /lpv for proxy

• Web editor: /lp editor

• Command tree: /lp tree

• Verbose report record: /lp verbose record /lp verbose paste

  • Verbose report live: /lp verbose on !internal/internal/commandblock & !internal/internal/console & !internal/console

  • Verbose report for player: /lp verbose on <player>

• Promote/demote user along track: /lp user <player> {promote|demote}

  • If player is in group with more than one track: /lp user <player> {promote|demote} <track>

• Assign group to player: /lp user <player> parent set <group>

Permissions

📃 Vanilla-like permissions (backend server)

• Groups: default - operator

• Track: main ( default → operator )

default		operator
weight.100	✔️	weight.200	✔️
*	❌	group.default	✔️
minecraft.command.help	✔️	minecraft.*	✔️
minecraft.command.list	✔️	minecraft.command.save-all	❌
minecraft.command.me	✔️	minecraft.command.save-off	❌
minecraft.command.msg	✔️	minecraft.command.save-on	❌
minecraft.command.teammsg	✔️	minecraft.command.stop	❌
minecraft.command.trigger	✔️

"Weight" in simple, defines group priority. Read this.

With this setup, available commands will "emulate" vanilla commands. ALL plugins commands will be disabled.

To give OP, must promote to operator group. They will not have access to level 4 commands (e.g. /stop).

You can compact permissions with shorthands, for example default group can be compacted to:
minecraft.command.{help,list,me,msg,teammsg,trigger}

🔀 Vanilla-like permissions (proxy server)

• Groups: default

default
*	❌
floodgate.command.linkaccount	✔️
floodgate.command.unlinkaccount	✔️
geyser.command.advancements	✔️
geyser.command.offhand	✔️

All proxy commands will be disabled except Floodgate linking commands and Geyser utility and informational commands.

LuckPerms in-game permissions

• Groups: operator

operator
luckperms.user.promote	✔️
luckperms.user.demote	✔️
luckperms.user.info	✔️
luckperms.user.permission.info	✔️
luckperms.group.listmembers	✔️
luckperms.group.info	✔️
luckperms.group.permission.info	✔️

Append to current permissions.

With this setup you will be able to promote/demote players in-game and view some information about their permissions but every permission management is done in the console. Change permissions if you dont want that.

Extras

Promote/demote alias

• 📃 /paper/commands.yml:

  aliases:
    promote:
    - lp user $$1 promote main
    demote:
    - lp user $$1 demote main

Set shared database as storage method

Must do this if want to share permissions between proxy and backend.

TIP: You can use Supabase to host a free PostgreSQL database.

First export data with /lp export <filename>.

• 🔀 /velocity/plugins/luckperms/config.yml:

  storage-method: postgresql      # Select database.
  data:
    address: '<address>:5432'
    database: postgres
    username: postgres
    password: '<password>'
  
  messaging-service: pluginmsg    # Messaging system between proxy and backend. Must match.

• 📃 /paper/plugins/luckperms/config.yml:

  storage-method: postgresql      # Select database.
  data:
    address: '<address>:5432'
    database: postgres
    username: postgres
    password: '<password>'
  
  messaging-service: pluginmsg    # Messaging system between proxy and backend. Must match.

Then import data with /lp export <filename>.

To force synchronization between proxy and backend use /lp networksync.

⬆ Go to top