FerryPluginCore
FerryPluginCore
What it does
This is a plugin that contains many features I use across all my new plugin, like code by codename_B to play firework at some locations, and other code pieces from my to provide other features I use, like better error handling at plugin startup
Why doesn't you place those important code pieces to those plugin
this method has a drawback when 1 of the codes found out to crash sometimes, you need to update all of those plugin, with the system I created, you only need to update 1 plugin to fix all the plugin using that system.
Configuration
There will be 2 configuration keys, the first will be debug mode, and the second wll be a format al of my plugins are going to use when they send a message
Permissions
This plugin does not have permissions.
Commands
This plugin does not have any commands.
Metrics
Multiworld uses statistics tracking Multiworld is using a statistics tracking code so useage statistics will be logged. The following data is read from the server in some way or another:
What is logged:
File Contents of plugins/Plugin Metrics/config.yml (created if not existent)
Players currently online (not max player count)
Server version string (the same version string you see in /version)
Plugin version of the metrics-supported plugin
Mineshafter status - it does not properly propagate Metrics requests however it is a very simple check and does not read the filesystem
how to disable
edit plugins/PluginMetrics/config.yml and set opt-out to true.
TODO
Maybe add more code pieces as I am continuing the developing of the plugin.
@Aterruit
I think he means:
"Why dont you put those important pieces of code into the plugins"
"Why doesn't you place those important code pieces to those plugin"
I try my best to understand what people say, but you lost me man.