Pomeg data corruption glitch: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
m (Text replacement - "http://forums.glitchcity.info" to "https://forums.glitchcity.info") |
|||
Line 144:
=====Corruption initiators (increasing success chance)=====
If the player is unsuccessful with the glitch after many attempts, they may attempt to place different Pokémon next to the Pokémon applicable for the glitch, referred to as [[corruption initiator]]s for example they could try random Pokémon or (if the glitch was successful before) they could try placing a specific Caterpie known as "[
Another good corruption initiator is the in-game trade Plusle untouched but with all moves but Growl removed. This is a useful corruption initiator that is easy to get (if the player hasn't obtained the Plusle already). It is ideal for obtaining wrong Pokémon Eggs or double corruption, and is much quicker to get than the Caterpie.
Line 229:
If the player performs Pomeg data corruption glitch on a route with Trainers it can cause corruption of the player's challenge music, and/or corruption of their text (often long instances of "qÁF" in their text) or cause a full red screen. Sometimes after closing the text box (it may take a very long time for to finish printing it) it can cause a battle with a [[glitch Trainer]] to begin.
[
The same NPC may be used to trigger a 'super corruption glitch' in which the player's Pokémon, name, items, Pokédex data, play time and gender according to the save box is corrupted and saving may break the save, causing a black screen upon loading.
It is also [
{{youtube|QaPs2KZ7F70|ChickasaurusGL}}
Line 316:
After filling the Pokémon Storage System with Eggs and Bad Eggs, any unwanted Eggs and Bad Eggs created from Pomeg data corruption glitch can easily be removed with the [[Battle Tower inverse cloning glitch (Emerald)|Battle Tower inverse cloning glitch]] or [[Decamark specific glitches#fast inverse cloning glitch|fast inverse cloning]].
==External links==
*[
==Credits==
Voltage first discovered the sub-glitch to send out a Decamark in early 2011.
|