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

Sheer Force and Shield Dust do not affect the correct moves #3055

Closed
BuffelSaft opened this issue Jun 12, 2023 · 1 comment
Closed

Sheer Force and Shield Dust do not affect the correct moves #3055

BuffelSaft opened this issue Jun 12, 2023 · 1 comment
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet

Comments

@BuffelSaft
Copy link
Collaborator

Description

Sheer Force does not negate effects that benefit the user, due to this line in battle_script_commands.c:
if (TestSheerForceFlag(gBattlerAttacker, gCurrentMove) && affectsUser != MOVE_EFFECT_AFFECTS_USER)

This applies to Flame Charge, Charge Beam, Diamond Storm, Power-Up Punch, etc.

Shield Dust decides which effects to block based on the order of the move effect definitions:
&& (gBattleScripting.moveEffect <= MOVE_EFFECT_TRI_ATTACK || gBattleScripting.moveEffect >= MOVE_EFFECT_SMACK_DOWN)) // Exclude stat lowering effects
I suspect this was not considered/updated when adding new effects (I certainly didn't know it was there), so this is not working correctly.

This was also discussed in the discord, starting here: https://discord.com/channels/419213663107416084/774393519569502268/1117747437436665886

Version

1.5.0 (Default)

Upcoming Version

No response

Discord contact info

buffelsaft

@BuffelSaft BuffelSaft added bug Bug category: battle-mechanic Pertains to battle mechanics status: unconfirmed This bug has not been reproduced yet labels Jun 12, 2023
@Bassoonian
Copy link
Collaborator

With the Sheer Force updates of 1.8, this is now superseded by #4104

@AsparagusEduardo AsparagusEduardo closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 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

3 participants