Anonymous user
ItemDex/RB:085: Difference between revisions
→Planned SRAM corruptions as a concept outside of 10F
Line 118:
*"The file data is destroyed!" message does not appear. (An example of an issue may be a bad save checksum).
*That it's possible in the first place to achieve the desired result while meeting the criteria above through calculation or a tool/SRAM corruption emulator.
As a general concept, the subject may also have implications for the logistics of programming a tool (such as a SRAM corruption emulator). If the tool is given support for algorithmic or mathematical models (e.g. [[wikipedia:Simulated annealing|simulated annealing]]) it may be possible to follow/visualise simulations as well.
{{clr}}
| |||