diff options
| -rw-r--r-- | Force-Set-battle-style-or-forbid-item-usage-in-battle.md | 22 |
1 files changed, 19 insertions, 3 deletions
diff --git a/Force-Set-battle-style-or-forbid-item-usage-in-battle.md b/Force-Set-battle-style-or-forbid-item-usage-in-battle.md index 801850c..24d3c8c 100644 --- a/Force-Set-battle-style-or-forbid-item-usage-in-battle.md +++ b/Force-Set-battle-style-or-forbid-item-usage-in-battle.md @@ -5,7 +5,8 @@ This tutorial explains how to force a battle style and forbid the use of items i 1. [Force a battle style](#1-force-a-battle-style) 2. [Forbid item usage](#2-forbid-item-usage) -3. [Implement the new battle types in a trainer battle](#3-implement-the-new-battle-types-in-a-trainer-battle) +3. [Implement a new battle type in a trainer battle](#3-implement-a-new-battle-type-in-a-trainer-battle) +4. [Optional: Fix the item prohibition text](#4-optional-fix-the-item-prohibition-text) ## 1. Force a battle style @@ -126,7 +127,7 @@ BattleMenu_Pack: Here, we are adding a check in order to skip the Battle Pack call, which would load the pack once selected. Similar to the link battle check already in the code, this new one will check whether we are using `BATTLETYPE_SETNOITEMS`. If so, we jump to `.ItemsCantBeUsed`, which skips the pack call and loads text saying that items can't be used. If you added the third constant, you would want the same check for that battle type here as well. -## 3. Implement the new battle types in a trainer battle +## 3. Implement a new battle type in a trainer battle Now that the battle types and checks have been implemented, it's time to add one to a trainer battle script. We'll use the battle with Red as an example. @@ -146,4 +147,19 @@ Red: startbattle ``` -Voilà! With that battle type set, the player won't be asked whether they would like to switch Pokémon after defeating one, regardless of which battle style has been selected in Options. If you would like to have both this and forbidden items in the same battle, swap out `BATTLETYPE_SET` for `BATTLETYPE_SETNOITEMS`.
\ No newline at end of file +Voilà! With that battle type set, the player won't be asked whether they would like to switch Pokémon after defeating one, regardless of which battle style has been selected in Options. If you would like to have both forced Set and forbidden items in the same battle, swap out `BATTLETYPE_SET` for `BATTLETYPE_SETNOITEMS`. If you added the third battle type that I mentioned (or any other), include it here in the same way. + + +## 4. Optional: Fix the item prohibition text + +You may want to take this opportunity to change the text used when you are unable to use items in battle. The original text states that "Items can't be used here." While this is appropriate in the Battle Tower, it sounds odd when used in proximity of other trainers that don't force Set, since the item prohibition is not proximity-based in that instance. + +Edit [data/text/battle.asm](../blob/master/data/text/battle.asm): + +```diff + BattleText_ItemsCantBeUsedHere: + text "Items can't be" +- line "used here." ++ line "used right now." + prompt +```
\ No newline at end of file |