Türkenheimer | Writing to Uncached ROM Data is weird @turkenheimer4448 | Uploaded 2 years ago | Updated 19 hours ago
[Edit: This behaviour is not related to ROM data, it is just a new quirk that happens when you hit a Doubleword boundry with something smaller than a Word.]
What the ROM-Hack is this video?
0:00 slashing a bush to load a function to uncashed memory
0:06 hacking ROM data in the KZ hex viewer does not persit
0:23 hacking a pointer in a bush. When the bush is cut it will normally write a byte of 0x01 to the address of the pointer +0x1BE
1:07 cutting the grass to write to ROM
Expectation: Since this is a write to uncashed memory a double word write is expected. So at 8FEE6670 we should find 01000000 01000000.
1:12 which does happen as expected. However, what the hack happened to the previous doubleword???
1:17 trying to hack data in the hex viewer again. Did somehow not work this time, but it worked the previous time I did this, before this recording.
[Edit: This behaviour is not related to ROM data, it is just a new quirk that happens when you hit a Doubleword boundry with something smaller than a Word.]
What the ROM-Hack is this video?
0:00 slashing a bush to load a function to uncashed memory
0:06 hacking ROM data in the KZ hex viewer does not persit
0:23 hacking a pointer in a bush. When the bush is cut it will normally write a byte of 0x01 to the address of the pointer +0x1BE
1:07 cutting the grass to write to ROM
Expectation: Since this is a write to uncashed memory a double word write is expected. So at 8FEE6670 we should find 01000000 01000000.
1:12 which does happen as expected. However, what the hack happened to the previous doubleword???
1:17 trying to hack data in the hex viewer again. Did somehow not work this time, but it worked the previous time I did this, before this recording.