“Pacing” is one of those words that critics use as sort of a catch-all to explain why a game doesn’t flow as well as it should. It can refer to stories or plots that climax too soon or too late, to mechanics that get in the way of whatever progress you are making in learning a game, to all kinds of things that interfere with that sense of enjoyment you get when you are lost in a game.

When we think of pacing in strategy games, we generally mean how well it spaces out tasks or shows you new things to move on. The whole “one more turn” thing is predicated on the idea that you have set up a game that has steadily delivered a feeling of accomplishment to the player and promises more of that feeling if the player is just willing to sit there till 2:00 AM making the trains run on time. Good pacing can be a slow burn (the Imperialism games) or a constant sensory assault (Age of Empires 3).

Pacing problems are more noticeable when games try to tell a story. Though the drama of kings and wars should make for a natural story-telling genre, the way that strategy games deliver the war machinery and diplomacy has proven generally ill-suited for story telling more elaborate than cut scenes in between mission assignments. When mechanics and narrative collide, the game usually wins in this genre.

I’m playing Disciples 3: Renaissance for review and it has major pacing issues. There is a lot of good stuff in the game, too, but the pacing prevents me from going back out of joy instead of out of obligation. Nothing focuses the mind like a deadline.

One of the big problems for scenario design in story based campaigns is mission length. In a turn based game like Disciples 3, where you have to end turn and watch the enemy make its moves, all the while interrupted by tactical battles that can take a while to finish, the decision on how and where the player can best spend his/her time is a critical one. Completing one objective after two hours on a map only to find that there are now new objectives is a pacing problem for both game play (new objectives can mean that you have the wrong tools in your toolbox) and narrative (too long in one place means the story does not get told efficiently.)

Real time strategy games can have this problem, too. The first Supreme Commander game had maps that expanded and unveiled new things to deal with and each one made me groan in frustration.

But by and large, story based campaigns in RTSes are linked to the technologies available to you. So the missions grow in length and complexity at the rate you get new toys to play with. The default RTS mechanics of the story telling are generally in tune with good pacing.

This is a happy coincidence, since most of the problems with RTS story campaigns are related to repetitiveness or lack of good characters. Since they don’t have to worry about matching the mechanics to the tale, they can work on the puzzles of the mission scenarios. And maybe writing something interesting. (Someone. Please.)

So what is the sweet spot for a mission scenario’s length? Personally, any more than an hour and I get into some serious trouble staying interested, especially if I know that there are even more missions to come. Properly paced, an hour can seem like twenty minutes, but some games constantly remind you how long you are at something. (Turn counters are a good idea, but when I read Turn 50, my first instinct is to wonder how many more turns I have to play.) Disciples 3 is not well paced, so every hour feels like an hour. After a dozen plus hours in the game, I feel like I should be farther ahead than I am.