Wrong pocket TMs and HMs: Difference between revisions
m
Made the descriptions of TM21 and TM25 refer to eachother, instead of themselves
m (Text replacement - "{| border=1 width="100%" align=left class="sortable" style="background:#f0f0f0; border:1px solid #000000; border-collapse:collapse;" |-style="background: silver;"" to "{| class="wikitable sortable"") |
m (Made the descriptions of TM21 and TM25 refer to eachother, instead of themselves) |
||
| (One intermediate revision by one other user not shown) | |||
Line 7:
{|
|-
|
Line 21 ⟶ 20:
| D0 || 208 || TM17 || Gold/Silver (English) || Executes arbitrary code from FA47 (Echo RAM for DA47, which is the caught data for party Pokémon 1. The player can make a jump to somewhere more useful (via C3 yy xx), using Pokémon 1 as a [[slide Pokémon]] if necessary.
|-
| D4 || 212 || TM21 || Crystal (English) || Executes arbitrary code from FA69 (Echo RAM for DA69, which is somewhere in the expanded Balls pocket; like
|-
| D8 || 216 || TM25 || Crystal (English) || Executes arbitrary code from FA69 (Echo RAM for DA69, which is somewhere in the expanded Balls pocket; like
|-
| D8 || 216 || TM25 || Gold/Silver (English) || Executes arbitrary code from FA6A (Echo RAM for DA6A, and DA6A is the least significant Defense EV byte of the second Pokémon in the party. The Speed EVs word follows, and the player can make a jump to somewhere more useful (via C3 yy xx). This may be possible without trading, but getting the exact EVs would be tedious and it would be hard to keep track of them without a memory viewer. Through arbitrary code execution in {{RBY}}, the second Pokémon may be manipulated to have Defense and Speed EV values that the player desires.
| |||