Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emergency Exit + Eject Pack timing bug #5550

Open
TerraPrograms opened this issue Oct 20, 2024 · 0 comments
Open

Emergency Exit + Eject Pack timing bug #5550

TerraPrograms opened this issue Oct 20, 2024 · 0 comments
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet

Comments

@TerraPrograms
Copy link

Description

When a Pokemon uses up it's own Eject Pack (say Typhlosion uses Overheat) on a Pokemon with Emergency Exit (Golisopod), Emergency Exit should activate and cancel out Eject Pack. Currently in the Expansion, both Pokemon switch out.
Showdown proof: https://replay.pokemonshowdown.com/gen9customgame-2227013955 (Typhlosion holds Eject Pack, you can even see it getting consumed, but still cancelled)
Showcasing how it works with Double Battles:
https://replay.pokemonshowdown.com/gen9doublescustomgame-2227104763 - Typhlosion hits Golisopod into Emergency Exit range and it's Eject Pack still gets cancelled
https://replay.pokemonshowdown.com/gen9doublescustomgame-2227015758 - Typhlosion misses out on activating Golisopods Emergency Exit, thus activating its Eject Pack successfully. Ninjask then gets 1 more hit off, activating Golisopods Emergency Exit

Version

1.9.3 (Latest release)

Upcoming/master Version

No response

Discord contact info

..terra..

@TerraPrograms TerraPrograms added bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet
Projects
None yet
Development

No branches or pull requests

1 participant