WWPD
WWPD
WWPD
WWPD
WWPD
WWPD
WWPD
WWPD
WWPD

Saturday, December 6, 2014

Farting with the Ancients

Wikipedia.
Playing a few games of Hail Caesar! has gotten me thinking about the design of ancient/fantasy wargaming rules.

A typical ancients game (one that's based on big armies and not skirmishers like Saga) features two clashing battle lines. Each line is composed of blocks of infantry, and the main decision of the game usually occurs when one line or the other begins to lose combat, break and falter. Other units in the game largely exist to support the main line: skirmishers may run ahead of it, archers may soften a target, cavalry may try to punch a flank or whatever -- but mostly, it's the core infantry that matters.

Variations of course exist: a ranged army's line will be mostly archers, and it will try not to close for as long as possible.  A skirmish army will float around trying to be obnoxious.  A pure cavalry army might form its fighting block of powerful knights rather than infantry.  But the core grammar remains the same.

From a game-design perspective, then, the question is how to bring interest to such a format. Some games focus primarily on the interplay of different types of units: swords vs spears, pikes vs horses, the merit of different levels of armor or resilience of training. Other games try to focus on command: Hail Caesar! makes the movement of its units unreliable, so you're never sure how far or fast they will move.

I am not enamored of either of these approaches. If the focus is on the equipment of different units, then the main question of the game will be which unit is paired against which when the battle lines clash.  Given the rigid nature of ancient battle, these match ups will be set early (probably in deployment), and I find only minimal interest in watching them play out.  Hail Caesar's! movement and order system makes the outcome less certain, but largely by ensuring that the main clash of lines will occur piecemeal.  But was the art of generalship in the ancient world really about making sure your troops marched at a consistent speed?

For me, the interest in any game comes from giving the players meaningful, important choices. A good game system will identify the decision points in its simulation and lay its emphasis there. In ancient battle, what could a commander do to ensure victory or avoid defeat? Where would his choices most matter?

1) The general could ensure that each of his assets were best matched against his enemy's. The initial deployment of forces would often determine everything that followed. So, in my game, I want choices and options in the deployment phase, with each player able to psych out, surprise, or outmaneuver his opponent as the battle is configured.

2) The general could deploy reserves.  Uncommitted units could reinforce faltering ones, press an advantage, or otherwise react to the flow of battle. So in game terms, I want a way for a player to move reserves where he needs them to be, and then to swap or support units in the battleline.

3) The general could spring some surprise or clever trick. Think about Hannibal at Cannae, deliberately weakening his center.  Some generals or units should have "special powers" letting them perform unusual actions, such as feigned retreats, ambushes and so forth.

4) The general could rally and inspire. By remaining visible and issuing commands, he could prevent his troops from faltering or becoming disorganized.  Conversely, he could run away or get himself spectacularly killed in such a way that his forces break.  So generals should be able to bolster morale of nearby units.

Now, most games allow a general to do some or all of these things already, through the ordinary choices of deployment, movement or melee.  What I want is to make them a formal part of the game, in which the players perform a kind of resource management with their commanders, deciding which of several options or orders they will employ at each stage of the game. This system of command-level choices will then float on top of the normal movement and combat mechanics, rather like Saga's system of powers and Battle board floats on top of a standard skirmish game.

In other words, it will be a lot like my Doctrine system in Sabre and Raygun.

Next up, beginning the design...

No comments :