Jump to content

Bad clone glitch: Difference between revisions

Clarified that both real bad clones and friendly clones (in Crystal) are useful in the introduction.
No edit summary
(Clarified that both real bad clones and friendly clones (in Crystal) are useful in the introduction.)
Line 1:
{{Major glitches}}
{{PRAMA|bad-clone-trick}}
The '''bad clone glitch''' is a [[natural glitch]] in {{GSC}} that allows the player to obtain an [[unstablea hybridglitch Pokémon]] known as a '''bad clone'''., Thewhich badin clone can be stabilized into a [[?????]],turn enablingenables many othergame-breaking glitches such as [[????? party overloading]] or [[Time Capsule exploit]]. The bad clone glitch is named as such because its procedure is similar to the [[Pokémon cloning (Generation II)|Gold/Silver/Crystal cloning glitch]], the only essential difference being the reset timing; indeed, it can happen by accident when doing "normal" cloning.
 
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 names. 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.
 
==Obtaining a bad clone==
Line 72 ⟶ 78:
{{main|Unterminated name Pokémon (Generation II)}}
Bad clones with unterminated names can also be used for various other exploits, notably [[0x1500 control code arbitrary code execution]].
 
== References ==
<references />
 
[[Category:Generation II glitches]]
Cookies help us deliver our services. By using our services, you agree to our use of cookies.