Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kill events triggering before PlayerHurt events #457

Open
Falderebet opened this issue Oct 24, 2023 · 2 comments
Open

Kill events triggering before PlayerHurt events #457

Falderebet opened this issue Oct 24, 2023 · 2 comments

Comments

@Falderebet
Copy link
Contributor

Describe the bug
Kill and playerhurt events trigger in wrong chronological error order (may be due to sub-tick). See example:

"zorte<6><TERRORIST>" [490 -474 -160] killed "siuhy<15><CT>" [-946 -659 -263] with "awp"
"zorte<6><TERRORIST>" [490 -474 -160] attacked "siuhy<15><CT>" [-946 -659 -263] with "awp" (damage "108") (health "0")

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.

@markus-wa
Copy link
Owner

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.

@sirherrbatka
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants