You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand this can be problematic but I'm not sure this is something we will fix - that's the order the events are in the demos, so they are fired in this order.
What I personally do is store those events in a buffer, and handle them after parsing the frame. I had to do this because of weapon fire events popping up after player hurt events.
Describe the bug
Kill and playerhurt events trigger in wrong chronological error order (may be due to sub-tick). See example:
To Reproduce
Download link to demo:
https://drive.google.com/file/d/1NXLcl3n8roTLqyRDH2LBhWF1YItkisbA/view?usp=sharing
Round where it happens:
CT 15 | T 15
Expected behavior
That the kill events triggers after playerhurt events.
Library version
v4.0.0-beta.5
Additional context
This might be due to CS2 sub-tick.
The text was updated successfully, but these errors were encountered: