I never realized that schedulers are not bound to a plugin, if the plugin author does not add the plugin parameter to the scheduler. But no one, except mob plugin does that. This caused PluginManager to cancel schedulers even if you reload another plugin.
With this update, PluginManager scanns every ten seconds for schedulers and if they dont have a plugin attatched to it, PluginManager detects the plugin and attaches it then.
Schedulers are now forced to be tight to a plugin. Reloading a single plugin wont break other plugins schedulers anymore!
- PluginManager is now registering Sub Command Data.
- Fixed some misspellings.
- The Plugin Info Window displays commands again, if they are not in the plugin.yml.
- The Plugin Info Window now shows you all Plugins that depend on a Plugin.
- Added Command /pluginmanager uninstall. Only executable by an operator!
- Config Browser will now list folders first, than files
- Added a button to the config browser to go to the previous folder (..)
- Window Identification now by ID instead of random color codes in the title
- Plugin Info Form will blend out unknown sections
- Commands from unloaded plugins will now be unshown to users, readded when plugin loaded again
- Plugins that depend on a disabled/unloaded plugin will now disable and reenable when the plugin is loaded again.
- Added permission "pluginmanager.admin" to access everything
- pm load does not require you to write the full file name. It now searches for a file starting with your input.
- You cannot load plugins twice anymore using pluginmanager.
- Fixed bug which allowed you to disable pluginmanager when its written in lowercase
- /pluginmanager [plugin] now shows the plugin ui. You dont have to browse every plugin in the /pm menu anymore. (Even though it is still possible) [You also dont have to write the full pluginname]
It was a little bit annoying to type "FastAsyncWorldEdit" everytime I wanted to unload it.
The UI also tells you the filename of the plugin. Very helpful if you compiled the plugin under a wrong name so you know which is the faulty file.