Out of bounds: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens |
>Torchickens |
||
| Line 16: | Line 16: | ||
If the player goes beyond an x boundary, the map will loop until x equals the west or east boundary after which the connection will be loaded, and if it was invalid a freeze or Glitch Hell (Japanese Red/Green/Yellow running on emulators) will occur. The 'copies' of the maps are called [[phantom town]]s, as warps and signs do not work there, and people cannot be found there. |
If the player goes beyond an x boundary, the map will loop until x equals the west or east boundary after which the connection will be loaded, and if it was invalid a freeze or Glitch Hell (Japanese Red/Green/Yellow running on emulators) will occur. The 'copies' of the maps are called [[phantom town]]s, as warps and signs do not work there, and people cannot be found there. |
||
If the player goes beyond a y boundary, they will encounter |
If the player goes beyond a y boundary, they will encounter an [[Glitch City (Red, Blue, Yellow)#Out of bounds Glitch City|out of bounds Glitch City]] for a very high (very southerly) y position, and the same effects described above will happen for entering a north or south boundary. |
||
If the boundary was invalid, the game will freeze (or Glitch Hell may appear in Japanese Pokémon Red, Green and Yellow running on emulators). If the boundary was valid, the relevant location will be loaded (e.g. FF in Route 3 loads Pewter City) and the coordinates will be updated. |
If the boundary was invalid, the game will freeze (or Glitch Hell may appear in Japanese Pokémon Red, Green and Yellow running on emulators). If the boundary was valid, the relevant location will be loaded (e.g. FF in Route 3 loads Pewter City) and the coordinates will be updated. |
||