Fix Pursuit interaction with Encore#11803
Open
andrebastosdias wants to merge 2 commits intosmogon:masterfrom
Open
Fix Pursuit interaction with Encore#11803andrebastosdias wants to merge 2 commits intosmogon:masterfrom
andrebastosdias wants to merge 2 commits intosmogon:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://www.smogon.com/forums/threads/past-gens-research-thread.3506992/post-10865371
Gens 3 and 4 work like this because Pursuit is hardcoded into every switch-out. All Pokémon are looped through, checking whether they are going to use Pursuit or are encored into Pursuit.
To simulate this inside the Pursuit condition:
pursuitcondition holder from the possible targets to the Pokémon that selected Pursuit (which, IMO, makes a lot more sense).pursuitcondition if the Pokémon is encored into Pursuit.