diff options
author | Rangi <35663410+Rangi42@users.noreply.github.com> | 2018-05-06 18:50:02 -0400 |
---|---|---|
committer | Rangi <35663410+Rangi42@users.noreply.github.com> | 2018-05-06 18:50:02 -0400 |
commit | 159102fbc3985a49a7bc6bed504af924f1997879 (patch) | |
tree | 980fc673d27c1d424912c00c0c379fa6f0c60ff1 /Add-a-new-TM.md | |
parent | a7735a40b2ddb339ddfe5fa69a24c108cc3441b1 (diff) |
Updated Add a new TM (markdown)
Diffstat (limited to 'Add-a-new-TM.md')
-rw-r--r-- | Add-a-new-TM.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Add-a-new-TM.md b/Add-a-new-TM.md index 3b78b6e..880c826 100644 --- a/Add-a-new-TM.md +++ b/Add-a-new-TM.md @@ -112,7 +112,7 @@ So far we've created a TM51 item and assigned it a move, but nothing can learn i - [lugia.asm](../blob/master/data/pokemon/base_stats/lugia.asm): `..., NIGHTMARE, FLY, ...` → `..., NIGHTMARE, AEROBLAST, FLY, ...` - [mew.asm](../blob/master/data/pokemon/base_stats/mew.asm): `..., NIGHTMARE, CUT, ...` → `..., NIGHTMARE, AEROBLAST, CUT, ...` -The learnable moves have to be in the same order as the `add_tm` lines, since that's what they're referencing: the `tmhm` macro turns `NIGHTMARE` into` `NIGHTMARE_TMNUM`, `CUT` into `CUT_TMNUM`, etc, and then processes them to efficiently store learnsets. (We'll get to the details of how it works next.) +The learnable moves have to be in the same order as the `add_tm` lines, since that's what they're referencing: the `tmhm` macro turns `NIGHTMARE` into `NIGHTMARE_TMNUM`, `CUT` into `CUT_TMNUM`, etc, and then processes them to efficiently store learnsets. (We'll get to the details of how it works next.) Anyway, that's all: |