-
-
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
[Hotfix] Allow Fake Out to be used at the start of every wave again #4105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 🚀
Please test with mat block too |
Mat Block also works. |
@@ -23,6 +23,16 @@ export class BattleEndPhase extends BattlePhase { | |||
this.scene.unshiftPhase(new GameOverPhase(this.scene, true)); | |||
} | |||
|
|||
/** | |||
* Allow Fake Out and First Impression to be used at the start of every wild battle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you just want to make a change to two specific moves wouldn't this make more sense as a move attribute rather than doing something that might cause unintended behavior by manually changing a Pokemon's turns out?
What are the changes the user will see?
Fake Out and First Impression can be used at the start of every wave.
Why am I making these changes?
Request from @damocleas due to player feedback.
What are the changes from a developer perspective?
The active Pokémon's turn count is set to 1 at the start of every wave, so first-turn-only moves won't fail.
How to test the changes?
npm run test fake_out
Checklist
[ ] I'm usingbeta
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?