Talk:INES
From NESdevWiki
Discuss the [iNES 2.0 proposal]. Try to follow the general structure here. Indent replies by adding an extra colon (':') at the beginning of the line. Try to be concise.
Contents |
[edit] Critique
[edit] RAM size field
Bad idea since the handling is mapper-specific anyway.
- Why not have such a common thing be represented in a consistent way? The mapper gives meaning to almost all the bits in the header, even PRG and CHR size.
[edit] Additions
[edit] Version Number
Needs version number to allow future extension for anything left out.
- There are still reserved bits that can be defined at a later time.
[edit] Needs more region bits
Needs more bits describing region and intended console to play it on.
[edit] Add data to end of file
Just add UNIF-style blocks at the end and call it iNIF.
- Do what you like, but this is about defining more of the first 16 bytes of the file.
[edit] Store mapper revision numbers
Store mapper revision numbers, even if we don't yet know of any differences.
- Problematic since revisions might only be distinguished by the production date or cosmetic differences.
[edit] Process
[edit] Consensus
Don't implement format until there is a consensus from everyone on all details.
- What about experimental implementations to uncover problems that nobody thought of, and for people to get a more concrete feel for the proposed format?
