Bukkit

@Yebol

Thank you for the comment. I would like to request that the next time you want to report that a plugin may be non-functional, you attempt to use the plugin first. I assume you're referring to the recent updates for 1.6 and such, so I feel I should note their standard information on whether or not the update breaks plugins:

"Provided the developers of the plugins you are using are keeping up with the development of Bukkit, all your plugins should work fine, with the exception of plugins that use Minecraft or CraftBukkit code."

This plugin uses only the Bukkit api. It does not use Minecraft code, nor does it use internal CraftBukkit code. Unless the craftbukkit team releases an update that breaks the majority of plugins, this one is likely to remain intact. If you are concerned about the plugin-breaking information provided with the 1.6.2 update, I feel it should be noted that my last post in this thread was on August 31st, which was nearly two months after the release of the 1.6.2 builds, and that I did thorough testing at the time to ensure that the API was still functional in the ways I had used it. I feel I should note that, as always, bug reports should be filed on the issue tracker linked above, since I keep up to date with that.

All right guys, I'm really sorry about the long absence. While I can't make any promises about updating this plugin, there are a few things I can at least clarify.

1. This plugin currently functions on any version of Bukkit, Libigot, or Spigot that I have tested it on, so there should be no compatibility issues. Further, it does not use anything outside of the normal Bukkit API, meaning that it shouldn't break unless the Bukkit team starts doing massive rewrites.
2. I can't touch the EnderDragon's death sound effect without making a pull request to Bukkit and CraftBukkit to add a cancellable sound event. This is because Bukkit currently does not give any way to cancel sounds being sent to the client. At the moment, I don't have the kind of time it would take to implement that kind of patch, nor do I have the time to sit there waiting in their pull request system hoping to get noticed.
3. For those concerned about shared experience, the recent patch by socram8888, which is in the dev builds, allows you to configure the plugin so that the EnderDragon drops the exp as an experience orb, rather than simply granting the exp to the players directly.
4. For those wondering about the plugin's version numbers, I would like to point out that they have no bearing on what versions of Minecraft they are intended for. I update the version numbers of my programs and plugins when I feel that enough changes have been made to warrant it, rather than when related software changes versions.
5. For those who still have issues with the dragon respawning, I would simply like to apologize. I realize there is a bug in my code somewhere, but I have yet to find it, even after a year of tracing the entire plugin line-by-line in search of it whenever I grew bored.
6. For those who are looking for an update to the plugin, I would like to refer you to the issue tracker link at the top of the page. That not only deals with bugs, but also feature requests, and you can see what my plans for the plugin were when I was interrupted by life in general. As a general rule, if someone files something in that issue tracker, I would get back to it much faster than if it were mentioned in this thread. That's because I still visit Github on a regular basis, and it informs me when issues have been filed. While I cannot guarantee that I will work on this plugin (I have other obligations at the moment, including a job, college, family, and a large-scale programming project between some friends and me), I can say that I have been known to go dig through my old issues for something to do when I grow bored, so it isn't outside the realm of possibility.

I would also like to note that in the current version of the plugin, the triggers for spawning the EnderDragon are someone entering a world it's configured to spawn in, as well as someone logging in while in one of those worlds, and that they have to be close enough to the configured spawn point that the chunks would be loaded. I would also like to note that I'm fairly certain that if an EnderDragon has never been spawned in that world, it may still cause problems with this plugin, which can be fixed by using a plugin like Essentials to spawn a dragon in the appropriate world, then kill it as normal. This is because the timer needs a starting point, and I'm unsure of whether or not I set an appropriate starting point for when no dragon has been found. (It's been a while since I've looked into that, as well)