You finally came up with the game of your dreams. You wrote everything down, used all available studies and it sounds too good to be true on paper. But how do you make sure it ends up being fun to play?
You finally came up with the game of your dreams. You wrote everything down, used all available studies and it sounds too good to be true on paper. But how do you make sure it ends up being fun to play? You could build the game and throw in endless testing afterwards until your test subjects think it’s fun. But is that really the way to go? I think not. There are better ways to do quality checks. So what easier and quicker ways are there?
Periodic player involvement
Don’t shy away from asking potential players to try and review your game concept. Besides the obvious part where they give feedback on what they like or dislike, they are also the first to try the game itself when it’s finished. If you gain their interest the chances are they will be the first group to spread the word. Not to mention they feel a part of the game since they were involved. It’s a good way for a small indie developer to get some attention. But let’s get back to the obvious part. If you think developing your game takes around 5 months. Make sure to involve your future players at least once a month. It gives you time to act on their fears and comments. Later on this will lower the time taken during testing.
Prototype, prototype and implement
I learned that creating your game at once with all features feels good, but it gave a headache to test it with my audience. Instead, I tend to build smart prototypes in the GameCreator with the most important game features. When I’m making a platform game with a special boss I take the bosses mechanics and put it in a small level which I can easily fine-tune. It’s quicker and easier to get done for your next session with players. Nothing beats seeing your involved audience smile for five minutes rather than get stuck on issues you didn’t want them to comment on.
To further know if your game will be a success, write down which statistics to record and how you expect them to analyse. Letting players test your game is one. But how do you record the necessary information you need to know the players act as you wish? Is watching enough? Do you need to record the screen and eye moments? Before I get to play-tests I write a simple table with bullet points I need to know in Excel. It often contains: time needed to finish a level/section, amount of retries, keys being pressed, the player’s emotion and their average compared with all others.
This is just a small set of techniques I use and have seen in other companies. They give you the edge and act as a forward warning system when users freak out about your concept. Large game development companies even have their own departments with data analytics who analyse every pixel of a game during game-play.
How do you make sure your users enjoy? Did you ever use play tests? Or are you planning to? I would love to know!