Fiel Wrote:Finally found the answer, but the quest for truth is often more interesting than the truth itself. I will give a spoiler alert, though. I found a bug!

This utterly baffled me, so I went searching for answers. I checked the results of my regex and it turns out it was spitting out an additional 300 ms garbage value at the end. But how is this possible? It shouldn't be doing that. I then changed a simple ".*?" to "\d+" and it worked perfectly. Turns out ".*?" is too permissive which allowed the query to find 3 - 4 lines instead of just one, singular line. So it stole delay values from other delay classes causing it to spew out wrong values. How disheartening. I did do some preliminary testing before calling this method stable, but the ones I tested on were unaffected by this bug. Damn.

I sincerely, really apologize for the mistake and for causing such an uproar. Mia culpa. The correct delays are now posted.

byakugan Wrote:Nah, it's all ok. Even when I did nothing at all, I had fun reading all the comments and calculations in this thread. I'm sure most of us feel the same way (except Paladins xD).