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: Add 263/264 line types #5896

Merged
merged 1 commit into from
Nov 3, 2023
Merged

raidboss: Add 263/264 line types #5896

merged 1 commit into from
Nov 3, 2023

Conversation

valarnin
Copy link
Collaborator

@valarnin valarnin commented Nov 3, 2023

Add the new line types, and their corresponding documentation.

I don't think I missed anything here but please double check as the info included in LogGuide.md may be excessive or not 100% accurate for all cases.


This line contains extra data for ActorCast/StartsUsing network data.

This line is always output for a given StartsUsing cast. If the ability does not target the
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a belated thought for the OP patch, but I wonder if it'd be better if this line always printed the source position and then also included the target data if it existed (maybe with flags here too, if they exist). Mostly just saying that there's a lot of "figure out where things are when they start casting" that would benefit from always having the source actor position. (cc @xpdota too)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it have the same issue as the native 20/21/22 lines, where a position read from memory might be stale?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the hope was that it would have actor position data in the network packet as well, but I don't think that's the case?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that was my hope. I guess if it doesn't have it, then it doesn't have it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the only true solution for cast-before-move race conditions - without modifying the base plugin - is to hook ActorMove (and anything else that could move an actor), and have that data take priority over memory in 261-lines.

@quisquous quisquous merged commit ebe47e9 into quisquous:main Nov 3, 2023
6 checks passed
github-actions bot pushed a commit that referenced this pull request Nov 3, 2023
Add the new line types, and their corresponding documentation.

I don't think I missed anything here but please double check as the info
included in LogGuide.md may be excessive or not 100% accurate for all
cases. ebe47e9
github-actions bot pushed a commit that referenced this pull request Nov 3, 2023
Add the new line types, and their corresponding documentation.

I don't think I missed anything here but please double check as the info
included in LogGuide.md may be excessive or not 100% accurate for all
cases. ebe47e9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants