-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] Fix Wimp Out/EE Trainer Battle causing enemy stack with multi hit #4935
Open
muscode13
wants to merge
9
commits into
pagefaultgames:beta
Choose a base branch
from
muscode13:bug/wimptrainer
base: beta
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tempo-anon
added
Ability
Affects an ability
P2 Bug
Minor. Non crashing Incorrect move/ability/interaction
labels
Nov 25, 2024
DayKev
reviewed
Nov 26, 2024
DayKev
previously approved these changes
Nov 26, 2024
frutescens
previously approved these changes
Nov 28, 2024
Co-authored-by: innerthunder <[email protected]>
DayKev
force-pushed
the
bug/wimptrainer
branch
from
November 29, 2024 22:02
3eb53e0
to
b58719c
Compare
It was a simple fix, nevermind. |
Video of new method: wimp.out.multihit.test.mp4 |
DayKev
approved these changes
Nov 30, 2024
MokaStitcher
approved these changes
Nov 30, 2024
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes the user will see?
Activating Wimp Out or Emergency Exit on a boss pokemon (Guzma 115) will no longer cause the ability to trigger twice and cause 2 pokemon to stack on top of one another
Why am I making these changes?
Bug Thread: https://discord.com/channels/1125469663833370665/1290778513363959941
What are the changes from a developer perspective?
Screenshots/Videos
How to test the changes?
Basically this issue started happening due to Wimp Out and Emergency Exit triggering twice due to the interaction with the boss break bars. One for Multi-hit, which waits until the end of damage, and the other is just for general damage.
To prevent this I've added more guardrails around the applyAbAttrs to prevent this from happening again. Now there should be no overlap between the two applyAbAttrs.
I added an optional argument
move
todamageAndUpdate
inpokemon.ts
. This allows me to check forMultiHitAttr
I moved the multi-hit check to
move-effect-phase.ts
to utilize thelastHit
variable. This will make the effect more consistent rather than relying on hitCount or hitsLeft.Videos
Before
Multi-Hit Move
before_multihit.mp4
Multi-Lens
before_lens.mp4
Parental Bond
before_bond.mp4
After
Multi-Hit Move
yaboi_multihit.mp4
Multi-Lens
yaboi_lens.mp4
Parental Bond
yaboi_bond.mp4
Checklist
beta
as my base branchnpm run test
)npm run create-test
) or updated existing tests related to the PR's changes?Are there any localization additions or changes? If so: