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 partly 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)

As far as I can remember, it's not even that smart. I was reading iimarckus' disassembly and it almost looked more like this subroutine (the one that loads the front sprite to show the dex information) was changing the index number without the caller even expecting it was doing it. I'm really quite bad at assembly of any sort, but I could look at it again to see what was going on. My guess is it doesn't fill in both index numbers at the same time and copies the Rhydon ID after it has shown the dex data and the dex has already "corrected" the index number. So there still is a glitch, but it's that the Pokémon give subroutine expects that the dex code will never change the index number, which would be a pretty reasonable expectation to make and holds for all real Pokémon. I'm a bit surprised they even bothered to put that check code in. --FSX (talk) 20:22, 22 June 2014 (UTC)

More to this glitch

You can turn a glitch Pokémon into the Rhydon hybrid without having to view the dex entry. Just deposit it in the PC, view its stats, and withdraw it. I've actually done this plus the Day Care method to switch my Missingno. between its normal form and the Rhydon hybrid in order to teach it Rock Slide and Hyper Beam. Worth adding to the article?- unsigned comment from Missingno. Master (talk • contribs) 18:09, 8 January 2015 (UTC)

Yes, don't see why not. --Chickasaurus (talk) 18:50, 8 January 2015 (UTC)

I think you have to view the stats multiple times for it to turn into a Rhydon. At least I have to do that. Mattjod (talk) 22:52, 13 May 2016 (UTC)

Number

The index number in gen 1 go from 1 to 190. which include the 151 regular pokemon and 49 glitch pokemon. Is the Pokedex number a separate internal variable or should this article (and at least also the Rhydon one) should be changed to talk about the 1-190 range?--Nngnna (talk) 13:44, 5 May 2020 (UTC)

Yes, index numbers and Pokédex numbers are separate. But this glitch is based on Pokédex numbers. Some glitch Pokémon have Pokédex numbers that are not between 1 and 152; as an error handler, the game tries to turn such Pokémon into Rhydon (the Pokémon whose index number is 0). --SnorlaxMonster 14:29, 5 May 2020 (UTC)