@Bone008 That is exactly what I tried to do in NoLagg, but all it does then is throw the error as if NoLagg crashed. And thus everyone posts at NoLagg because hey, it's the first-stated plugin name right? So I got rid of the throw bit and made the error as undistinctive from NoLagg as possible to ensure proper care for those errors. The question is: how far do you go? I have no idea how CPU-heavy the 'Thread.getCurrentThread()' is, it could cause performance loss if you use it in (commonly called) Bukkit methods. And yes you are right about deadlocks, they will surely occur if a plugin manages to synchronize some sort of infinite loop.