Update LuckPerms with the file for the platform the plugin is actually running on. A Velocity download does not belong on a Paper server. Back up the permission data and configuration first, and after the update, check with a normal player account whether groups and permissions still behave the same.
Determine the Platform and Storage Location
First, note where LuckPerms is installed: on the Minecraft server, the proxy, or on multiple components. Check the launched platform and version in the log. Do not rely only on the filename of a JAR that was uploaded at some point.
Next, check the configured storage for permissions. With an external database, the authoritative data is not necessarily in the plugin folder. A plain file backup of that folder may therefore be incomplete. Treat credentials from the configuration confidentially and do not include them in public error reports.
Backup Before Replacing
Back up the existing plugin file, the configuration, and the permission data store that is actually being used. Use a suitable export or database backup process for the data and check whether you can read the backup again. Note the time and which servers or proxies use the same data store.
For a small test, documented examples are enough: a normal player without special permissions, a member of a named group, and an account with a specific extra permission. Note the expected behavior. Do not grant global wildcard permissions or broad OP permissions for the test; that would hide permission errors.
Update During a Maintenance Window
- Choose the download for your actual platform from the official LuckPerms page.
- Check the requirements and notes listed there for moving from your current version.
- Shut down the affected server or proxy component cleanly.
- Replace the plugin file; keep the configuration and data storage as they are unless the specific update instructions require a migration.
- Start the component and check the log for loading and storage errors.
- Test the permission cases you documented earlier.
If you use multiple components, update them in a controlled way and document their version states. Do not derive a blanket upgrade instruction for all Minecraft servers from a new proxy build.
Check the Result
Do not test only with your administrator account. Check with a regular player whether allowed commands still work and forbidden actions are still rejected. If you use different permissions per server or world, repeat the test in exactly those contexts.
A successful startup alone is not enough: the server may be reachable while a database connection or permission rule behaves differently than expected. Note the platform, plugin version, test result, and, if applicable, the first relevant error message.
Safe Rollback
If permissions behave unexpectedly, stop making further administrative changes and first check the platform file and the storage connection. Use the backed-up data for a controlled restore test. Do not blindly restore an older database state if other servers have since written correct changes to the same data store.
FAQ
Is the most recently published file always the right one? No. The platform, requirements, and specific release notes have to match.
Is the plugin folder enough as a backup? Only if it also fully contains the data store that is actually being used. Check the storage connection.
Do I need to recreate permissions after every update? A regular update is not a reason to proactively rebuild your groups. Check the data store and error messages first.