Monitors the server console during and after startup for error messages. Parses the plugin name from error message if possible and outputs the constructor to a flatfile. Stops server, disables plugin (or moves plugin out of plugin folder), starts server, and prints the constructors of all plugins in flatfile to the server chat once every 10 minutes in a "system report". Permissions node 'updateswatter.alertbroken' to determine who can hear the alert. Periodically (period defined in a config file) check for the newest version of craftbukkit. Print the version number and changelog information to the server chat once every 10 minutes in a "system report". Allow anyone with access to the permissions node 'updateswatter.cbupdate' to type /swatter cbupdate and force a shutdown, update, and restart of the server. Allow anyone with access to the permissions node 'updateswatter.cbrollback' to type /swatter cbrollback to move back to the next most recent version of craftbukkit that the server has used. Permissions node 'updateswatter.alertupdate' to determine who can hear the alert.
This is an absolutely awesome idea. I'm surprised no one has thought of this before, I'd love to see this done.
Interesting idea... perhaps the swatter could be set to auto-rollback for important plug-ins like World Guard, should they crash. Or perhaps not allow people to join until all mentioned plugins in a file are loaded up completely (like World Guard), to ensure that everything is working properly before people go on, and admins can figure out what's not working immediately and get it fixed. All-in-all, great idea.
well minus physically moving the plugins Pail and CButD will work keep an eye on pail as well because its still being improved every day.
