You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, when a Pokémon switches out (without fainting), a switch request is triggered immediately. However, there is at least one case where this does not happen: if a Pokémon's Emergency Exit ability activates in the middle of a so-called fieldEvent—which includes switch-ins and residual effects. In this case, the entire fieldEvent sequence completes before the player has the opportunity to switch in another Pokémon.
This leads to some strange mechanics. For example, if a Pokémon leaves the field during switch-ins, Intimidate will not lower that Pokémon's Attack, but the ability message will still be displayed. Essentially, the Pokémon in that slot is still considered active (as indicated in-game if you attempt to switch in the Emergency Exit Pokémon again), but it is completely immune to everything—damage, healing, stat changes, status conditions, non-volatile statuses, item changes, ability changes, etc.
Some mechanics still need to be tested. For example, in a doubles battle, does Imposter fail or does it transform into the other opponent's Pokémon?
This is also a good excuse to finally separate the action of switching out from the action of switching in, as the Emergency Exit Pokémon should leave the field immediately, only being replaced at the end of the fieldEvent. Additionally, abilities like Neutralizing Gas and Primordial Sea should deactivate after the user leaves the field, and moves like U-turn should make the Pokémon leave the field before allowing the player to choose the switch-in (which is mostly client-relevant).
I would like to start working on this after this PR #10902 gets merged, as it already addresses some mechanics, such as the Emergency Exit skipping other events during the fieldEvent sequence. It also includes the Intimidate test above.
If anyone remembers other relevant cases, feel free to share!
The text was updated successfully, but these errors were encountered:
Usually, when a Pokémon switches out (without fainting), a switch request is triggered immediately. However, there is at least one case where this does not happen: if a Pokémon's Emergency Exit ability activates in the middle of a so-called
fieldEvent
—which includes switch-ins and residual effects. In this case, the entirefieldEvent
sequence completes before the player has the opportunity to switch in another Pokémon.This leads to some strange mechanics. For example, if a Pokémon leaves the field during switch-ins, Intimidate will not lower that Pokémon's Attack, but the ability message will still be displayed. Essentially, the Pokémon in that slot is still considered active (as indicated in-game if you attempt to switch in the Emergency Exit Pokémon again), but it is completely immune to everything—damage, healing, stat changes, status conditions, non-volatile statuses, item changes, ability changes, etc.
Some mechanics still need to be tested. For example, in a doubles battle, does Imposter fail or does it transform into the other opponent's Pokémon?
This is also a good excuse to finally separate the action of switching out from the action of switching in, as the Emergency Exit Pokémon should leave the field immediately, only being replaced at the end of the
fieldEvent
. Additionally, abilities like Neutralizing Gas and Primordial Sea should deactivate after the user leaves the field, and moves like U-turn should make the Pokémon leave the field before allowing the player to choose the switch-in (which is mostly client-relevant).I would like to start working on this after this PR #10902 gets merged, as it already addresses some mechanics, such as the Emergency Exit skipping other events during the
fieldEvent
sequence. It also includes the Intimidate test above.If anyone remembers other relevant cases, feel free to share!
The text was updated successfully, but these errors were encountered: