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] Frenzy moves wont stop by paralyze #3718

Open
allen925 opened this issue Aug 23, 2024 · 2 comments
Open

[Bug] Frenzy moves wont stop by paralyze #3718

allen925 opened this issue Aug 23, 2024 · 2 comments
Labels
Duplicate This issue or pull request already exists

Comments

@allen925
Copy link
Contributor

Describe the bug

I am guessing it's not just paralyze, but I'll just leave idea here, that frenzy moves like thrash continues after being interrupted by paralyze, which is an incorrect behaving.
image

(but if my PR of rollout non stop got merged, it would be a lot more obvious that if you're paralyze and choose to use rollout, there's a possibility you won't be able to command a long time if pokemon survive. )

thrash-paralyze.mp4

Session export file

No response

User data export file

No response

Expected behavior

stop if paralyzed and maybe other status effects, something like

      .attr(MissEffectAttr, frenzyMissFunc)
      .attr(NoEffectAttr, frenzyMissFunc)

but status effect version should trigger

Screenshots / Videos

No response

What OS did you observe the bug on?

PC/Windows

If other please specify

No response

Which browser do you use?

Chrome

If other please specify

No response

Additional context

No response

@allen925 allen925 added the (Legacy) Bug Legacy Label, don't apply to new issues/PRs label Aug 23, 2024
@Snailman11 Snailman11 added the Move Affects a move label Aug 23, 2024
@Snailman11
Copy link
Collaborator

Snailman11 commented Aug 26, 2024

Does
#3041 fix this
@schmidtc1

@schmidtc1
Copy link
Contributor

Does #3041 fix this @schmidtc1

I don't think it does. You likely need to apply the noEffectAttr somewhere in MovePhase either where status effects are activated or where moves are cancelled in doMove(). That's my guess at least

@Snailman11 Snailman11 added P2 Bug Minor. Non crashing Incorrect move/ability/interaction and removed (Legacy) Bug Legacy Label, don't apply to new issues/PRs labels Sep 5, 2024
@Snailman11 Snailman11 added (Legacy) Bug Legacy Label, don't apply to new issues/PRs P2 Bug Minor. Non crashing Incorrect move/ability/interaction and removed P2 Bug Minor. Non crashing Incorrect move/ability/interaction (Legacy) Bug Legacy Label, don't apply to new issues/PRs labels Sep 16, 2024
@Snailman11 Snailman11 added Duplicate This issue or pull request already exists P2 Bug Minor. Non crashing Incorrect move/ability/interaction Move Affects a move and removed Move Affects a move P2 Bug Minor. Non crashing Incorrect move/ability/interaction Duplicate This issue or pull request already exists labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants