Trouble with the mew glitch in Red

[loopytheone]

Hello all,

I restarted my old pokemon red game in my gameboy colour a couple of weeks ago for some glitching action and I'm having trouble with the extended mew glitch with a special stat of 196. I know from reading bulbapedia that it should give me PokeWTrainer but it's not playing nice. =(

Every time I've tried it (~20 times now) it's frozen before the start of the battle. I managed to get the screen to load past the black "start of battle" screen once and it displayed a trainer with a black box for myself and the trainer and a load of 9's on the screen. The trainer had 6 alternating "healthy" and "fainted" pokeballs and the screen froze after "9999999 wants to fight". Now, obviously this isn't PokeWTrainer and it kinda explains why my game freezes so much if it's trying to load some glitch battle instead.

I've never had a gameshark on that cartridge or gameboy before. Has anyone heard of this happening before? Or do they know why it's happening? Everything else in my game works perfectly.

Many thanks and sorry if this isn't the right place to post this. ^^;

Loopy

EDIT:: Actually, when I activate the TMTrainer effect via my .4's superglitch move it begins with both pokemon having poison status then falling to sleep, unlike the usually burn/frozen statuses. The pokemon that I'm battling become a normal level 57 hitmonchan if I catch it. I know that superglitch moves can do a lot of strange things but I've never heard to this happening to anybody else? I don't know if it's related to what I've put above but I thought I should mention it just in case. =)

[Torchickens]

Sept 15, 2011 8:23:09 GMT -5 loopytheone said:

Hello all,

I restarted my old pokemon red game in my gameboy colour a couple of weeks ago for some glitching action and I'm having trouble with the extended mew glitch with a special stat of 196. I know from reading bulbapedia that it should give me PokeWTrainer but it's not playing nice. =(

Every time I've tried it (~20 times now) it's frozen before the start of the battle. I managed to get the screen to load past the black "start of battle" screen once and it displayed a trainer with a black box for myself and the trainer and a load of 9's on the screen. The trainer had 6 alternating "healthy" and "fainted" pokeballs and the screen froze after "9999999 wants to fight". Now, obviously this isn't PokeWTrainer and it kinda explains why my game freezes so much if it's trying to load some glitch battle instead.

I've never had a gameshark on that cartridge or gameboy before. Has anyone heard of this happening before? Or do they know why it's happening? Everything else in my game works perfectly.

Many thanks and sorry if this isn't the right place to post this. ^^;

Loopy

EDIT:: Actually, when I activate the TMTrainer effect via my .4's superglitch move it begins with both pokemon having poison status then falling to sleep, unlike the usually burn/frozen statuses. The pokemon that I'm battling become a normal level 57 hitmonchan if I catch it. I know that superglitch moves can do a lot of strange things but I've never heard to this happening to anybody else? I don't know if it's related to what I've put above but I thought I should mention it just in case. =)

Hi loopy, welcome to the forums. Don't worry, you posted this in the right board, this is currently being used as a temporary forum for Glitch City Laboratories until the site is back online.

PokéWTrainer (0xC4) unfortunately causes the game to freeze when you encounter it on the opponents' side and/or can corrupt the battle in ways like that. This can occur with a lot of glitch Pokémon depending on the version and the Pokédex number (most notably Yellow Missingno.) Unfortunately all dex:205 (which includes PokéWTrainer) freeze the game in Red/Blue.

However, you can easily acquire a PokéWTrainer by doing the Trainer-Fly (Ditto trick/Extended Mew glitch) on Pokémon Yellow instead, and obtaining the equivalent glitch Pokémon X ゥ- xゥ (0xC4) dex:203 which doesn't freeze the game; and will become PokéWTrainer when traded over to English Red/Blue. Alternatively you can do the Johto guard glitch with Typhlosion, but that's harder.

Since X ゥ- xゥ shows a Pokédex entry when captured, you will have to capture it again, because all glitch Pokémon which show a Pokédex entry dex:152-255 and 0 become Rhydon after their Pokédex entry is shown.

P.S. You live in Nottingham? I live in Mansfield, small world huh?!

[loopytheone]

Sept 15, 2011 17:39:02 GMT -5 Torchickens said:

Hi loopy, welcome to the forums. Don't worry, you posted this in the right board, this is currently being used as a temporary forum for Glitch City Laboratories until the site is back online.

PokéWTrainer (0xC4) unfortunately causes the game to freeze when you encounter it on the opponents' side and/or can corrupt the battle in ways like that. This can occur with a lot of glitch Pokémon depending on the version and the Pokédex number (most notably Yellow Missingno.) Unfortunately all dex:205 (which includes PokéWTrainer) freeze the game in Red/Blue.

However, you can easily acquire a PokéWTrainer by doing the Trainer-Fly (Ditto trick/Extended Mew glitch) on Pokémon Yellow instead, and obtaining the equivalent glitch Pokémon X ゥ- xゥ (0xC4) dex:203 which doesn't freeze the game; and will become PokéWTrainer when traded over to English Red/Blue. Alternatively you can do the Johto guard glitch with Typhlosion, but that's harder.

Since X ゥ- xゥ shows a Pokédex entry when captured, you will have to capture it again, because all glitch Pokémon which show a Pokédex entry dex:152-255 and 0 become Rhydon after their Pokédex entry is shown.

P.S. You live in Nottingham? I live in Mansfield, small world huh?!

Ah, that's a relief, I'm glad I haven't posted wrong and annoyed anyone. Thank you so much for the info, that makes a lot more sense to me and I'll be sure to try it out when I get a copy of Yellow. ;D


Yep, I live Nottingham and I have friends in Mansfield! It's not very often I see someone else from the East Midlands online! Nottinghamshire representing, I guess!