You want your game to be perfect ?
To be an examples to the others? To have the official "Seal of Quality"? Then follow these simple guidelines.
Note: It's a draft. Don't hesitate to suggest additions/modifications.
Things in bold are mandatory. Other things are optional, you might not need them. It's just so you know where they go.
Have the game with the source + the binaries on Github (or other repos) with the following structure.
Let's say your game is named MyGame:
- Binaries to copy/paste on the microSD card
- binaries/MyGame/TITLESCREEN.BMP (80x64px BMP RGB 24 bit)
- binaries/MyGame/ICON.BMP (32x32px BMP RGB 24 bit)
- binaries/MyGame/TITLESCREEN.GMV (see note below)
- binaries/MyGame/ICON.GMV (see note below)
- binaries/MyGame/assets/track.wav (44.1Khz 8-bit uncompressed WAV)
- Source code
- Asset sources (the files you use to create your assets, eg. photoshop psd)
Note: *.GMV files are automatically generated when you display the *.BMP for the first time on the Gamebuino META. It's better to include them so people don't have to wait for them to be generated. Include GMV if you have animated *.BMP as conversion times can be long.
Make a Creation so that in appears in the Creations page. Please include the following.
- Github link (or other repository)
- Cover picture
- Game description
- Screen recording or screenshots of gameplay
- Credits (if any)
- The main goal is consistency across games and ease of use.
- People don't have to RTMF if you need no manual. Use intuitive controls.
- TEST, TEST, TEST. User experience is based on what the user thinks, not on what you think they think.
- Use as little text as possible. Replace it with pictograms. This way a kid that don't read, or someone that don't speak English could still enjoy your game. Plus, people are lazy and often don't read what's written (trust me on this one).
- Use the default titlescreen and home menu for a consistent behavior.
- Make simple and easy to use menus.
- Use the default 80x64px resolution and use the Official Gamebuino Palette (follow the link to see why).
- Use the lights. This makes a nice, immersive effect. But be gentle, don't go disco-ball!
- Buttons usage. See
- A : OK/validate/enter/start/shoot/main action
- B : cancel/return/discard/jump/secondary action
- Menu: item list/pause menu/map
- Home: Don't touch this. Do not attempt to adjust system settings like volume or light intensity through your game. The Home Menu is there for that.
- Arrows: well do you need an explanation for that?
- If you need key combinations, think twice about it. If you still need them, introduce them in the tutorial so people don't have to guess (or read the manual, because they won't).
Variable naming conventions
Check out the Arduino Style Guide for easy-to-read, beginner-friendly code.