Dear All,
After a long wait, I am pleased to announce the release of the 2.0.0 version of the PluginManager+. I'll go over the important features that have been altered in this release in the sections below.
Why was it delayed for so long?
This launch was delayed for so long because I had a lot of schoolwork to do as I am now graduating from high school. The majority of the work on this plugin was completed two weeks prior to this date.
Short Description
The fact that the first release contained so many bugs, as well as the code being written so poorly that it was difficult for me to fix, played a significant role in my introducing the 2.0 version. That's when I decided to completely rewrite the plugin and release an updated version. With the new version, I was also able to include an API that developers can use for their own purposes (which will be released in the next 7 days, as I document the whole project).
Additions
Below this line, I will list the majority of the features that I have already implemented in this plugin, as well as the features that will be added in the upcoming updates.
- API - this feature allows me to update the plugin a whole lot faster and it allows other developers to control the plugins on the server better than the standard Spigot plugin provides (to be released).
- Console Logs - with a single click, you can get reports of the plugin into the console
- Private Logs - with a single click, you can also get reports written directly to you in the private chat
- Plugin Loader - this feature is responsible for loading and unloading the plugins and is much safer to handle than the previous loaders that I have written.
- Commands - while the previous version only contained basic commands, such as reload and enable, this version contains more than 10 commands that are regarding a plugin.
- Actions - this feature allows the admins to listen to the actions that PluginManager was performing (to be released)
- TimedActions - this feature was introduced for decreasing the load on the server when editing the plugins on the server. Now each action has a cooldown for X seconds, after which it can be completed again. (for example, a plugin may only be disabled/enabled at the rate of 6 seconds)
Changes
Below this line, I will list the changes that have been made from the 1.5.7 version to the 2.0.0 version, and the reason that those changes happened.
- Messages - messages that are being sent to players have not been removed, but those in the inventories which were a part of the previous versions have been removed. The main reason for this is that I am currently in the process of creating an API that will create inventories based on the .json format. (to be released, probably not in May though)
- GUI's - inventories and how my plugins work in general, separate me from most developers on this website. That's why I took the time and restructured the inventories so that they would appear a lot more natural.
- Animations - all animations that have been a part of the GUI system were completely removed because after analyzing the server load issues reported by the users, I noticed that the GUI updating was in fact producing more load on the server than it was supposed to. (I hope to recreate this feature but by doing it with a safer approach)
- SmartCompletion - this approach was completely integrated within the plugin, so now users may not break a plugin by simply disabling one of its dependencies.
Commands
Below this line, all commands that are now a part of this plugin will be listed:
- /pm or /pluginmanager - opens up the main GUI which is intended for admins when controlling plugins (permission -> plugin.manager.admin)
- /plugin refresh - refreshes the plugins found in the /plugins folder and searches for a new version of the plugin if it is available (permission -> plugin.manager.refresh)
- /pl enable <plugin> - this command enables a certain plugin that has been previously loaded by our manager. (permission -> plugin.manager.enable)
- /pl disable <plugin> - this command disables a certain plugin that is enabled at the moment of execution (permission -> plugin.manager.disable)
- /pl reload <plugin> - this command reloads a certain that is disabled or enable at the moment of the execution (permission -> plugin.manager.reload)
- /pl description <plugin> - sends a quick message containing the description of the specified plugin (permission -> plugin.manager.description)
- /pl info <plugin> - opens up an inventory, containing the most important information about this plugin (permission -> plugin.manager.admin)
- /pl commands <plugin> - opens up an inventory, containing all commands of this plugin, which can also be controlled upon clicking (permission -> plugin.manager.commands)
- /pl whitelist <add/remove> <plugin> - add or remove a plugin from the plugin whitelist (permission -> plugin.manager.whitelist)
Bug Reports
Every bug found in the plugin should be reported directly to me by joining the Pinger Services discord, which can be found on the PluginManager+ page and sending a message in the #bugs channel. I'll get back to you as soon as possible, and I'll do my best to solve the problem as soon as possible.
Enjoy controlling the plugins,
~ Pinger