Lately there was quite some change in a bunch of branch names because of
this thread.
I'm ok with changing the fastest possible time for a game to the branch
any%. However, when changing that branch it is important to change branch of the original any% as well.
In the case of SMW for example it was just changed to
no memory corruption.
If you go ahead and simply define memory corruption by saying
changing a memory address to arbitrary or impossible values then you'll quickly see that the "no memory corruption" run of SMW actually does corrupt memory (goal orb in reserve) and that the any% run does not.
Keep in mind that the
obsoleted any% run does corrupt memory.
Moving on to the next example, Yoshi's Island. The same happened to the
short and the
long run.
In this case, the short run does corrupt memory and the long one doesn't,
but the reason why the short run corrupted memory was not the key factor to the credits glitch. It corrupted memory because I had to waste time for the controller registers to update and so I activated random DMA channels, which corrupted VRAM.
It should be noted that the "no memory corruption" applies to the
obsoleted any% run in this case.
Does this still count as memory corruption?
Does getting a goal in reserve count as memory corruption?
On that note, how do we use the appropriate categories:
Foregoes memory corruption &
Corrupts memory?
