improve ai switching with bad moves #3213
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
LOuroboros
reviewed
Aug 8, 2023
Co-authored-by: LOuroboros <[email protected]>
Merged
…emerald into ai_switch_mon_fix
|
Conflicts solved, ready to merge @ghoulslash |
ghoulslash
approved these changes
Aug 29, 2023
Merged
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.
If all moves have bad scores, the AI can also switch in double battle, and as a partner player pokemon, as opposed to just an opponent in a single battle.
I moved shouldSwitchMon from ai thinking struct, because it gets overwritten everytime move is chosen for any of the ai battlers. I also created an additional field monToSwitchId, so that it doesn't look for the mon 2 times.