Hey everybody, Sorunome
here. I converted this table into a more machine-readable format and made it way easier to search by address or by ID, so e.g. when searching for 8005 (or $8005 or 0x8005) it'll jump to appData.
You can find it here: https://www.omnimaga.org/index.php?page=ramhere
is some more information as to what all that search supports
***** barring obscure situations, this memory won't be touched by outside forces
**** some avoidable practices will overwrite this memory
*** normal operation may occasionally overwrite this memory
** this memory location is not stable by any means, though, it's still memory
* this is hardly memory, it's only listed because it was in the way
***** changing this memory has absolutely no effect on anything
**** there are some situations where changing this has an effect, though, you probably won't run into them
*** this makes some rather rare events fail, but it could happen
** this makes some common tasks fail
* honestly, the calculator basically crashed
The collateral damage number is only correct if you follow my recommendations for cleanup. If you don't, then things might go very bad. What it breaks is what won't work when you are using that memory, it will work after you are done.
And when you clean up, I recommend you first zero all the memory you used, copy back the manual backup locations, and then run all the necessary bcalls.
Lastly, if you see any changes that need to be made to the list (like anything), be sure to tell me.
Be sure to thank shmibs for hacking the width of this page.