User:Princess Torchic ❤/List of collision oversights: Difference between revisions
>Torchickens (New page: {{Summary page}} {{Diverse}} {{Incomplete}} Within the Pokémon games, there are various examples of instances where the collision data of tiles have not been sufficiently coded. As such,...) |
>Torchickens m (Princess Torchic ❤ moved page User:Evie ✿/List of collision oversights to User:Princess Torchic ❤/List of collision oversights) |
(One intermediate revision by the same user not shown) | |
(No difference)
|
Latest revision as of 10:31, 8 December 2017
This article is a summary page for different variations of a glitches, etc. when talked about as a whole. |
Please note that such examples of glitches appear very commonly, hence it is unlikely that all examples would have been noted here. |
This article is incomplete. Please feel free to add any missing information about the subject. It is missing: {{{1}}}. |
Within the Pokémon games, there are various examples of instances where the collision data of tiles have not been sufficiently coded. As such, a player may be able to walk on to a tile that was not intended to be stepped on by the game developers. Also, a player may be blocked by a tile that he or she usually has the ability to walk on.
Other problems are often caused by objects or events which serve a purpose in changing the player's map coordinate, for example in the first generation of hand-held Pokémon games, if the player jumps off a ledge and an NPC is in the position that the player will land, this will give the player character's sprite a higher priority over the NPC's sprite, making it appear as if the player is standing on top of that NPC.