Out of bounds: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens |
>ISSOtm m (→In Generation I: Super Glitch also may cause tile corruption) |
||
| Line 2: | Line 2: | ||
==In [[bp:Generation I|Generation I]]== |
==In [[bp:Generation I|Generation I]]== |
||
Going out of bounds is possible with a [[walk through walls]] glitch or cheat, the [[dokokashira door glitch]] via tile corruption, or [[arbitrary code execution]]. |
Going out of bounds is possible with a [[walk through walls]] glitch or cheat, the [[dokokashira door glitch]] or [[Super Glitch]] via tile corruption, or [[arbitrary code execution]]. |
||
In [[bp:Generation I|Generation I]], every map has a boundary for each connection. These include x position (memory address D362 or D361 in Yellow) boundaries that are one tile wide and infinitely tall, and y position (memory address D361 or D360 in Yellow) boundaries that are one tile tall and infinitely wide. The y position increases for more southerly values, unlike other conventions. |
In [[bp:Generation I|Generation I]], every map has a boundary for each connection. These include x position (memory address D362 or D361 in Yellow) boundaries that are one tile wide and infinitely tall, and y position (memory address D361 or D360 in Yellow) boundaries that are one tile tall and infinitely wide. The y position increases for more southerly values, unlike other conventions. |
||