If you are still using the old URL (datacrystal.romhacking.net), please update your bookmarks! The old URL may stop working soon.
The current URL is datacrystal.tcrf.net.
The current URL is datacrystal.tcrf.net.
Talk:Castlevania (NES, Famicom Disk System)/RAM map: Difference between revisions
Jump to navigation
Jump to search
TheouAegis (talk | contribs) (Created page with "Huge shout-out to MarioFan for the audio stuff. I always forget to look for APU-related code. I had to do a lot of NESDev reading while I worked on this, and MarioFan's previo...") |
m (Hawk moved page Talk:Castlevania:RAM map to Talk:Castlevania (NES)/RAM map) |
(No difference)
|
Revision as of 01:25, 24 January 2024
Huge shout-out to MarioFan for the audio stuff. I always forget to look for APU-related code. I had to do a lot of NESDev reading while I worked on this, and MarioFan's previous work was an invaluable asset! With that said, there are still some variables unmapped after over a week of looking over the game's code, so we still have a lot of work to do. There are quite a few bytes that appear to never be used within the 300-5ff range, as well as the 7D0-7FF range. We shouldn't try to map all the various uses of the lower Zero-Page bytes, which are typically just used for passing arguments to functions, but some of the bytes may have value being mapped even if they get overwritten 100 CPU cycles later.