Game:

Pokémon FireRed and LeafGreen (2004)

Duration: 6:25

1,743 views

87

Notes:

This is from some of Riley's Generation III trade evolution data. Mirrored here:

https://glitchcity.wiki/File:Decamark_trade_evolution_examples_Firered.png
https://glitchcity.wiki/File:Decamark_trade_evolutions_examples_Emerald.png

This video assumes you got a 0x939E Decamark (for a Glitzer Popping corruption that would be 147 Attack, 158 HP for a substructure ID 7 e.g. Dots and Seasor for mod 24) but here, inside an Egg (e.g. via arbitrary code execution in Emerald). Although Riley evolved it outside of the Egg, when I tried it it froze the game (even though their data said Shiny 0x939E outside an Egg doesn't freeze), so there may be another unseen condition in which it freezes (and the Shininess data may be in question).

In FireRed/LeafGreen but not Emerald, it will evolve upon trade into Lugia. The 0x939E I generated to be Shiny, but due to the below it ceased being Shiny after hatching on the new game. It seems it remained its data for the old Shininess after evolving within the Egg.

The Lugia inside the Egg is Shiny unhatched but not hatched because it was from an Emerald game with a different TID and SID; the relationship between the TID, SID and personality value is used to determine Shininess https://bulbapedia.bulbagarden.net/wiki/Shiny_Pok%C3%A9mon#Generation_III_onward but the TID and SID is overwritten (to match the FireRed game) upon hatching and it ceases to be Shiny.

Trying to view Lugia causes a menu glitch (previously only observed from bad HP values), so you can overwrite almost all of its moves in the Day Care to fix its moves and make it stable. You may be able to get away with levelling it up in battle as well if it only has one glitch move, where in this video it caused a menu glitch but it could be cancelled out and the first move (a glitch move) was automatically overwritten.

Other Statistics