exactly, its less about time and more about the resources to do it. From there I could ATTEMPT to cross reference what changes were made to the hooks and methods called in the plugins and from there I could again ATTEMPT or someone else could assist in making every method continue to spam console so when it crashes the method in question would continue to spam. In fact I am going to compile a list of plugins that should be tested. Ok so what we would need is someone to volunteer to run 522 since errors seemed to be more frequent using this for me at least, with these plugins, Code: Achievements.jar Authentication.jar AutoSave.jar BigBrother.jar ChatStamp.jar Citizens.jar CraftIRC.jar dynmap.jar General.jar iConomy.jar mcMMO.jar MinecraftCheck.jar MonsterHunt.jar MyHome.jar Permissions.jar SearchIDs.jar Stats.jar TelePlus.jar uQuest.jar WorldEdit.jar WorldGuard.jar Removing one at a time on each crash, when one remains and it crashes write it down and start over until no crashes are evident for 24 hours. From which point I will do my best (or get help) to dissect the code of the plugin(s) writing down each class and hook, and cross referencing them to hooks and methods changed inside bukkit between 440 and 493. Then I or with help will work on making each of those hooks/methods echo to the console continuously until a crash happens and the problematic class is spamming console without stopping. (this server and log I would personally deal with considering it would be A LOT of spam and little resources since it will only be connected to to test status.) From there I or with help could look into WHY the method is hanging OR just report the hanging method as a bug to the bukkit team (depending on how complicated it is? I have just started java but it's similarities to the other languages I know may provide the answer) I'm in, 440 lags like hell lol, anyone else? EDIT by Moderator: merged posts, please use the edit button instead of double posting.