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

raidboss: r2s/m2s Poison Sting (drop) timeline entry is misleading #362

Open
valarnin opened this issue Aug 20, 2024 · 3 comments
Open

raidboss: r2s/m2s Poison Sting (drop) timeline entry is misleading #362

valarnin opened this issue Aug 20, 2024 · 3 comments

Comments

@valarnin
Copy link
Collaborator

Per the comment here:
Originally posted by @Battler624 in #294 (comment)

The timeline entry for Poison Sting (drop) is misleading. The timeline entry corresponds to the damage snapshot. However, the actual visual damage numbers and the puddle drop snapshot are not at the same time.

Example lines:

20|2024-08-14T00:08:43.1510000-04:00|4000743C|Honey B. Lovely|9193|Poison Sting|10001234|Some One|5.700|100.00|100.00|0.00|3.14|56456489927f107d
21|2024-08-14T00:08:49.1260000-04:00|4000743C|Honey B. Lovely|9193|Poison Sting|10001234|Some One|750003|4A1F0000|E80E|B7D0000|1B|91938000|0|0|0|0|0|0|0|0|0|0|208158|208158|3600|10000|||118.33|99.26|0.00|1.74|44|44|0|10000|||100.00|100.00|0.00|3.14|00005462|0|1|00||01|9193|9193|0.200|FFFF|8948232c0116ddc8
37|2024-08-14T00:08:49.7520000-04:00|10001234|Some One|00005462|189183|208158|3600|10000|0||118.33|99.37|0.00|0.13|1500|0|0|02|05000000|0|0|E0000000|06000B7D|0|419B5A1B|4000743C|cc031b7c5aa1fb40
4096|2024-08-14T00:08:49.9720000-04:00|SpawnObject|668|40007601|02|07|05|001EBAA1|40007601|00000000|800375BA|E0000000|00000000|1.0000|0000|-0.0001|0000|00|00|00000000|00000000|0.0000|118.3628|0.0000|dc3e01f12051d4d6

(My custom SpawnObject line's X/Y/Z indexing has been broken since DT release, but this is the correct actor for the puddle)

It is likely that the puddle drop's position snapshot corresponds to the 37/NetworkActionSync line, but I don't have time to dig through raw network data right now to confirm.

@Battler624
Copy link

If possible, can we update it to the puddle drrop snapshot? would be perfect for uptime stuff.

thanks valarnin and everyone. <3

@valarnin
Copy link
Collaborator Author

If possible, can we update it to the puddle drrop snapshot? would be perfect for uptime stuff.

That would be the goal but we'd either have to err to the side of caution (use the SpawnObject timing, which could be 250ms late), or we would need more careful raw network packet inspection (checking the raw ActorMove packets pre-player-filtering for someone not the current player to see which packet corresponds most closely with the spawned puddle, then doing some linear interpolation to get the actual timing).

@Battler624
Copy link

Is there no cast or channel that happens at the same that can be used as a pointer?
I recall this is what was used in p9s meteor.

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

No branches or pull requests

2 participants