Forums Bug Reports timer and $ticks

I'm not going to attempt to have a pointless meta-conversation about how your bug report was inadequate. Perhaps you should just heed my advice and acknowledge that there was enormous confusion in this thread about what you were reporting. The fact that the other two posters in this thread had no idea what you were reporting is a pretty good indicator that something is wrong. Unless you're of the belief that you can't be wrong, and everyone else is an idiot, I think you should be a little less defensive.



Yes, there is. It's not sufficient to assume that your expectation matches that of the help file, especially since the help file does not describe anything regarding the topic you're reporting, so the help file point is quite irrelevant. More importantly, your expectation may not be what the help file describes (in this case we might say that this is not per spec, but in some cases the help file may be wrong too-- you would point that out). We need to know this-- it wouldn't be the first time a bug was mistakenly posted because the user had an expectation that did not match up with the specification. In a few of those cases, we discovered that the specification itself might be wrong (and the user was right after all).

When reporting a bug you need to tell others what result you got, but more importantly, what result you were expecting. I don't see any mention of the actual bug you were reporting, ie., the fact that "the test timer is still in the active timers list", and you made no mention of this in the reproduction steps, nor did you ask anyone to check this; IOW you made no mention that you were expecting the timer to disappear. That might seem fairly obvious, but the lack of this information in your reproduction steps as well means that nobody was expecting this information to be relevant-- you're lucky that Dreadnought accidentally caught this. It's not in the bug subject line either. Nobody knew this was related until you had to point it out a few days later. This doesn't seem wrong to you?



This is not an opinionated assertion. The forums have a search feature, you can look up your past posts for real evidence. Two feature suggestions come up: this and this (the latter of which I still don't even understand, and I guess by the lack of responses, others don't either). I even recall one situation where you were asked outright to better explain your report-- but the forums don't seem to go back far enough.

There is good information on how to write a proper bug report. I highly suggest you read this article completely so you understand what people expect of you when you report a bug. There is a fair bit of valuable information there, you should follow it to avoid future confusion and wasted time.