summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Add-a-new-Fairy-type.md18
-rw-r--r--Hard-coded-logic.md9
2 files changed, 19 insertions, 8 deletions
diff --git a/Add-a-new-Fairy-type.md b/Add-a-new-Fairy-type.md
index 9d2883f..e89a620 100644
--- a/Add-a-new-Fairy-type.md
+++ b/Add-a-new-Fairy-type.md
@@ -1,13 +1,15 @@
This tutorial is for how to add a new type for Pokémon or moves. As an example, we'll add the Fairy type from Gen 7.
-In short, we need to update all of these files:
-- [constants/type_constants.asm](../blob/master/constants/type_constants.asm)
-- `TypeNames` in [data/types/names.asm](../blob/master/data/types/names.asm)
-- `TypeMatchups` in [data/types/type_matchups.asm](../blob/master/data/types/type_matchups.asm)
-- `PokedexTypeSearchConversionTable` in [data/types/search_types.asm](../blob/master/data/types/search_types.asm)
-- `PokedexTypeSearchStrings` in [data/types/search_strings.asm](../blob/master/data/types/search_strings.asm)
-- `TypeBoostItems` in [data/types/type_boost_items.asm](../blob/master/data/types/type_boost_items.asm)
+## Contents
+
+1. [Add a `FAIRY_T` constant](#1-add-a-fairy_t-constant)
+2. [Update `TypeNames`](#2-update-typenames)
+3. [Update `TypeMatchups`](#3-update-typematchups)
+4. [Update `PokedexTypeSearchConversionTable` and `PokedexTypeSearchStrings`](#4-update-pokedextypesearchconversiontable-and-pokedextypesearchstrings)
+5. [Update Pokémon types](#5-update-pokémon-types)
+6. [Update move types](#6-update-move-types)
+7. [Change `POLKADOT_BOW` to boost `FAIRY_T` moves](#7-change-polkadot_bow-to-boost-fairy_t-moves)
## 1. Add a `FAIRY_T` constant
@@ -141,7 +143,7 @@ Edit the type columns in [data/moves/moves.asm](../blob/master/data/moves/moves.
- `MOONLIGHT`: `NORMAL` → `FAIRY_T`
-## 5. Change `POLKADOT_BOW` to boost `FAIRY_T` moves
+## 7. Change `POLKADOT_BOW` to boost `FAIRY_T` moves
At this point we're technically done: all the canon aspects of the Fairy type are implemented. (If you want to add new Fairy-type Pokémon or moves, check out different tutorials.) But there's no held type-boosting item for it, and Gen 2 happens to have the unavailable `POLKADOT_BOW` item that boosts Normal moves like `PINK_BOW`, so let's change it to boost Fairy moves instead.
diff --git a/Hard-coded-logic.md b/Hard-coded-logic.md
index a016019..d8219a4 100644
--- a/Hard-coded-logic.md
+++ b/Hard-coded-logic.md
@@ -1,6 +1,15 @@
Much of the game logic can be changed via the files in [data/](../blob/master/data/), but some things are hard-coded and can be tricky to find. This page lists things that may trip you up when hacking.
+## Contents
+
+- [`RIVAL1`'s first Pokémon has no held item](#rival1s-first-pokémon-has-no-held-item)
+- [`RIVAL1` and `RIVAL2` don't print their trainer class in battle](#rival1-and-rival2-dont-print-their-trainer-class-in-battle)
+- [Some trainer classes have different battle music](#some-trainer-classes-have-different-battle-music)
+- [Some maps don't display a location sign](#some-maps-dont-display-a-location-sign)
+- [Outdoor maps within indoor maps don't confuse Dig or Escape Rope](#outdoor-maps-within-indoor-maps-dont-confuse-dig-or-escape-rope)
+
+
## `RIVAL1`'s first Pokémon has no held item
This is caused by `InitEnemyTrainer` in [engine/battle/core.asm](../blob/master/engine/battle/core.asm):