Hey Alaistar, welcome to the forums!
There are a lot of glitches in the Pokémon games that you can already try out, such as the old man trick
, Trainer-Fly glitch
and "CoolTrainer" type move corruption
, that might be nice for you to experiment with. My approach is when you try a completely new glitch is to follow the steps carefully. Then once you have done the glitch a few times, it will become more natural to exploit.
You do not need to have much knowledge of programming or the game's inner workings to do your own research. By doing glitches a little differently, you can discover things for yourself (such as returning to the route you escape from with a Trainer-Fly immediately to avoid battles on that route).
The big list
is a valuable so you can know what characters in your name will give which Pokémon for the old man trick, or what Special stats for the Trainer-Fly glitch give which Pokémon, etc.
One useful thing if you are playing on an emulator is to refer to or learn Pokémon Red and Blue's memory structure
(not everything is on this link, but you can find more on the GameShark code archives on this site by reversing the order of the last two bytes pairs in a code, e.g. 01xxD8CF edits CFD8), for example, if you don't have all badges to be able to Fly and can't access all fly locations, you can set D356 to FF (every badge) and D70B, D70C (fly locations) to FF FF too.
You can have fun with memory editing through a memory editor such as VBA or the BGB debugger. You can also do something like edit D31E to obtain a glitch item easily and see what it does without having to obtain one with TheZZAZZGlitch's looping map trick
. Note that memory addresses are generally -1 in Yellow (so Yellow's item 1 is D31D), with the exception of certain ones like CD38 (lets you walk through walls when a non 00 value).
With glitches that corrupt the memory, such as Super Glitch/CoolTrainer, you can also observe what values areas of the memory get corrupted too. For instance, CoolTrainer corruption has proved most useful for corruption of the species of the opponent in battle (CFD8); hence, you could view that to see what Pokémon got corrupted beforehand, or if the game corrupted data that far, you could view CFF1 to see what the foe's DVs became, etc.
These save files
should also come in handy if you're using an emulator.
Good luck and have fun.