diff options
| author | Idain <luiscarlosholguinperez@outlook.com> | 2021-09-13 07:27:22 -0400 |
|---|---|---|
| committer | Idain <luiscarlosholguinperez@outlook.com> | 2021-09-13 07:27:22 -0400 |
| commit | e012fe41d421711a3cb61b66e2f563ef91470b9f (patch) | |
| tree | b72d58cb6383149e98f45636aad657220d3355d4 | |
| parent | 0dedd47b6ec0a898a6c41f91a3bb7c76bd94d572 (diff) | |
Fix missing diff.
| -rw-r--r-- | Make-new-battle-text-to-distinguish-status-move-misses-and-fails.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/Make-new-battle-text-to-distinguish-status-move-misses-and-fails.md b/Make-new-battle-text-to-distinguish-status-move-misses-and-fails.md index 035fa2b..ef03ebe 100644 --- a/Make-new-battle-text-to-distinguish-status-move-misses-and-fails.md +++ b/Make-new-battle-text-to-distinguish-status-move-misses-and-fails.md @@ -1,4 +1,4 @@ -In Generation 2, it is hard to know if the status move missed or can't affect the opponent (either due to being statused already or status immunity) due to the ambiguity of the move failure text. With this tutorial, we can fix this. +In Generation 2, it is hard to know if a status move missed or didn't affect the opponent (either due to being statused already or status immunity) due to the ambiguity of the move failure text. With this tutorial, we can fix this. ## Contents @@ -27,11 +27,11 @@ AttackMissed2Text: ... ``` -You may not add this separate text for missing status moves. Just remember to use either `AttackMissedText` or `AttackMissed2Text` when `AvoidStatusText` is used in this tutorial. They are identical anyway. +You must not add this separate text for missing status moves. Just remember to use either `AttackMissedText` or `AttackMissed2Text` when `AvoidStatusText` is used in this tutorial. They are identical anyway. Next, edit [engine/battle/effect_commands.asm](../blob/master/engine/battle/effect_commands.asm): -``` +```diff ... BattleCommand_Poison: @@ -187,7 +187,6 @@ BattleCommand_Paralyze: ... - .dont_sample_failure - ld a, BATTLE_VARS_STATUS_OPP - call GetBattleVarAddr @@ -203,6 +202,6 @@ BattleCommand_Paralyze: jp StdBattleTextbox ``` -That's it! Now we can know if the status move missed or can't affect the opponent (either due to being statused already or status immunity)! +That's it! Now we can know if the status move either missed or doesn't affect the opponent (either due to being statused already or status immunity)! 
\ No newline at end of file |