Talk:Action 53: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
(Lots of questions answered)
No edit summary
Line 8: Line 8:
:The [[Detect TV system|TV system detection code]] is just 32 bytes and, like the gamepad reading code, could just as easily be duplicated in all banks. Most games won't see a value in the X register anyway, as they LDX #$FF TXS very early on.
:The [[Detect TV system|TV system detection code]] is just 32 bytes and, like the gamepad reading code, could just as easily be duplicated in all banks. Most games won't see a value in the X register anyway, as they LDX #$FF TXS very early on.
:As for the Family BASIC keyboard, I'm sort of loath to support any peripherals that I can't easily obtain to test with. I added controller, mouse, and Zapper support because that's what I happened to have lying around. --[[User:Tepples|Tepples]] 17:10, 26 September 2012 (MDT)
:As for the Family BASIC keyboard, I'm sort of loath to support any peripherals that I can't easily obtain to test with. I added controller, mouse, and Zapper support because that's what I happened to have lying around. --[[User:Tepples|Tepples]] 17:10, 26 September 2012 (MDT)
::I agree about avoiding that frustration with ratchet scrolling; but depending on the game there may be solutions:
::* Have it switchable by a mode on the title screen (possibly a secret mode).
::* Push SELECT and START button at the same time to commit suicide.
::* Have infinite lives so you can retry the level as often as you want (but you should absolutely not put a checkpoint in the wrong path!!).
::I happen to like games with a lot of traps like these as long as you can recover (such as save files or whatever; of course in this case there are no save files). But if you don't like it, it is OK; if I make anything like that you can choose not to put it on Action 53.
::For your other things I understand OK; yes I did read your wiki already. However: Is it required that each game can run standalone once extracted from the Action 53 ROM?
::Another question: Is there requirement for input devices used by the games? My suggestion (just my opinion; of course the way you decide to do it may differ) is: Any controllers may be used, but it must work with only two standard controllers, without requiring the use of SELECT/START/microphone on the second controller (but they can be used as an optional feature if the game supports them, I suppose, as with any other input devices such as mouse and keyboard). This way is more compatiblity.
:: --[[User:Zzo38|Zzo38]] 18:55, 26 September 2012 (MDT)

Revision as of 00:55, 27 September 2012

Will you release the ROM file? Will you release the source codes of the files for the Action 53 engine? Do you have 72-pins and 60-pins cartridges? Should you give examples about quality of Action 52 since not everyone would know that? Why do you hate unwinnable situations by ratchet scrolling (there are some situations in which you can make a game having this as part of a puzzle)? Which input devices can be used? Is NROM with CHR RAM for pattern tables acceptable? If you have 53 games and someone has more which is eligible, can you also make the second volume? Are there requirements for initialization which must be performed? Can you make the main menu perform TV mode detection and store the result in the X register (like NSF does)? Another idea would be allow use of Famicom keyboard on main menu (but not required): Arrow keys to move cursor, space bar to display description, RETURN to start game, CLR HOME to reset, letters and digits select a game quickly (assign a code consisting of a letter and digit to each game) and displays the description (pushing RETURN from there starts the game). --Zzo38 14:30, 26 September 2012 (MDT)

Let's break this down:
The ROM file and the menu source code are available: Action 53 0.03 release announcement.
As for 72- and 60-pin carts, that depends on whom I eventually choose as the manufacturer.
As for ratchet scrolling, I want to avoid the frustration of having to press Reset and lose all progress. Super Mario Bros. handles it well: apart from hardcore glitch abuse, the player can't really get stuck in a situation where the only option is to wait for time to run out. I was thinking more of situations like R-Type, where the path forks, and the player can't tell which fork is correct without choosing the wrong one and losing a life at a dead end.
As for what not to do (A52 style), I've described that in more detail in the page on my own wiki; plenty of the subjective requirements link to pages on TV Tropes that list examples of egregiously violating games.
NROM modded with CHR RAM is perfectly fine; Munchie Attack uses that configuration. In fact, if there's demand, I plan to allow for including BNROM games in the collection by allowing the builder to patch a bank lookup table.
The TV system detection code is just 32 bytes and, like the gamepad reading code, could just as easily be duplicated in all banks. Most games won't see a value in the X register anyway, as they LDX #$FF TXS very early on.
As for the Family BASIC keyboard, I'm sort of loath to support any peripherals that I can't easily obtain to test with. I added controller, mouse, and Zapper support because that's what I happened to have lying around. --Tepples 17:10, 26 September 2012 (MDT)
I agree about avoiding that frustration with ratchet scrolling; but depending on the game there may be solutions:
  • Have it switchable by a mode on the title screen (possibly a secret mode).
  • Push SELECT and START button at the same time to commit suicide.
  • Have infinite lives so you can retry the level as often as you want (but you should absolutely not put a checkpoint in the wrong path!!).
I happen to like games with a lot of traps like these as long as you can recover (such as save files or whatever; of course in this case there are no save files). But if you don't like it, it is OK; if I make anything like that you can choose not to put it on Action 53.
For your other things I understand OK; yes I did read your wiki already. However: Is it required that each game can run standalone once extracted from the Action 53 ROM?
Another question: Is there requirement for input devices used by the games? My suggestion (just my opinion; of course the way you decide to do it may differ) is: Any controllers may be used, but it must work with only two standard controllers, without requiring the use of SELECT/START/microphone on the second controller (but they can be used as an optional feature if the game supports them, I suppose, as with any other input devices such as mouse and keyboard). This way is more compatiblity.
--Zzo38 18:55, 26 September 2012 (MDT)