Loaded plugins arent "loaded" about plugman HOT 7 OPEN

So what is the difference between /plugin disable and /plugin unload

from plugman.

The server is not aware of the existence of an unloaded plugin -- it has no idea it's even real. The server is aware of disabled plugins, it just ignores them.

For example, plugins that attempt to load at server startup but fail will be disabled by the server. They're still loaded, but the server does not attempt to use them.

If a plugin is not loaded, the server doesn't even touch it's .jar file or named folder.

from plugman.

Answer to the second question: /plugman unload is not meant to delete the jar from the server, only unload it. The plugin will be loaded again next time the server is started.

What plugin are you trying to load? Some plugins don't support runtime loading and should only be loaded during server-startup. Perhaps you can provide us with a complete log file?

from plugman.

Does /plugman disable stop it loading on next restart?

from plugman.

No, /plugman disable does not stop the plugin from loading when the server is started, it simple disables the plugin during server runtime. This is different from /plugman unload which both disables and then unloads the plugin. When the plugin is disabled, it is still loaded on the server, but the server just doesn't let it do anything.

from plugman.

So /plugman unload stops the server enabling it on next restart? Different from what the first guy said. Also what about plugman load not having commands for a plugin despite it being installed

from plugman.

/plugman unload both disables and unloads the plugin from the server while it is running. the command does not stop the server from reloading the file the next time it starts. this plugin has no mechanism in place to provide that kind of functionality, all loads/unloads/enables/disables happen during runtime and will not persist across server restarts.

as for plugins not having commands after being loaded using /plugman load, I don't know the cause. I suspect the reason is that your plugin is not being loaded correctly and the commands aren't being registered. however, I cannot confirm this without a specific log file from the server.

from plugman.