Did you see? only a programmer understands this pain.There are some procedures in my game (on twine are called widgets) that work just like those Counterstrike functions.Wait until you reach the next step: You look at your code, to improve it or add a functionality, just to discover that it shouldn't works ; yet so far it's working without problem.
It's something that happen more often that professionals are ready to admit it. But when you look at advanced open source project, it's not this exceptional to find comments that goes like, "I know, there's a bug here, but if you fix it, everything will stop to works".
There's a relatively well known case like this ; my memory don't improve with the age, so don't quote me on this, but I think that it's in the source for the original Counter-Strike. There's two consecutive call to the exact same function, with the exact same parameters. And a comment before them, warning that if you remove one of the call, then the call will have no effect...
For whatever totally unknown reason, you need to process the same code, with the same values, twice in a row for it to works, and it only happen in that part of the code. For any other place where the function is called, one call is enough, except... there.
You have my heart but then you always run saying that you have to chat with someone named Icarus... and leave me hurt and heart broken