Advanced LuckPerms: Permissions, Groups, and Multi-Server MySQL Sync
Master LuckPerms web editor, tier groups, and sync ranks instantaneously across nodes via MySQL.
Verified against
- LuckPerms
- v5
- Engine
- Paper / Purpur / Velocity
- Last checked
- 2026-09-13
Before you start
- A Paper, Purpur or Velocity based server
- Console access to run commands
- For MySQL sync: a MySQL/MariaDB server reachable from the node
On This Page
All Guides
LuckPerms is the industry gold standard for permission management. It works locally via H2 or scales globally using MySQL for real-time rank synchronization.
Install LuckPerms
Downloads LuckPerms from Modrinth to your server. Database wiring is configured separately using the steps in this guide.
- A compatible LuckPerms build lands in the plugins folder
- On restart it starts with the default file-based storage
The server must be restarted for this change to take effect.
If you have a Clodo service you can apply these steps without touching a terminal. You always see the diff before anything is written.
1. Configuring Ranks via Web Editor#
Instead of writing tedious commands in console, generate an interactive visual session via `/lp editor`.
/lp editor
# Olusan baglantiya tiklayin, duzenlemenizi yapip sag ustten 'Save' butonuna basin
# Ardindan konsola donup olusan /lp applyedits <token> komutunu calistirinHow to Implement This?
Clodo Control Panel Quick Method
Ready-made credentials in the panelThere is no wizard that binds LuckPerms to your database. The database is a separate Managed Database plan; you take its credentials from the panel and write them into LuckPerms' config.yml yourself.
Step-by-step Execution:
- 1Open a MariaDB plan from the Managed Database category.
- 2Copy the credentials from the 'Database' card on your Minecraft service detail page.
- 3Install LuckPerms from the 'Plugins & Mods' tab, then set storage-method to MySQL in plugins/LuckPerms/config.yml and fill in the details.
- 4Enter the same details on every server in the network; sync only happens when they all write to the same database.
Was this guide helpful?
Feedback goes straight to the team that maintains this guide.

