The screen that is allowing you to write to RAM, is that a messed up rendition of the naming screen that is being referenced in from the location of where we originally named the child to the map? Also, what is the importance of renaming the child at this specific point in time versus earlier? Is it because this portion of the ram is overwritten to a new location to run the payload? What is it overwriting that is being run? I'd really love to see a technical deep dive into how this works rather than just an overview if you ever get the chance!
Check the description for a blog post that goes into all the gory details. Yes, the naming screen is the same one that is normally opened when naming the child. The graphics get corrupted because the game is trying to load the graphics while the screen is still on, which doesn't really work properly. The graphics would normally be loaded when the screen is off and VRAM is fully accessible. I don't totally understand your other questions, but perhaps the blog post will give some insight. It is not possible to run the child's name as code until I reach the out-of-bounds area, hence it would be pointless to rename the child any earlier (aside from setting up an initial name so that it won't crash immediately).
Absolutely beautiful. Good work.
Well done!
I dont mind the mistakes in this run, Im just happy these games continue to have an active speedruning community in the first place
Looks like a new era of speedrunning has been kicked off 😅
Thank you for teaching me that some glitches cannot be contained within a single game.
The screen that is allowing you to write to RAM, is that a messed up rendition of the naming screen that is being referenced in from the location of where we originally named the child to the map? Also, what is the importance of renaming the child at this specific point in time versus earlier? Is it because this portion of the ram is overwritten to a new location to run the payload? What is it overwriting that is being run? I'd really love to see a technical deep dive into how this works rather than just an overview if you ever get the chance!
Check the description for a blog post that goes into all the gory details. Yes, the naming screen is the same one that is normally opened when naming the child. The graphics get corrupted because the game is trying to load the graphics while the screen is still on, which doesn't really work properly. The graphics would normally be loaded when the screen is off and VRAM is fully accessible.
I don't totally understand your other questions, but perhaps the blog post will give some insight. It is not possible to run the child's name as code until I reach the out-of-bounds area, hence it would be pointless to rename the child any earlier (aside from setting up an initial name so that it won't crash immediately).
@@Stewmat Very cool! Thank you for the response!