[Balance] Adjust Relevant Abilities to Match Lures #4231
Merged
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?
Abilities that affect double battle encounter chance (
Illuminate
,No Guard
, andArena Trap
) will now match the effects of lures; that is, the multiplier applied to the base double battle encounter chance will be increased from double to quadruple.Why am I making these changes?
With the changes made to lures, it was intended for the list of abilities that provide the same effect to match the increase in the double battle chance multiplier.
What are the changes from a developer perspective?
Documentation was added to the
DoubleBattleChanceAbAttr
class to match theDoubleBattleChanceBoosterModifier
's documentation since they essentially provide the same effect.Unit tests were added for the relevant abilities to test the increase in double battle encounter chance along with their other individual effects. Note that one of the tests for
Arena Trap
was marked astodo
with a comment due to #935.Although it ended up not being needed for the unit tests, the calculations done for double battle chance were moved into their own function in the case that spying is needing later on for other unit tests.
Screenshots/Videos
N/A
How to test the changes?
The unit tests essentially cover changes, but using an override for ability can be used to manually test.
Checklist
beta
as my base branch[ ] If I have text, did I make it translatable and add a key in the English locale file(s)?npm run test
)[ ] Are the changes visual?[ ] Have I provided screenshots/videos of the changes?