What is it? Plugin Metrics/ MCStats is a service that was created by myself around 5 months ago (the start of January). It serves to be more open than other closed-off plugin stats systems while at the same time striving to provide incredible possibilities in what can be done with it. All data is for the most part public and you can view the same data plugin authors can view. A very large percentage of Bukkit-enabled servers are somehow affected by Plugin Metrics / MCStats. There are over 80,000 servers reporting during peak times of the day (which is over 400 requests/second). Metrics represent over 500 plugins that make up our servers and define how our servers work. Of these are ones almost everyone will have heard of: Essentials, Vault, mcMMO, ChestShop, LWC, and many other excellent plugins. Even the Bukkit fork CB++ which is not a plugin uses this. What does it do? It does stat collecting. Much like Minecraft's official stats but this does not cover the same aspects Metrics covers. Plugins can optionally submit and graph custom data, for example Vault creates pie graphs of what Econ/Perm/Chat plugins are hooked. Metrics does not download any files to install itself. It is bundled directly with the plugin and reads from the same config file as every other metrics-enabled plugin. Some plugins add in a second opt out (which only one needs to be activated) and some allow you to opt out from in-game (for example, Essentials), however all will contain at least one opt-out inside plugins/Plugin Metrics/config.yml How am I affected? No server can be identified by IP. Servers that participate in Metrics and are not opted out identify themselves by a unique GUID which the server itself generated, it is not generated by my end. Why even create this? As the author of LWC I wanted to know usage stats but also did not want a proprietary solution. There was other stats providing services but I wanted something I could tweak and I imagined much more than just basic numbers. So I made it. And then opened it up to other authors and got the best feedback I could have gotten. From there it built up slowly and I have the plugin authors - those that create the plugins that shape our servers - to thank for the great success and progress we made which kept me motivated to add things others would enjoy. For us, we are surprised by the numbers we see and it will make some server owners mad to see this but it will not diminish our amazement for what we get from it. I personally lose from this venture but I've gained more than enough in experience and fulfillment to make up for it all. Ok, but what exactly is read/sent? It is not possible for Metrics to control the plugin in any way except for plugin-specific code the plugin author implements. As mentioned before, nothing is downloaded, so what you get is what the plugin author implemented. The following data is read from the server in some way or another: 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 The following data is sent to http://mcstats.org: Metrics revision of the implementing class Server's GUID 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 Any custom data the supporting plugin implements. This is variable and I am not responsible for this however usually it is just plugin-specific data (e.g for LWC, the database type: MySQL or SQLite, and Locale used (english, german, etc)) How do I really know you aren't doing something sketchy? The entire source (both frontend and business end) have been open-source from the very beginning. I've not seen other plugin stats services open source everything so I think this is a first. This transparency gives me a better assurance that it is better received and I also benefit from from pull requests, critique, and general banter around it. These can be found here: https://github.com/Hidendra/mcstats.org (frontend, old report processing backend) and https://github.com/Hidendra/MCStats (new reporting backend, in Java) What can I do? Plugin Metrics / MCStats would not be where it is today if not for the many plugin authors that have at least tried out this service. As well, I could not do it alone, and many of the ideas are a result of speaking with these same authors and throwing ideas around. As a plugin developer, you are free to use this service at absolutely no cost. There will never be ads or a "premium service" -- I cover all costs however donations are of course welcome but not required. The service is self-sustained and only requires my intervention to let you access your plugin in the admin panel. For more information please take a look here: https://github.com/Hidendra/Plugin-Metrics/wiki or join us in IRC As a server owner, you are free to question the service, welcome it, or deny it. All plugins that support Metrics use the same opt-out and as such you may opt out of further data at any time. You may ask myself any question and I will do my best to answer it -- I am as open as possible with Plugin Metrics / MCStats and hope this will help you understand what exactly it is. Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true. If this folder does not exist, you do not have any metrics-enabled plugins installed As anyone else, your input is extremely welcome. How you feel about it will allow me to make improvements and make it better for everyone as a whole. http://mcstats.org If you have any questions at all about how the service works or anything about Plugin Metrics/MCStats, please feel free to ask here or PM me, I (or anyone else) will do our best to answer it. also, join us in IRC, we have a lot of love to go around: irc.esper.net #metrics Thank you.