User talk:ISSOtm

Generation I glitches category on walk through walls glitch pages

My impression was that since they are different tricks and each walk through walls glitch is significantly different (they have different causes and side effects), they should each have the Generation I glitch category. I'm OK with walk through walls having the category too. Torchickens (talk) 15:29, 5 April 2015 (GMT+6)

Thank you

Thanks so much for your edits on this dormant wiki. I will get back to work on the wiki soon. Torchickens (talk) 15:29, 5 April 2015 (GMT+6)

RE:Research plans

I don't notice anything wrong with your explanations.

Good luck and have fun then! Researching text box matching might actually be a really rewarding idea. There are two very promising things about it.

It never occurred to me before until after I learned about the Pikachu off-screen arbitrary code execution method (involving creating a glitch sign that takes its data from D221) that Trainer-Fly glitch text boxes may take their script from a re-writable place as well.

If you store a text box ID (CF13) that is higher the largest text box for the original route, you can sometimes get other glitch texts instead of a plain error message. I can't find one that runs an arbitrary script, but I definitely don't rule it out.

Other related things that need research are glitch map scripts. You might have read in my latest video, these are found at addresses past D5F1 and for maps with Trainers they are set to 01 to create the Trainer-Fly script. But a non-start menu script may leave the address at an invalid value, hence the walking lag glitch. But those scripts may execute arbitrary code too.

It is possible to check the source of a text box by going into BGB and double clicking 0:2882 (Yellow) or 0:2992 (Red). Torchickens (talk) 15:33, 9 April 2015 (GMT+6)