Glitch City Laboratories Archives

1. Turn on the gameshark code
2. Get into a wild pokemon battle
3. Right before having the black screen that transitionate between the overworld and battle screen, turn off the gameshark (This will cause the glitch pokemon to be without the trainer and take the form of the pokemon that it was supposed to be encounterd temporaly). This trick will never cause the game to crash except FA-FF (this can happen)
4. Before catching or defeating the glitch, turn the gameshark code back on.
5. The pokemon you will catch (unless converted into RHYDON) will be the glitch pokemon (there is no fusing, you will really catch the glitch pokemon like C7 and below)

I've confirmed that this works.

I've also confirmed that "a" is a pain in the ass to battle!  It won't let me attack after I've selected an attack.  I'd really like to see someone delve into the inner workings of "a" and see why it spawns so many text boxes, for one thing.

It's due to an improperly terminated name.  The game looks for HEX $50 before it can terminate a name.

There are various other glitches that have longer names than what's allowed too btw.

1. Turn on the gameshark code
2. Get into a wild pokemon battle
3. Right before having the black screen that transitionate between the overworld and battle screen, turn off the gameshark (This will cause the glitch pokemon to be without the trainer and take the form of the pokemon that it was supposed to be encounterd temporaly). This trick will never cause the game to crash except FA-FF (this can happen)
4. Before catching or defeating the glitch, turn the gameshark code back on.
5. The pokemon you will catch (unless converted into RHYDON) will be the glitch pokemon (there is no fusing, you will really catch the glitch pokemon like C7 and below)

I've confirmed that this works.

I've also confirmed that "a" is a pain in the ass to battle!  It won't let me attack after I've selected an attack.  I'd really like to see someone delve into the inner workings of "a" and see why it spawns so many text boxes, for one thing.

It's due to an improperly terminated name.  The game looks for HEX $50 before it can terminate a name.

1. Turn on the gameshark code
2. Get into a wild pokemon battle
3. Right before having the black screen that transitionate between the overworld and battle screen, turn off the gameshark (This will cause the glitch pokemon to be without the trainer and take the form of the pokemon that it was supposed to be encounterd temporaly). This trick will never cause the game to crash except FA-FF (this can happen)
4. Before catching or defeating the glitch, turn the gameshark code back on.
5. The pokemon you will catch (unless converted into RHYDON) will be the glitch pokemon (there is no fusing, you will really catch the glitch pokemon like C7 and below)

I've confirmed that this works.

I've also confirmed that "a" is a pain in the ass to battle!  It won't let me attack after I've selected an attack.  I'd really like to see someone delve into the inner workings of "a" and see why it spawns so many text boxes, for one thing.

It's due to an improperly terminated name.  The game looks for HEX $50 before it can terminate a name.

That was what I thought.

But menu commands don't respond properly even when a's name isn't being displayed.