Out of bounds: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Bbbbbbbbba m (→Technical Explanations: typo) |
>Bbbbbbbbba m (→In Generation I: A word.) |
||
| Line 4: | Line 4: | ||
In [[bp:Generation I|Generation I]], the player's coordinate on the map is represented by two bytes, the X coordinate (horizontal position; east is larger; $D362 in R/B, or $D361 in Yellow) and the Y coordinate (vertical position; south is larger; $D361 in R/B, or $D360 in Yellow). Therefore, the entire "map space" available to the player in theory is a 256*256 square. |
In [[bp:Generation I|Generation I]], the player's coordinate on the map is represented by two bytes, the X coordinate (horizontal position; east is larger; $D362 in R/B, or $D361 in Yellow) and the Y coordinate (vertical position; south is larger; $D361 in R/B, or $D360 in Yellow). Therefore, the entire "map space" available to the player in theory is a 256*256 square. |
||
Since byte operations overflow and underflow normally, the left side and right side are "connected together", and so |
Since byte operations overflow and underflow normally, the left side and right side are "connected together", and so are the top side and the bottom side, although the player cannot directly step through the boundary without triggering a (possibly invalid) map connection. |
||
===Accessing out of bound areas=== |
===Accessing out of bound areas=== |
||