Users browsing this thread: 1 Guest(s)
Restored Menus
02-21-2020, 09:07 PM
(This post was last modified: 02-21-2020, 09:08 PM by Catone.
Edit Reason: The fool didn't proof read the post.
)
Nah, just need to invent digital "duct tape", then duct tape the extra SRAM, a bit of RAM, and maybe a Tbyte of ROM space right to the side of it. Anything will hold with enough duct tape, sure the same goes for digital duct tape, just have to invent it.
Bad jokes aside, trying to cram everything into 1 ROM and make it function is half the challenge, and un-utilized resources are just wasteful, gotta make use of every single bit.
Regardless, back on topic, something that doesn't seem right. The SwdTech Menu patch uses 3 blocks of data to save any changes, (as usual, to the best of my understanding here)
/1CF8 (48 bytes)
/1E1D (35 bytes)
/1E70 (13 bytes)
Now sure, /1E1D to /1E40 would overlap with the treasure expansion, but wouldn't anything at /1E70 - /1E7D already cut the end off them anyway? Or does treasure info only fill up to /1E70 vanilla, but extend to /1E7F by default?
Bad jokes aside, trying to cram everything into 1 ROM and make it function is half the challenge, and un-utilized resources are just wasteful, gotta make use of every single bit.
Regardless, back on topic, something that doesn't seem right. The SwdTech Menu patch uses 3 blocks of data to save any changes, (as usual, to the best of my understanding here)
/1CF8 (48 bytes)
/1E1D (35 bytes)
/1E70 (13 bytes)
Now sure, /1E1D to /1E40 would overlap with the treasure expansion, but wouldn't anything at /1E70 - /1E7D already cut the end off them anyway? Or does treasure info only fill up to /1E70 vanilla, but extend to /1E7F by default?
The only true wisdom is knowing you know nothing.
« Next Oldest | Next Newest »
|
||||
Users browsing this thread: 1 Guest(s)