I'm not entirely certain what that definition is, but in the case of Game Genie, I meant a Game Genie boot ROM as an .NES file. Part of the mapper implementation for the emulator would be to select another .NES file to stack with it. Yes it's a very simple (almost trivial) mapper, aside from the extra file selection involved in the emulator implementation, but I don't think its simplicity is a point against it.lidnariq wrote:It is, by definition, impossible to create a ROM that requires the Game Genie hardware be present.rainwarrior wrote:1. Create and publish the ROMs that require it. (Not just theorizing they could exist.)
The advantage, though, is that you could emulate Game Genie + ROM in a slightly more "native" way, letting you play through and/or debug the transition from Game Genie boot to game.
Does anyone need this? Probably not, but if someone built (past tense) a working implementation of ROM + emulator that needs it, I see nothing wrong with allocating an NES 2.0 mapper (or 020 submapper) for it.
Another argument against it is that there's nothing stopping the emulator author from just implementing a special Game Genie mode that emulates its boot state and mapper. The .NES ROM format doesn't need to be involved. Unlike most single-instance mappers, a Game Genie mapper probably requires too much special case UI for stuffing it into the .NES format to be of any convenience.