8
edits
Glitch battle: Difference between revisions
→Examples: fixed
("Tile graphic" is a good way to describe this.) |
SlySamurott (talk | contribs) (→Examples: fixed) |
||
| Line 16: | Line 16: | ||
* [[4(h4?]] is the most appropriate example, since its encounter sequence clearly showcases all features of a glitch battle. | * [[4(h4?]] is the most appropriate example, since its encounter sequence clearly showcases all features of a glitch battle. | ||
* [[4 4]] crashes the game upon encounter. However, before the game crashes, it is possible to see the glitched battle screen for a brief moment. When it is sent out in a trainer battle, it severely | * [[4 4]] crashes the game upon encounter. However, before the game crashes, it is possible to see the glitched battle screen for a brief moment. When it is sent out in a trainer battle, it severely alters the game screen and freezes the game shortly afterwards. It shares these traits with two other glitch Pokémon, [[8B 4 8]] and [[ゥ' B]]. | ||
* [[Missingno.#Yellow forms|Yellow form Missingno.]]'s front sprite often crashes or freezes the game. It also | * [[Missingno.#Yellow forms|Yellow form Missingno.]]'s front sprite often crashes or freezes the game. It also heavily alters the music and affects graphics after returning to overworld. | ||
* [[♀ .]] slightly corrupts some memory addresses responsible for music and graphics, but keeps the game playable. | * [[♀ .]] slightly corrupts some memory addresses that are responsible for music and graphics, but generally keeps the game playable. | ||
* Certain glitch Pokémon, like [[PkMnaPkMnゥ ♂ fPkMnk]], crash the game instantly and do not give enough time to see any glitch battle effects. | * Certain glitch Pokémon, like [[PkMnaPkMnゥ ♂ fPkMnk]], crash the game instantly and do not give enough time to see any glitch battle effects. | ||