Glitches.

An NPC's pathing routine has two loops with no bound between them. Stand on one specific unreachable tile and the search loop walks off the end of a four-entry table, wraps the whole 64K address space, and the copy loop starts reading 898 bytes of ROM graphics data as a movement script — landing on a wild battle against a level-0 Dragonite with no scripted trigger behind it. Seventeen years documented by others; this is our own reproduction, byte for byte, on TerminalGB's core.

An evolution-table lookup has no bounds check, so any out-of-range species byte reads past the table and evolves into whatever ROM garbage it lands on — predictable, not random, since the garbage never changes. Two real ways in: a trainer's own chosen name, routed through the Old Man's catching demo and one coastal tile; or a modified link partner, which can hand it over in an ordinary trade and have it evolve, unnoticed, at the next battle won.

A trainer who spots the player on the frame they faint advances the map's own script before the blackout warp fires. The script index survives the warp and the heal, and hands the player a trainer battle the moment they walk back onto the tile it happened on — the community's trainer escape glitch, caught here in a run nobody set up for it.