GlitchDex/GS:000: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
VisualWikitext
 
Line 132: Line 132:


==Notes==
==Notes==
When this {{GNS|Pentamark}} is encountered in battle, it may cause corruption of the memory beginning from $D000.
When this {{GNS|Pentamark}} is encountered in battle, the area between $D000 and $D0FF is corrupted with $D1 values due to [[Invalid Sprite Transfer Corruption]].


This may change the battle style to a Link Battle. This disables the use of items and making a turn will result in a "Waiting...!" message which may never end. The Link Battle freeze can be avoided by setting the memory address D042 to 00 (or by using the [[cheating device|GameShark]] code 010042D0).
Among other things, this changes the battle style to a Link Battle. This disables the use of items and making a turn will result in a "Waiting...!" message which may never end. The Link Battle freeze can be avoided by setting the memory address D042 to 00 (or by using the [[cheating device|GameShark]] code 010042D0).


If the [[Cheating device|GameShark]] code 0100EDD0 is enabled from within the battle, then it is possible to capture the {{GNS|Pentamark}} and register its Pokédex entry if bit 7 of $DC03 is not set; but unexpected battle behavior may follow the nickname prompt; reportedly including an enemy Trainer switching Pokémon, or {{GNS|Pentamark}} fleeing.
If the [[Cheating device|GameShark]] code 0100EDD0 is enabled from within the battle, then it is possible to capture the {{GNS|Pentamark}} and register its Pokédex entry if bit 7 of $DC03 is not set; but unexpected battle behavior may follow the nickname prompt; reportedly including an enemy Trainer switching Pokémon, or {{GNS|Pentamark}} fleeing.
Retrieved from "https://glitchcity.wiki/wiki/GlitchDex/GS:000"