User talk:ISSOtm: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
>Torchickens
>Torchickens
Line 14: Line 14:
If you store a text box ID (CF13) that is higher than the largest expected text box ID 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. I have barely looked.
If you store a text box ID (CF13) that is higher than the largest expected text box ID 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. I have barely looked.


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 Trainer-Fly's text box/Special stat encounter 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.
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 Trainer-Fly's text box/Special stat encounter script. But a non-start menu script may leave the address at an invalid value, hence the walking lag glitch. It seems likely to me that one of the scripts over 01 executes 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). [[User:Torchickens|Torchickens]] ([[User talk:Torchickens|talk]]) 15:33, 9 April 2015 (GMT+6)
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).

You can check for arbitrary code by going on debug>access breakpoints, entering writable memory (e.g. 8000-EFFF - I forgot the actual end of Echo RAM, I have a feeling it's not actually EFFF, sorry) in the address range box and checking 'on execute'. [[User:Torchickens|Torchickens]] ([[User talk:Torchickens|talk]]) 15:33, 9 April 2015 (GMT+6)