Hey guys. Quite an odd question for you all so I'm not sure what can be achieved.
As you guys might know, through a series of inputs it is possible to get the game to a point where it's inputs become volatile to the games data and can allow you to corrupt the main system's memory data (More usefully, the range in particular that handles recording of "what players" are active, etc).
Through messing around with your inputs you can get the value stored at 0xFFFF0A to become a non-expected value (0 - 3 is the intended range) and a value of 128 becomes a "Blue Knuckles".
This is mostly just a goof-around project but I have gotten my inputs
(admittedly lifting inputs from aglar and marzojr's runs, as they are amazingly optimized for the early areas of the game) to a point where it puts the game into this state but I cannot seem to get the game to "crash" successfully and write to that area of the memory, bit of a out-there question but I don't suppose anyone has suggestions or inputs on how I can achieve this?
The input file so far.
Note: This input requires making a save and takes up the first slot (going from a clean SRAM)
[Edit]
p.s this is recorded in BizHawk, as I need to be able to do a console reset [/Edit]