Let's be honest, Bukkit's reload command is based on a flawed idea which often ends up causing more problems than benefits. It's to the point where forks like Spigot and Paper have added messages warning users against the use of the command, telling them to rather restart the server. So, what if the reload command was replaced entirely by a better system?
Inspired by the SpongePowered project, BetterReload swaps Bukkit's attempt at literally reloading all plugins to an event that is passed along to plugins instead. Upon issuing the /reload command with BetterReload installed, plugins that depend on BetterReload can receive an event that leaves the reloading process up to the plugins.
As of update 1.4.0, the plugin also includes a configurable system allowing any plugin to be supported via the external section of the config.yml file. Please read more about this here. Ideally plugins should support the event, but this ensures universal support.
/reload command and accessible through /BetterReload./BetterReload in legacy versions, on both commands in modern)./bukkit:reload.BlockCommandSenders (typically command blocks) cannot use the /reload and must rather use /BetterReload.For information on how to use BetterReload's commands, please check the Command wiki.
For information on how to configure BetterReload, please check the Config wiki.
For information on how to support the ReloadEvent, please check the ReloadEvent Support wiki.
For information on how to support the ReloadManager, please check the ReloadManager Support wiki.
For a list of known supported plugins, please check the Supported Plugins wiki.
For general support, please join my Discord server.
For issues with the project, please open an issue in the issues tab.
A plugin which overrides Bukkit's default reload command, switching to something more like Sponge's