Description

Everytime I reload the server, there are errors printed in the console. Updated from 5.3.61 to 5.3.64, error is still there.

Reproduction steps

1. Start the server with new LuckPerms installation
2. Use the /reload Command
3. Error in console

Expected behaviour

I expected no error and my prefix assigning system using bukkit permissions assignes the default prefix to me. Just when I rejoin, my plugin assigns the right prefix. I made sure that my plugin is loading after LuckPerms. After I replaced LuckPerms with PEX, reload worked with the right prefix assignment.

Environment details

• Server type/version: ExampleSpigot running version CraftBukkit version git-Spigot-db6de12-18fbb24 (MC: 1.8.8)???`
• LuckPerms version: LuckPerms v5.3.64

console log
https://gist.github.com/justtoin/9f66ca7bf0fe1bddfb25138b5aaa25aa

Any other relevant details

Solution: don't use /reload

It would be annoying for plugin development if I would have to restart the whole server every time I changed something in the code.

https://madelinemiller.dev/blog/problem-with-reload/

Thx. But if this is deliberately ignored, there could be a console message that says that luckperms is not compatible with /reload on reload.

Thx. But if this is deliberately ignored, there could be a console message that says that luckperms is not compatible with /reload on reload.

Not only LuckPerms but a plethora of plugins break/error out when reloading (I personally have experienced issues with WorldEdit, WorldGuard, Quests, McMMO, GriefPrevention, GriefDefender, EssentialsX, Citizens2, and a long list of etceteras I barely even remember), surprisingly enough even the server itself in the long run will show erroring behavior. While in theory the way Bukkit does it should work, it's known to be a fundamentally broken mechanism, the JVM is simply not designed for hot-swapping.

[19:25:45 INFO]: CONSOLE: Are you sure you wish to reload your server? Doing so may cause bugs and memory leaks. It is recommended to restart instead of using /reload. To confirm, please type /reload confirm
> reload confirm
[19:25:48 INFO]: CONSOLE: Please note that this command is not supported and may cause issues when using some plugins.
[19:25:48 INFO]: CONSOLE: If you encounter any issues please use the /stop command to restart your server.
[19:25:48 INFO]: Server Ping Player Sample Count: 12
[19:25:48 INFO]: Using 4 threads for Netty based IO
[19:25:48 INFO]: Debug logging is disabled
[19:25:48 INFO]: [LuckPerms] Disabling LuckPerms v5.3.60
[19:25:48 INFO]: [LuckPerms] Starting shutdown process...
[19:25:48 INFO]: [LuckPerms] Closing storage...
[19:25:48 INFO]: [LuckPerms] Goodbye!
[19:25:48 INFO]: Reloading ResourceManager: Default, bukkit
[19:25:48 INFO]: Loaded 7 recipes
[19:25:48 INFO]: [LuckPerms] Loading LuckPerms v5.3.60
[19:25:48 INFO]: Server permissions file permissions.yml is empty, ignoring it
[19:25:48 INFO]: [LuckPerms] Enabling LuckPerms v5.3.60
[19:25:48 INFO]:         __
[19:25:48 INFO]:   |    |__)   LuckPerms v5.3.60
[19:25:48 INFO]:   |___ |      Running on Bukkit - Paper
[19:25:48 INFO]:
[19:25:48 INFO]: [LuckPerms] Loading configuration...
[19:25:48 INFO]: [LuckPerms] Loading storage provider... [YAML]
[19:25:48 INFO]: [LuckPerms] Loading internal permission managers...
[19:25:48 INFO]: [LuckPerms] Performing initial data load...
[19:25:48 INFO]: [LuckPerms] Successfully enabled. (took 183ms)
[19:25:48 INFO]: CONSOLE: Reload complete.
[19:25:48 INFO]: Timings Reset

I can't reproduce - perhaps another plugin is interferring by shading the LuckPerms API classes incorrectly.