GTS morphing glitch (Generation IV): Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
old->Torchickens mNo edit summary |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{poorqualityimage}} |
{{poorqualityimage}} |
||
{{researchneeded|Confirm if the glitch happens in other games with a video.}} |
{{researchneeded|Confirm if the glitch happens in other games with a video.}} |
||
<br clear=left> |
|||
[[Image:GTS species glitch.png|270px|thumb|right|A Mew, portrayed as a Torterra]] |
[[Image:GTS species glitch.png|270px|thumb|right|A Mew, portrayed as a Torterra]] |
||
| Line 6: | Line 7: | ||
The cause of this glitch is unknown. |
The cause of this glitch is unknown. |
||
{{clr}} |
|||
[[Category:Generation IV glitches]] |
[[Category:Generation IV glitches]] |
||
[[Category:Global Trade System glitches]] |
[[Category:Global Trade System glitches]] |
||
[[Category:Glitches that no longer occur]] |
|||
Latest revision as of 15:53, 2 January 2018
An image or multiple images in this article are of poor quality and need replacing.
| |
|
If possible, please reupload the image(s) at emulator quality, without changing the emulator's resolution. An image from a capture card would also be an improvement to an image taken from a camera. |
More research is needed for this article.
| |
|
Reason given: Confirm if the glitch happens in other games with a video. |
The GTS morphing glitch referred to instances in Pokémon Diamond and Pearl when a Pokémon found through the 'Seek Pokémon' option of the Global Trade System (now impossible to access in Generation IV due to Nintendo Wi-Fi Connection being discontinued from May 20th 2014) is displayed as the wrong Pokémon, with the picture of another Pokémon and often a nickname of that Pokémon. It does not change the original species name of that Pokémon however, resulting in many reports of players seeing Pokémon like a Mew with the nickname and picture of 'TORTERRA'.
The cause of this glitch is unknown.