Bad clone glitch: Difference between revisions

Jump to navigation Jump to search
m
Fixed a word.
(→‎Obtaining a bad clone: Removing the stress on "very difficult")
m (Fixed a word.)
Line 5:
Broadly speaking, the term "bad clone" includes two kinds of glitch Pokémon:
* A "real" bad clone, which is an [[unstable hybrid Pokémon]]. Such a bad clone can be stabilized into a [[?????]], enabling many other glitches such as [[????? party overloading]] or [[Time Capsule exploit]]. It also has an unterminated nickname, and thus can usually be used as a "friendly clone" if desired, although the timing window for getting a "real" bad clone is usually much tighter than that for getting a "friendly clone".
* A "friendly clone" (a term from the speedrunning community<ref>[https://www.speedrun.com/pkmncrystal/guide/axd5j Pokémon Crystal any% guide] by entrpntr</ref>), which is normal in every aspect except for its [[Unterminated name Pokémon (Generation II)|unterminated nickname]]. There is no known way to exploit a "friendly clone" in Gold/Silver, mainly due to stricter error checking for nicknames in those namesversions. However, in Crystal, a "friendly clone" can either be exploited for [[0x1500 control code arbitrary code execution]], or for simple buffer overflow (which can give the player a "real" bad clone).
 
Generally, a "real" bad clone is more exploitable, but also much more difficult to obtain. Technically there are other possible kinds of bad clones, such as one with correct species bytes but no moves<ref>[https://pokemon-speedrunning.github.io/speedrun-routes/#/gen-2/gold-silver/main-any/silver-no-collision-route/ Pokemon Silver Any% No Collision Route]</ref>, although they are even more unlikely to appear. The bad clone glitch can also be used to create unstable hybrids between valid Pokémon, but such unstable hybrids are not known to be game-breaking in any way.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu