That's not all, other weird things happen as well. There seems to be some kind of pattern with it, but I can't discern it. I actually have some proof here as well.
I re-bound my MOUSE1 to the following:
- {l Code}: {l Select All Code}
bind MOUSE1 [action 0; echo (getmillis)]
I also set an environment with botspeed 0, MANY bots, and a small map with few spawns like echo to cluster them, and on insta. This was to make testing easier.
The purpose behind the bind is to show how much time has passed between each kill (more debug info mostly for the devs). Regardless, you can still see something is quite screwy by looking at this log:
- {l Code}: {l Select All Code}
bot [1] was laser shocked by ZeroKnight [WAZU] [@2.53m]
7769837
bot [16] was laser shocked by ZeroKnight [WAZU] double-killing [@2.25m]
7773224
bot [7] was laser shocked by ZeroKnight [WAZU] [@3.20m]
7774011
bot [1] was laser shocked by ZeroKnight [WAZU] triple-killing [@2.69m]
7777455
bot [23] was laser shocked by ZeroKnight [WAZU] [@4.26m]
7778144
bot [15] was laser shocked by ZeroKnight [WAZU] [@2.12m]
7779147
bot [9] was laser shocked by ZeroKnight [WAZU] [@3.52m]
7779648
bot [11] was laser shocked by ZeroKnight [WAZU] multi-killing [@5.39m]
7780441
Notice how I got a double, no triple, then a triple? Just like I mentioned in my opening statement. Then as you can also see, something even weirder happens. 3 kills after triple, none of them count as a killstreak, but a kill right after that earns me a multi? It seems like the window of time given to get the next kill is being calculated incorrectly, and giving false results if things are timed up just right.