redstone torch burnout problems fixed!

I've had issues with redstone torches burning out and never coming back (until the server is restarted) for what feels like years. I'm finally at a point where I can fix this myself. it's a simple patch, only changing one line in one file. it's a simple patch for bukkit servers, just extract the zip and drop in the jar. I can't post it here, but pm me if you want a copy. I've been running the patch for almost 2 months with no issues or lag from it. use at your own risk.

 

why can't you post it here? also, technically you should have informed the bukkit team of your findings, and let them modify the necessary code instead of redistributing one of your own files.
NuclearW

 

I dunno. maybe posting just the patch would be ok, but I'd have to check first. last time I was yelled at for posting a modified bukkit build. lol. I've commented in bug tickets and reported my findings there. I'd love to have a simple api to modify the behavior of redstone torch burnout. or another way to do it, add it to bukkit.yml with options to enable/disable or set a custom threshold.

not sure if I still have the issue with torches not coming back on with the latest recommended build. I went back to R1.0 when I got tired of the exception spamming from "connection closed".

 

I understand why they would be annoyed with a modified bukkit build, since that could be completely unstable or worse, include damaging code. However, if you ask an administrator to review your modifications, and they find it safe, there would be no reason to prevent its use, and the information might end up in an actual build, benefiting everyone

 

that would be great. I'm doing well with plugins, but I'm not so confident submitting code for bukkit. I could make an attempt. can't be that hard to add a line to bukkit.yml. I'm sure #bukkitdev irc would give me a hand if I needed it.