6.2. Quality Assurance¶
Before publishing your game, there are a few things that you can do to improve the final published game. These improvements lead to a better game that will increase the engagement of players and the final success of your game. In this page, we provide a set of guidelines to help you improve your game.
6.2.1. Visual Design¶
- All artwork contained within in a game should adhere to the same styling. If you use a cartoon style for your game’s characters, then you should make the game’s world cartoon like as well.
- Game characters and images should be sized in proportion to one another.
- Your game’s user interface should you the same font(s), color(S), style on all buttons and user interface.
- Use high resolution images(128x128 pixels is a good size for characters)
- Colors should not be used in a way that makes it difficult for the player to distinguish what is going on.
- Game artwork should be easily visible on mobile devices.(try not to use very small text)
- Game characters size and shape should match up nicely with their collision boundaries.
6.2.2. Game Mechanics Design¶
- Make sure the controls for your game match nicely with target device.(don’t use tiny buttons for mobile devices)
- Build controls that can be used by wide range of players.
- Make sure gameplay is easy to understand or provide players with a instructions.
- Your game shouldn’t be too difficult or too easy for your target audience.
- Your game should be free of errors.
- Most importantly, the game should be fun
- Keep file sizes for assets to a minimum while maintaining quality. This will help speed up downloading the game to a device and shorten the load time for the game.
- Remove any unnecessary assets from you game.
6.2.3. Debug Your Game¶
Before you publish your game it should be free of bugs. Bugs(errors) are annoying to players and distract from the game.
Play-test Your Game
An easy way to catch bugs in your code, is to actually play your game. If there is a part of your code that you weren’t exactly sure how it would work, test everything related to that part. When play-testing, you have to try every possible thing that the player can do. If you encounter a bug, try to reproduce the conditions leading up to the bug and make changes to your code accordingly.
Even when your code runs exactly as intended, your game may still contain design flaws. An example would be the game is easy for you, but not for most players. Your game’s difficulty, controls, etc. should be designed to meet your target audience’s needs.
With play-testing, more testers are always better. Get as much feedback as you can from players of different ages, gender, etc.
Fix bugs on step at a time
When correcting your code, make a small change and test for the desired result. If you still have an error, change your code to how it was before and make a different change. You can keep repeating this process, making as few changes as possible so you don’t create another bug in the process.