SwitchType enum to clean up GetMostSuitableMonToSwitchInto #6184
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
AlexOn1ine
approved these changes
Feb 5, 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
I've meant to do this during some of the recent switching refactors and kept forgetting. Alex accidentally reminded me about this today.
For the last while,
GetMostSuitableMonToSwitchIntotakes a TRUE or FALSE to handle whether a switch is after a KO or not. In the spirit of getting rid of passing in booleans that are less readable where it makes sense, this PR refactors the affected functions to use an enum instead.Discord contact info
@Pawkkie