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] Eternatus's PP Flyout does not Reset Upon Form Change / to Reflect New Moveset #5185

Open
Snailman11 opened this issue Jan 26, 2025 · 0 comments
Labels
P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions.

Comments

@Snailman11
Copy link
Collaborator

Describe the bug

Eternatus's PP Flyout continues to display PP used from its initial moveset.
-As new moves are used, they're added to the box from left to right / top to bottom.
-If it uses the same move again, PP for that move is updated to reflect the true value.

Link to Discord's Bug Report (Final boss phase problem)
https://discord.com/channels/1125469663833370665/1332857914356011100

Reproduction

	STARTING_WAVE_OVERRIDE: 200,
	STARTING_BIOME_OVERRIDE: Biome.END,
	STARTING_LEVEL_OVERRIDE: 1000,

	MOVESET_OVERRIDE: [Moves.RECOVER, Moves.ENDURE, Moves.SYNTHESIS],
	ABILITY_OVERRIDE: Abilities.PRESSURE,

Expected behavior

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

Screenshots / Videos

Etern.PP.Flyout.mp4

Session export file

No response

User data export file

No response

Additional context

No response

@Snailman11 Snailman11 added P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions. Triage The issue needs triage labels Jan 26, 2025
@Snailman11 Snailman11 moved this from To triage to Ready in PokéRogue Bug Management Jan 26, 2025
@Snailman11 Snailman11 removed the Triage The issue needs triage label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions.
Projects
Status: Ready
Development

No branches or pull requests

1 participant