Corrected outdated motion detection property #1376
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Appears to work, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolved an issue that was reported on the XIV Tools Discord server concerning Anamnesis' inability to detect whenever actors are frozen while in GPose.
This property is part of Client::Game::Character::BlacklistProxyContainer, which starts at offset 0x1A98h from the Character object. I believe it corresponds to the motion state as the class has the functions "FreezeMotion" and "ResumeMotion". Testing it in-game also seems to corroborate that. Unfortunately, its not yet mapped by the guys and gals over at aers/FFXIVClientStructs so I can't say for certain this is the right variable.