Meta-map script activation: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Sherkel mNo edit summary |
>Sherkel mNo edit summary |
||
| Line 2: | Line 2: | ||
{{Bulbapedia2|0 ERROR}} |
{{Bulbapedia2|0 ERROR}} |
||
'''Meta-map script activation''', previously known as '''walking lag glitch''', |
'''Meta-map script activation''', previously known as the '''walking lag glitch''', '''0 ERROR''', and '''Zero Error''' (due to error codes that may appear during the text box matching method,) refers to a set of [[glitch]]es in {{RBY}}. |
||
These glitches will modify the 'meta-map script' associated with a certain map, which is a special map script used to execute code on particular maps (one byte for each map). Unlike the temporary map scripts stored at D36E-D36F, meta-map scripts are usually permanent unless the script itself changes the meta-map script ID to a different value. They are also specific to each map, unlike the D36E-D36F address that is a pointer to anywhere in the current bank in the ROM, or RAM. |
These glitches will modify the 'meta-map script' associated with a certain map, which is a special map script used to execute code on particular maps (one byte for each map). Unlike the temporary map scripts stored at D36E-D36F, meta-map scripts are usually permanent unless the script itself changes the meta-map script ID to a different value. They are also specific to each map, unlike the D36E-D36F address that is a pointer to anywhere in the current bank in the ROM, or RAM. |
||