If a button is pressed between the time Menu is pressed and released, it would not need to bring up the menu
Menu + Lock = take a screenshot
Menu + Up = the first game-added menu item
Menu + Left = the second game-added menu item
Menu + Down = the third game-added menu item
Menu + Crank = controls volume
That leaves Menu + Right / A / B for games to assign on their own
And I'd like to suggest long-hold Menu for a universal custom soundtrack menu that plays files in the music folder.
One reason for this is I've seen some people complain that that while the menu helps make up for the lack of buttons, bringing up the menu takes focus away from the game so it can't be used in-game
I think Menu+Lock does take a screenshot currently, and we're already using Menu+Up/Right for volume up, Menu+Down/Left for volume down. Letting games use Menu+A/B is an interesting idea.. I don't know if it makes more sense to map it to the menu items or let games choose what they do. I'll file that and we'll think about it.
fosterdouglas
(Foster Douglas / Everyday Lemonade)
4
It's maybe a bit awkward to hold the menu button and the reach across to press A/B? I could see a more complex game taking advantage of it maybe, but it doesn't feel particularly natural
Maybe volume could be re-assigned to just A/B, leaving Menu-d-pad free for FOUR custom game options.
Early users would have to get used to that little change, but it might "feel right" because A and B are nicely positioned below where the volume meter would otherwise appear. And for in-game functions, Menu-d-pad seems more comfortable for repeated use than Menu-A/B.
(I don't care either way about doing something with Menu-crank.)
More buttons is good! But I'm thinking the crank doesn't make an ideal volume shortcut for a few reasons:
Many games rely in the absolute position of the crank (Whitewhater Wipeout and Transmewting come to mind). If the crank is read by the system outside the game, then when you're done adjusting the volume, the crank is suddenly returned to gameplay in an unexpected position. And system use of the crank could mess with game play in a way button combos can't.
It's slower and more awkward to extract the crank, use it, and put it away, than just hold a pair of buttons. May as well not have a shortcut, then, and just use the pause/System Menu.
The volume has distinct steps: with buttons you know what "3 clicks quieter" sounds like, say, and it's easy to get just a small adjustment or a full mute. But the crank offers no tactile "steps" of feedback to know how much you have changed, or to help you stop "right on 3 clicks." Not impossible, just awkward as a shortcut.
I think a neat compromise would be to get rid of the volume redundancy and e.g. only have volume up on menu + dpad right. Personally find left/right the most intuitive because it also mimicks the volume UI in the side menu. That would free up the other two dpad buttons to be assignable via the SDK, or they could trigger an event similar to the pause or resume events.
I think this would be a clean alternative to button combinations or input schemes via the regular buttons, especially if a lot of those are already used for other ingame actions. Examples for common custom actions are opening up map or inventory screens which would naturally fit the menu button anyway. A risk could be that developers may rely on that additional "easily accessible input" to make their games' controls more complex instead of trying to design around fewer buttons which might not align with the Playdate's intended design direction.