Talk:INES Mapper 030: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
Rainwarrior (talk | contribs) |
Rainwarrior (talk | contribs) |
||
| Line 3: | Line 3: | ||
:While it is true that BK:MoT can function with just the Mapper 2 oversize, the game was made on the board that Mapper 30 is defined for. Given that it exists on the UNROM 512 board, I do have some plans to make a convenience hack, where the games continue points write something to the flash, so that the game can be saved, resumed later, without needing to write down passwords. Modding that to real cart will just be a matter of desoldering the 4 flash locked jumnpers, soldering the flash enabled jumper, mounting the 74*139, and flashing the modified rom to the cart. Such a hack would definitely need the mapper 30 definition. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 12:15, 8 April 2014 (MDT) | :While it is true that BK:MoT can function with just the Mapper 2 oversize, the game was made on the board that Mapper 30 is defined for. Given that it exists on the UNROM 512 board, I do have some plans to make a convenience hack, where the games continue points write something to the flash, so that the game can be saved, resumed later, without needing to write down passwords. Modding that to real cart will just be a matter of desoldering the 4 flash locked jumnpers, soldering the flash enabled jumper, mounting the 74*139, and flashing the modified rom to the cart. Such a hack would definitely need the mapper 30 definition. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 12:15, 8 April 2014 (MDT) | ||
::So... you want to allocate mapper 30 for a BK2 hack you plan to make in the future? I don't think it's good practice to allocate mappers before there is something to be emulated that needs one. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) | ::So... you want to allocate mapper 30 for a BK2 hack you plan to make in the future? I don't think it's good practice to allocate mappers before there is something to be emulated that needs one. There's not a lot of unallocated iNES 1 mapper space, and it's a waste of time for emulator authors to read or implement this definition until there's actually a ROM out there to emulate. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) | ||
Revision as of 21:06, 8 April 2014
Board allocation
Study Hall definitely needs its own mapper, but why does BK:MoT need to be here? It's handled by the standard m2 emulator oversize logic... —Lidnariq (talk) 11:54, 8 April 2014 (MDT)
- While it is true that BK:MoT can function with just the Mapper 2 oversize, the game was made on the board that Mapper 30 is defined for. Given that it exists on the UNROM 512 board, I do have some plans to make a convenience hack, where the games continue points write something to the flash, so that the game can be saved, resumed later, without needing to write down passwords. Modding that to real cart will just be a matter of desoldering the 4 flash locked jumnpers, soldering the flash enabled jumper, mounting the 74*139, and flashing the modified rom to the cart. Such a hack would definitely need the mapper 30 definition. Caitsith2 (talk) 12:15, 8 April 2014 (MDT)
- So... you want to allocate mapper 30 for a BK2 hack you plan to make in the future? I don't think it's good practice to allocate mappers before there is something to be emulated that needs one. There's not a lot of unallocated iNES 1 mapper space, and it's a waste of time for emulator authors to read or implement this definition until there's actually a ROM out there to emulate. - Rainwarrior (talk)
