Okay okay I'm as guilty as anyone...we're not doing very helpful bug reports. And an unhelpful bug report means that Tom is left to do all the work even though he's not in the situation to really test the problem out.

Some stuff we should be doing:

Figure out where the problem seems to be occurring, and then create a little test game with just that code.

Comment out stuff until you narrow down where the bug must be happening for sure.

Post the test case or send it to Tom with complete instructions on how to trip the bug.

If you can't narrow down the problem, have absolutely no clue where it's happening, or have to leave in 2 minutes for a 2 week vacation and don't have a chance to do a better report, then post something with the clear understanding that it's just a data point and that you don't expect Tom to stay up til 4 a.m. trying to hunt it down.

My main crime is that, while I will usually post the code, I don't go through the process of commenting things out until I find the problem. Frequently this reveals the bug in my own code instead of BYOND...and if it does reveal a BYOND bug it makes it vastly simpler for Tom to figure out.

This should be your Christmas gift to Dantom!