Talk:Rhydon glitch

Not actually a glitch

Unlike most glitches, which actually are glitches, the Rhydon "glitch" is actually error-handling code working as designed. It produces odd results, but it's the intended behavior of the code. --FSX (talk) 17:56, 7 June 2014 (UTC)

I'd support a move to something like the Rhydon error handler. I inquired about it on the GCL forums, and TheZZAZZGlitch provided proof here, the game definitely checks if the Pokédex number is 0, then checks if the Pokédex number is less than 152. --Chickasaurus (talk) 15:29, 10 June 2014 (UTC)

The fact that it becomes an "unstable" hybrid Pokemon if sent to Bill's PC after being caught still sounds like a "glitch" to me, and not just some benign "error handler". Is an unstable hybrid really "intended behavior"? Tiddlywinks (talk) 15:47, 10 June 2014 (UTC)

You're likely right. In relation to the move, the 'Rhydon glitch' is still error handling behaviour, just with a possible oversight or bug, so I still think it should be moved, maybe just with a note that it seems to be glitchy. (I agree with you with the theory that the Pokémon becoming an unstable hybrid when (and only when) it is sent to a box is not intended behaviour).

To clarify what happens (in case you don't know), there are two and not one species bytes for each Pokémon in the party or stored Pokémon data structure. What happens when you catch say a ▶ A, you have a full party, and you haven't enabled it capture flag? It gets sent to the box as 'RHYDON', though DA81 is changed to 01 but DA96 is not; it is left at BF, which is ▶ A's index number. It is still the glitch Pokémon in the way that it uses its in-battle palette and will revert to the glitch Pokémon when it is taken into Daycare and out again.

I feel that not setting both species bytes would be an easy mistake for Game Freak to make. --Chickasaurus (talk) 18:42, 10 June 2014 (UTC)