What if someone is using a slightly dated server for one reason or another? Won't removing the constructor break the plugin for builds older than 45? As @The_Wrecker said, changing the plugin directory, for instance to one used by multiple plugins. The super() automatically loads the plugin's config.yml file, what if you have a config.yml file shared by multiple plugins! In my case I'm also loading a second yml file in the plugin constructor in the same way. (Though this could be moved to enable, I had it there to be consistant. Eg, not one settings file loaded on the super constructor, and the other on enable.) In addition, if I am not mistaken, Bukkit will eventually allow you to enable and disable plugins live, no? What if there are things you don't want to be done on each enable and disable, such as static memory allocation for the plugin? --- merged: Feb 21, 2011 11:04 PM --- More: I looked over the specific change, and I see that the stuff that was in the super constructor was moved to a function called initialize. (Along with the yml load.) Perhaps this can be overridden, though I'm still concerned about maintaining compatibility with a broad range of builds, if I can.