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

[Bug] Releasing a Pokemon in a Double Battle after Switching to it with the First Pokemon Spends Turn, Sends out Fainted #5186

Open
Snailman11 opened this issue Jan 26, 2025 · 0 comments
Labels
P2 Bug Minor. Non crashing Incorrect move/ability/interaction

Comments

@Snailman11
Copy link
Collaborator

Snailman11 commented Jan 26, 2025

Describe the bug

In a Double Battle, choosing to switch with your first Pokemon into a Pokemon that is in a higher or equal slot in your Party than the Pokemon you release on your second Pokemon's turn sends out sends out a Pokemon that has just entered that slot, even if the new Pokemon is fainted.
-If no Pokemon would exist in that slot after the Pokemon is released, the Pokemon that would have switched does nothing on that turn.
-If the Pokemon is fainted the textbox plays: "xxxx is ineligible for this challenge".

Reproduction

Start a run with 5 Pokemon in your party.

  1. Switch into the Pokemon in the 5th slot.
  2. On the second Pokemon's action release the Pokemon in the 3rd Slot, then use a move.
	BATTLE_TYPE_OVERRIDE: "double",

Expected behavior

PP Flyout should reset if it would become inaccurate through moveset differences on form change.

Screenshots / Videos

Choosing to Switch into a Pokemon and releasing a Pokemon in an equal or lower slot sends out the Pokemon that newly occupies the slot.

Releasing.after.switch.Next.mon.in.slot.1.mp4

If the next Pokemon is fainted, the fainted Pokemon is sent out

Fainted.Pokemon.can.be.sent.out.if.new.slot.1.mp4

If no Pokemon would exist in that slot, the switching Pokemon does not act

Releasing.last.mon.no.move.1.mp4

Session export file

No response

User data export file

No response

Additional context

No response

@Snailman11 Snailman11 added the P2 Bug Minor. Non crashing Incorrect move/ability/interaction label Jan 26, 2025
@Snailman11 Snailman11 moved this from To triage to Ready in PokéRogue Bug Management Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Bug Minor. Non crashing Incorrect move/ability/interaction
Projects
Status: Ready
Development

No branches or pull requests

1 participant