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.

Sign up for GitHub

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

Jump to bottom

Z moves inherit priority of their base move when they shouldn't #3686

Closed
kleeenexfeu opened this issue Dec 11, 2023 · 0 comments · Fixed by #3690
Closed

Z moves inherit priority of their base move when they shouldn't #3686

kleeenexfeu opened this issue Dec 11, 2023 · 0 comments · Fixed by #3690
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet

Comments

@kleeenexfeu
Copy link

Description

Title is self explanatory, it is because in src/battle_main.c GetChosenMovePriority and GetMovePriority don't check the zmove structure in the BattleStruct.
It causes a z-sucker punch to have priority, and a dazzling target to stop said move.

Version

1.6.2 (Default)

Upcoming Version

No response

Discord contact info

No response
@kleeenexfeu kleeenexfeu added bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet labels Dec 11, 2023
@AlexOn1ine AlexOn1ine mentioned this issue Dec 11, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes z-move priority AlexOn1ine/pokeemerald-expansion-1
1 participant
@kleeenexfeu