As myself and other plugin developers have experienced, sometimes things will happen when despite the great care and effort we take in the release of our plugins something will go wrong and invariably, when this happens somebody will post something that looks a lot like the following: The problem with this sort of post is that even if we know what you mean it still doesn't help us solve the problem. We as develpers are only human; we can not read your mind (That hook is not added yet) and in the end, we cant help you unless you help us do so. So what do we need? At minimum the following should be included in all "hey, it doesnt work" style posts or replies to the hard working Plugin Developers who spend time away from their families, their kids, their cats, their wives, girlfriends, or even their mistresses to make your minecraft experience better.. DO: 1. Include the Craftbukkit/Bukkit Build Numbers. 2. Include a copy of any config files. 3. Include a good description of any error output that you get. 4. Include if you can a screenshot of the error. This alone will make the developer very interested in helping as it shows you care about his time and the effort he has put into making your life better. 5. Read http://itscommonsensestupid.blogspot.com/2008/07/tips-to-write-good-bug-report.html at least 3 times. 6. Read the topic to make sure your issue has not already been reported or fixed in an update. 7. Remember that if a plugin works with version 57 of Bukkit in version 90 of Craftbukkit, but not with version 57 of Bukkit and version 91 of Craftbukkit (Same Bukkit Version, Different Craftbukkit version) the problem is in Craftbukkkit, not the Plugin! DONT: 1. Use generic phrases like "it doesn't work in the current version". The "current version" is constantly changing and the build you may be thinking of may not be the build that just finished running that works fine.. and "it" is just not descriptive enough to be usefull. 2. Rant or insult the developer. We are doing this out of the kindness of our hearts, so be kind or you may find your requests for help ignored, or worse. 3. Expect the developer to support an old release of craftbukkit. A version one has not even been released yet so expecting him or her to support a version that is old and no longer relevant to the advancment of the project doesnt make sense. 4. Forget to thank the developer for making the plugin in the thread they released it in if you like it. 5. Treat bugs in CraftBukkit like bugs in Bukkit, or like bugs in a plugin. The plugin developers "job" or "obligation" to "fix things" stops at the Bukkit library. CraftBukkit just uses the bukkit library, and if the plugin works in one version of craftbukkit that uses the same version of bukkit as a version of craftbukkit that does not work as expected, the problem is in Craftbukkit and not the plugin developers plugin. If we all follow these rules, plugin releases should go smoother and the community will be better as a result.