Fix Carryall InitialActor creation. #19620
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
|
Going to running some test case. |
|
So far so good! |
MustaphaTR
approved these changes
Aug 20, 2021
|
2 hours test passed |
reaperrr
approved these changes
Aug 20, 2021
|
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.
Fixes #19619, which is caused by a bug in #19068.
Carryable.Attached was being called with the wrong actor, which meant that
carriedTokenwas being assigned a bogus token value that just happened to match a condition owned byGrantConditionOnDamageState. Carryable.Detached revoked the token out from underGrantConditionOnDamageState, putting the actor into an inconsistent state that causes a crash when that trait legitimately tried to revoke that condition some time later.