The “Playing” Aspect of your Casual Game

This is not a post of game design, basic mechanics or dynamics. Nor aesthetics, story or characters. This “Playing aspect” is a set of structures and practices all casual games should have on nowadays markets, regardless if it is a hidden object, time management or chain popper.

Loading Times and Start Menu

The game must load fast before the start menu, and after clicking the “Start” button. If the game features comics or intro videos, a skip button must be available. The player shouldn’t spend more than 3 minutes between “Finish” installation button and getting into the game.

So many casual games are out there, so many clones are made in no-time… The competition is fierce. If the game takes too long to start, why bother? Why not giving up and getting a similar game on the same portal?

Of course, players will have more patience with your loading time if they had to download the game in the first place. They invested time, had to install it, so they will be willing to wait a bit. If your game is a Flash webgame, however, loading times must should be really really fast. I’d say 10 seconds top – provided you make an obvious loading bar with the percentage loaded very clearly stated.

Controlling

Casual players don’t expect to use anything but the mouse. They are not used to first-person shooters WASD control schema. They are not used to map spells on keys like F2, F3, etc. They will try to use the mouse, and they will use the left button.

Should we never use arrows keys? Arrows are OK – if you clearly explain them, with BIG art of arrow keys on the tutorial screen before the game begins, highlighting the explanation with particles around! J I’m kidding, but really, players skip tutorial screens in a blink. So during the half of a second they look to them, you should explain arrow controls.

Everything else should be controls aimed to help advanced/dedicated players – not the core control of the game. Like PopCap says, it is not that your controlling schema should dogmatically follow the “left button of mouse” mantra. It is just that, if game can’t be played like that, game design probably isn’t simple enough for the casual audience.

Tutorials

The player must be taught how to play the game. Don’t be afraid of tutorial screens, but always make an in-game tutorial on the first game stage (even if you are doing one-more-match-3). Teach the mechanic basics with in-game tutorials. If your gameplay is more complex, you could extend the mechanics in-game tutorial to the second stage, but don’t go much further. Too many in-game mechanics tutorial will give the impression the game just takes too long to “really begin” (as the Shopmania team found out).

Use in-game tutorials again when the player gets new powers/items/spells. Always provide a “Skip Tutorial” button, so returning players who start new games won’t have to go through it.

Saving

On casual audience, gameplay sessions are short (10-15 minutes) but frequent over the day (5-7 sessions). The game should:

1. Save the player progression automatically during gameplay, without locking the game.
2. Load save games fast when returning
3. Restore games in the very same point the player left. Everything must be exactly the same.

Would that mean that checkpoint systems do not work for casuals? It could work, but so many casual titles have implemented the save feature as stated above that your player will probably be expecting for them – and get frustrated if you don’t have it. Avoid taking unnecessary risks.

Also, casual players won’t comfortably manage multiple saved games, which is the reason save files are connected to simple and straightforward “player profiles”. If possible pick the Windows account login as the default user name the first time the player runs the game.