Glitch City: Difference between revisions

m
Line 24: Line 24:
The reason the player may find themselves in Glitch City upon exiting the gate is because the door that would lead out to [[Fuchsia City]] is coded so that the warp points to warp 4 on the last map the player was on. This would work perfectly normally; however, many areas in Generation I [[Kanto]] lack a warp 4, and so the glitch goes through. The maps that have a warp 4—[[Celadon City]], [[Cerulean City]], [[Lavender Town]], [[Saffron City]], [[Fuchsia City]], [[Viridian City]], [[Pewter City]], [[Cinnabar Island]]<!--I've seen videos of it working here on the water right against the coast, but I don't know if that goes for everywhere else in the city--> and [[Vermilion City]]—do not result in a Glitch City, instead taking the player to wherever the warp 4 is and letting them leave it normally.
The reason the player may find themselves in Glitch City upon exiting the gate is because the door that would lead out to [[Fuchsia City]] is coded so that the warp points to warp 4 on the last map the player was on. This would work perfectly normally; however, many areas in Generation I [[Kanto]] lack a warp 4, and so the glitch goes through. The maps that have a warp 4—[[Celadon City]], [[Cerulean City]], [[Lavender Town]], [[Saffron City]], [[Fuchsia City]], [[Viridian City]], [[Pewter City]], [[Cinnabar Island]]<!--I've seen videos of it working here on the water right against the coast, but I don't know if that goes for everywhere else in the city--> and [[Vermilion City]]—do not result in a Glitch City, instead taking the player to wherever the warp 4 is and letting them leave it normally.


Due to warp-breaking, of course, this means that Glitch City is nothing more than a corrupted version of whatever map the player was on when he or she ran out of time. When the [[Town Map]] is viewed in Glitch City, the map will say that the player is in the area they were in just before entering Glitch City, because they technically are in the area, just a corrupted version of it. This is why the Glitch City found by running out on {{rt|17|Kanto}} will cause the player to constantly walk downward and why attempting to use the [[Bicycle]] results in the message "You can't get off here.", and why wild Pokémon data is the same as that of the map that the player entered Glitch City from.
Due to warp-breaking, of course, this means that Glitch City is nothing more than a corrupted version of whichever map the player was on when he or she ran out of time. When the [[Town Map]] is viewed in Glitch City, the map will say that the player is in the area they were in just before entering Glitch City, because they technically are in the area, just a corrupted version of it. This is why the Glitch City found by running out on {{rt|17|Kanto}} will cause the player to constantly walk downward and why attempting to use the [[Bicycle]] results in the message "You can't get off here.", and why wild Pokémon data is the same as that of the map that the player entered Glitch City from.


The dimensions of the source map are apparently preserved: going too far in any direction while in a Glitch City will cause the player to walk outside of the map, thus crashing the game. The only crash-free Glitch City is that of [[Pallet Town]], which does not allow the player to move at all. {{eng|Pokémon Stadium}}'s [[Game Boy Tower]] mistakes such crashes for a corrupted game.
The dimensions of the source map are apparently preserved: going too far in any direction while in a Glitch City will cause the player to walk outside of the map, thus crashing the game. The only crash-free Glitch City is that of [[Pallet Town]], which does not allow the player to move at all. {{eng|Pokémon Stadium}}'s [[Game Boy Tower]] mistakes such crashes for a corrupted game.
52

edits