The reload command in bukkit is diabolical, and should be removed. I've stated this many times in private before, but I'm often surprised by the number of people who are unaware of the problems with reloading. Memory Leaks: To understand why the reload command is terrible, you have to understand how it works. /reload disables all active plugins, and then, creates a new instance of every plugin in the plugins folder. It does not reactivate the old, disabled plugins. It creates a new copy. Due to the way Java works, and how Bukkit implements it's classloaders, this causes a memory leak. This is easy to confirm with most java profilers. The memory leak is not super significant (I'd guess at most, 5mb per /reload), but it does exist. Unfortunately, Java's eccentricities make it pretty much impossible to fix this memory leak. The effects of the leak can be viewed by my profiling some months back. Nothing has changed with plugin loading since these screenshots were taken. Server running BukkitContrib without any reloads. Server running BukkitContrib 4 reloads later. (Plugins loaded 5 times total, 4 reloads + 1 startup) All of the classes and any static variables remain in memory. Poor Plugin Design: Memory leaks are not the worst part about the reload command. Many, MANY plugins handle reloads poorly, or not at all. I'm certain most server admins are painfully aware that when they use /reload, the console will spit out at least one error, usually more. Exceptions are extremely common with /reload. And before you begin to berate plugin developers for simple mistakes, know that it is often extremely difficult to handle reload situations perfectly, especially the more complex the plugin. The most complex case I am aware of is Spout, where we have literally, thousands of lines of code simply to handle the /reload command. And Spout still doesn't handle reloads perfectly. Plugins that use multiple threads to achieve their tasks (usually plugins using some form of SQL, or persistent storage....) will also fail to end their threads after the plugin shuts down. This means your server could be wasting CPU cycles for extra threads that are not needed or used. Lag, Lag, Lag: Assuming that your server has only selected the highest tier plugins, of exceeding quality that handle reload flawlessly, and has gigabytes of extra memory to handle any leaks from bukkit, reload will still lag for several seconds after you issue the command. It is not uncommon for players to be kicked for fly hacking, moving to quickly, or just to read time out from lag. You might as well have used the 15 seconds it takes to RESTART the server instead of reloading it. There are several plugins made specifically to offer a way to safely RESTART your server instead of reloading it, and I encourage admins to use them: http://forums.bukkit.org/threads/ad...w-v0-3_2-full-server-restarts-818-1060.20039/ http://forums.bukkit.org/threads/ad...-automatic-rebooting-and-commands-1000.24652/ http://forums.bukkit.org/threads/ad...t-down-at-the-same-time-every-day-1248.26101/ http://forums.bukkit.org/threads/ad...detection-auto-saves-remote-console-1317.674/ I'm personally inclined to simply block the reload command from any of my plugins, but I expect that would make admins unhappy. So instead, I'm trying to raise awareness of why the command is bad, what can happen when you use it, and alternatives for it.