Fix Choice'd mons referring to incorrect move when switching #6204
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
Pawkkie
added
category: battle-ai
hedara90
approved these changes
Feb 7, 2025
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.
Description
One of @iriv24's players sent a recording of some weird switching behaviour which lead to this discovery. Turns out
ShouldSwitchIfBadChoiceLockwas checking if the last move used globally was a status move, not the last move the choice'd mon had used was. Whoops!This is to upcoming because
GetMoveCategoryisn't in master.People who collaborated with me in this PR
@/capncrunch
Discord contact info
@Pawkkie