Anonymous user
AreaDex/RB:231: Difference between revisions
→How the item swap effects and the party menu trick works
Line 34:
==How the item swap effects and the party menu trick works==
Items beyond slot 20 represent unrelated memory addresses, which are really just extrapolated beyond the end of the list. Setting 0xD35E to 0xE7 with the TM31 x1 in item 33 sets W_CURMAP (D35E) to this glitch map, but this alone only changes the map number partially loading data such as the Town Map name and map bank. Therefore, the TM41 x 79 in item 41 sets W_MAPSCRIPTPTR (D36E-D36F) to pointer 41 12 (1241). This pointer was chosen because at 1241 is the routine LoadMapData, which is documented [https://github.com/pret/pokered/blob/bbb0e7e82deb6741f75a12b48f81076d92f5d9dc/home/overworld.asm here] in the Pokémon Red disassembly project and for some reason bypasses a freeze from entering the glitch map directly from an entrance or exit, or as a map connection.
When the new map script for this glitch map (EAF1 (Echo RAM for CAF1)) runs, typically the player is fortunate not to have the game freeze up to EC2B (Echo RAM for CC2B) where having the cursor on the 202th Pokémon beforehand writes 0xC9 to CC2B (EC2B). This address wPartyAndBillsPCSavedMenuItem stores the Pokémon -1, so the 202nd (0xCA) Pokémon is considered as 201 (0xC9). This is relevant because 0xC9 is the ret opcode; since the player hasn't adjusted the stack this will terminate the code.
| |||