Categories of Action in Strategy Gaming

I always get really nervous when I try to talk about the theory and practice of strategy game design. I tend to get over-wordy, lose track of my point, and generate articles that I worry just don’t really help anyone very much or illuminate much of anything besides my own muddled thought processes.

And yet, here we are again. In this article, I’m going to seek to elucidate a theory of how players’ actions operate in the context of strategy games – mostly, in a competitive setting, though I think it also applies to single player or co-op as well. Specifically, I’m looking at how games’ rules direct player action into one of 4 interrelated categories of action, which I’m calling “Preparatory” actions, “Anticipatory” actions, “Direct” actions, and “Reactionary” actions.

We’ll take a look at each category separately, using examples across a range of games, and then talk about how these relate to one another, and where I feel existing game design could do a better job of providing a more rewarding experience.

As I said in the Twitter thread I used to workshop this piece: buckle up, chumps.

Preparatory Actions

Resource harvesting and building production structures are examples of Preparatory actions. You’re gearing up for the ‘real’ fight later on

Most strategy game design leads players to focus intensely on the first category of action. Preparatory Actions are exactly what they sound like. They’re the player preparing for something to happen.

Building up your economy (training workers, building Refineries) or manufacturing base (building production structures), researching tech/upgrades, and building out your army are preparatory actions. For these, benefits are often not immediate and may take minutes of careful management to build up to a payoff or better game position.

You’re building up towards being able push out your army, or to fend off the enemy’s big attack. You’re preparing to pull out your deathball, your super-unit or superweapon. You’re spending time and mental energy towards the goal of making something happen. These are incremental actions, with a long payoff; few of them reach their peak performance within a small time period.

Supreme Commander has a bevy of intricate Preparatory interactions, such as building adjacency bonuses

These are the actions that players really seem to tend to enjoy on average. Games like Age of Empires, StarCraft 2, and Supreme Commander have intricate and comprehensive systems of Preparatory actions that provide a high degree of control of economic outcomes.

In general, players tend want to build an intricate base that’s laid out just so, or maximize their build order to get those Banshees out in as few seconds as possible.

Overly focusing on preparatory actions, however, is bad for a competitive game. Just ask Grey Goo (or Forged Battalion). Grey Goo’s gameplay is really loaded towards a gradual ramp up to a large army. Once you’re in the middle of a battle, you don’t… really… have a lot of tools to react to your opponent’s actions, or manipulate the battle in meaningful ways beyond backing off and trying not to lose too much of your army.

Winning a Grey Goo match comes down, more often than not, to your abilty to maintain and expand an income to support army replenishment. Income and manufacturing reign supreme, to the game’s detriment.

I hate to derail this entirely to dump on Grey Goo, but a lot of this comes down to: slow average unit move speeds, and production and harvesting operations (refineries mostly) being highly defensible, combined with a low-impact counter system, means that harassment is difficult to pull off and it’s difficult to counter a large army with a smaller one. The game provides very little wiggle room or ability to pull out any sort of “oh crap!” measure to reverse your fortunes, and a small number of units don’t have a lot of room to make a big impact.

Contrast this with StarCraft 2, where a single uncontained Infestor or Oracle can mulch an entire base’s worth of income, or in WarCraft 3, where a Blood Mage or Archmage can whittle an army with a lucky hit, or a Demon Hunter or Blademaster can take out an enemy hero leaving their army vulnerable and unsupported – and these are the easy, low hanging fruit interactions to describe.

And, speaking of battle…

Direct Actions

Pew Pew! Direct actions are when you make something happen in a game, whether it’s taking territory, moving your army to initiate combat, or doing a rush/suprise attack.

Next, we have Direct actions. I’m skipping Anticipatory for now. I’ll do that one last because it’s the trickiest to tackle. Direct Actions are, well, doing stuff.

Direct Actions are proactive, aggressive actions you take in the game. Scouting your opponent, trying to cut off their supply line, sniping their workers to slow their economy, or doing a push with your army are primarily examples of actions that fall into this category. Even moving your army to a tactically advantageous position or to cut off your opponent from part of the map would count as ‘direct’ actions.

For instance, if in Age of Empires you scout your opponent sending an attack force in your direction, you might want to manipulate your forces to be ready for their likely attack point (an anticipatory action). You might also want to change from a more economic focus/boom economy towards maximizing your army, beginning a chain of preparatory actions to deal with your enemy’s evident aggression that would overwhelm you if you don’t have a large enough army to deal with it.

Sending a counterattack force to hinder their economy while they’re attempting to destroy your infrastructure would be an example Direct action.

Direct actions are, by and large, what the Preparatory actions are preparing for. Fast teching to a halftrack in Company of Heroes 2 to catch your opponent off-guard without a counter, getting those Dark Templar out (StarCraft 2) and into your enemy’s base before they get detection. These are the direct actions you’re taking to swing the course of the game.

Like the name says, these actions are often pretty transitory. In many cases, being the output of a Preparatory action, these are more of a result than a product in themselves. The kinetic result translated from the potential energy generated from preparatory actions.

Direct actions are the second half of what most RTS focus on (the first half being Preparatory actions, of course). Build a bunch of horsemen – preparation, send them to harass enemy villagers – direct action. Turtle up to get a nuclear missle – preparation; slam that missle into the enemy base – direct action.

Reactionary Actions

MOBAs, especially Heroes of the Storm, tend to have comparatively few preparatory actions and focus player attention on Anticipatory and Reactionary action types.

Reactionary actions are the ones players take *during* or *in response* to other actions, particularly in combat situations.

  • Retreating your army from a losing engagement
  • using skill shots or abilities to change the course of the combat
  • offmap/support powers
  • Most combat-oriented unit ‘micro’

Are almost always reactionary in nature.

The line between Direct actions and Reactionary actions blurs a bit at times, and I feel it’s mostly one of intent. Remember, we’re talking about how players are interacting with the game here. So, where a Direct action is sending your army out to attack your opponent’s base (with maybe a surprise sneak attack at enemy production lined up) the Reactionary actions that follow consist of the Psionic Storms, Stalker Blinks, Yamato cannons, Marine micro, grenade tosses, etc that you’re performing to ensure the success of your intended course of action.

Reactionary actions are typically loosely related to Preparatory actions: you might need to have constructed a structure or researched an upgrade to enable the Reactionary action (such as with support powers in Command and Conquer 3), or it might be tied to a unit you’ve had to train (such as Psionic Storm in StarCraft or Anti-Tank grenades in Company of Heroes).

These actions are the ones you take in the moment to impact the outcome of an engagement or interaction. Making the best use of the tools you’ve acquired in the Preparatory phase to ensure a better outcome for youself than your opponent. Micro. Active abilities. Skill-shots.

Hopefully, I’ve been able to demonstrate that so far, the majority of interactions RTS, each in its way, inherits from the Preparatory actions of building your economy. We’re going to come back to that in a bit. But first, Anticipatory actions.

Anticipatory Actions

Universe at War and the Command and Conquer games feature design that supports some fantastic Anticipatory actions

I saved Anticipatory actions for last since they’re not really generally a formalized piece of the puzzle in strategy games. These are actions you perform as a last-minute adjustment right before an engagement begins.

  • Scanner sweep to find burrowed Banelings/creep tumors prior to attempting to move your army into position to attack the enemy
  • Splitting your army into 2 groups to surround an incoming enemy force
  • Engaging an ability that reduces your unit/army’s ability to react quickly in exchange for increased defenses (e.g. a Sentry’s shield bubble)
  • Performing a unit configuration action (putting a different troop in a Multigunner IFV in RA3). Sometimes these are Reactionary (like changing a Viking from air to ground mode) but sometimes they don’t provide full benefits unless you’ve done them before combat begins in earnest.

You almost always can’t perform the anticipatory action without having prepared (e.g. constructed a unit), but it’s not quite the same order of thing, to me. If I were to extablish a relationship between the 4 types of action, it would be:

Preparatory actions precipitate Direct actions. Direct actions precipitate Anticipatory actions. Anticipatory actions preceed Reactions.

Since a lot of this is contextual, a single ability or unit action might be Anticipatory, Reactionary, or Direct depending on context, though I would argue in most cases, the specific design of these abilities almost always makes them most suitable when occurring in a specific category.

Universe at War had some great Anticipatory actions in its faction dynamics.

  • Novus applying a new faction-wide Patch. This isn’t something that’s directly going to swing combat in your favor – there’s no instant impact in a localized area. But, it might help you retreat, or apply that code debuff during combat to change the outcome over the course of the battle. It’s an action anticipating eventual reactions down the line.
  • Masari switching to Light/Dark matter mode to change their army behavior. Unless you have a certain research option unlocked, dark mode takes some time to bring its main benefit (its shield) online. And units take some time to adapt to their new mode, with air units slowly sinking to the ground once Dark Matter mode is activated. Not something you want to do in the heat of the moment, unless you’ve prepared for it ahead of time.
  • Hierarchy swapping Hardpoints on a Walker. Hardpoints can alter the outcome of a battle, but are vulnerable when warping in. Changing from production to combat orientation takes some time.
I would consider positioning a set-up weapon in a Company of Heroes game to be an anticipatory-type action in most cases

These actions are often too slow, or their effects are too gradual to be reactionary and are more individually impactful than the overlapping pile of your preparatory actions, so you end up with this weird space where, right before combat begins in earnest, you’re fine-tuning things to work to your advantage that otherwise might not work (or work as well) in the context of a battle.

This is kind of akin to Company of Heroes 2, where mines/barbed wire are Preparatory, since they take time to place and are useless if a unit is spotted while placing them.

But, say, positioning your tanks and weapons crews? That’s more of an anticipatory thing. You can KIND of do it offensively, if you approach an enemy just right and have units to screen the crews while they’re vulnerable. But if you’re too static with it, you’re gonna get hit with some missiles or mortar shells or some such nasty area damage Reaction to what you’re trying to do.

Why does this matter? – Proportionality

Much of your success in Tooth and Tail comes down almost purely to a careful balance between income and production of armed forces. Once you’re behind economically it’s almost impossible to come back.

Proportionality: Forming a relationship with other parts or quantities; being in proportion.

Getting these elements into various balance configuration is the product (or results in) of different types of design choices when crafting strategy games.

Clearly, a game like Grey Goo or Forged Battallion, which are heavily skewed towards a dominant buildup phase, where resources are king, is a poor solution. Games designed this way suffer. Or, more specifically, the players of games designed this way don’t have a great experience.

I’ve written before about “equilibrium“, and allowing players multiple semi-independent avenues down which they can succeed – and must demonstrate mastery in which to succeed.

For me, this is more than an idle mental excersise. I want to understand how people approach game rules in order to create interesting and deep interactions in the games I make. When working on my StarCraft 2 custom mod, and duing my brief tenure assisting Dream Harvest games with the NeuroSlicers game, I kept running into situations where I wanted to be able to provide the players with different types of option and action to handle different types of threat.

When playing a strategy game, I feel deeply unsatisfied if simple economics and preparations are enough to score me wins in battle. It’s frustrating when quickly pumping out a bigger army is the surest way to guarantee a victory in most cases, and where the outcome of the first encounter with the enemy is highly deterministic of the outcome of the final encounter (the slippery slope, if you will).

I don’t want to experience that, and I don’t want my players to experience that. Weighting one type of action too heavily with the game’s design leads to the slogfests of Grey Goo, and another type too heavily leads to the unsatisfying one-battle snoozefests of Sudden Strike 4. The games that have resonated most with players over time, the timeless classics, give you lots of ways to succeed, and lots of opportunities to perform well in various categories of activity.

I know I’m something of an American Primitive of game design, constantly creating my own terminology for things that have may already have a formalized recognition elsewhere. I’m trying to define, for myself, how and why some games work mechanically, and others don’t. For me, this is a big piece of why. Having the right balance of preparatory actions with a long payoff, a variety of approaches that lead to interesting direct actions, that are themselves able to be anticipated for and reacted to in the moment, with different skillsets and mindsets driving success for each of these action types, with each type of action being somewhat independent in success and initiaton from the other types, leads to the most interesting game to play. Too much or too little opportunity to succeed along these actions spoils the recipe, as well as too much or too little weight being afforded to skill along one of these avenues.

Anyway, thanks for reading.

5 thoughts

  1. Nice article, I think identifying and defining actions in games is probably the most important aspect of design. I think you’ve helped created a more digestible scope of what kind of actions we may encounter and build around.

    I would argue that the preparatory phase doesn’t fit into actions however… it belongs more under a thing I’ve been labelling ‘uncertainty’ or ‘prediction’ as of late. Essentially, humanities fascination with predictable but ultimately unknown outcomes as well as the desire to constantly increase the efficiency of our predictions. Its probably one of the largest driving factors in playing games… like, if things are completely unpredictable or if we get to the point where we can predict everything, our enjoyment takes a major hit.

    For example when building a base you will constantly be trying to predict every possible attack or thing that could go wrong – every action you then commit is a reaction to that prediction. The amount of ‘predictable prediction’ that goes into this part of an RTS tends to go beyond that of combat, hence people typically enjoy it more.

    Liked by 1 person

  2. Interesting taxonomy!
    I think that there are macro/ base building elements that fall into categories other than preparatory. E.g building a forward turret at a chokepoint is a direct action, choosing an expansion location based on the enemy attack route is reactionary, and throwing up a last minute blocking pylon to keep vultures out of your base is anticipatory.

    I’m not fully on board about there being a correct balance of your categories as you suggest in the conclusion.
    I think deviating from a ‘middle ground’ approach can be fertile ground for interesting games!

    One of the greatest weaknesses of SC2 for me is that preparatory actions are very similar every game.
    Brood War, with its greater pedigree, has tried to shake this up over the years with some unusual maps (to limited success).

    Games with generated maps like AoE 2, Cossacks: EW or American Conquest require more interesting and varied preparatory actions as you determine where resources, chokes flash points etc. are situated.

    Liked by 1 person

    1. Kroem, thank you for reading and replying to my article!

      I see what you’re saying about different ‘types’ of preparatory action, and I do think there could be sub-categories developed for economic expansion vs production expansion vs combat preparation types of preparatory action (combat prep being like, upgrades)

      I agree with what you’re saying about building actions falling into various categories contextually, and feel like the model I outline in the article accounts for that.

      I 100% agree with you that different proportions of these action types make for different kinds of great game! I had planned a section going into how I see SC2 being more reactionary than Command and Conquer 3, which has a greater respect and utilization of anticipatory actions. I am mostly concerned with the outliers in the model, like Grey Goo’s’ dearth of reactionary action and Sudden Strike 4’s lack of preparatory or anticipatory actions (as a for instance)

      I do think that defining a wide possibility space for different preparatory/reactionary/anticipatory approaches to succeed is really important for RTS to be deep and engaging in the long term, as you mention regarding SC2. It’s a tall order for any game to get these things right

      Like

  3. Hey, I enjoyed reading this, but I have to take issue with your judgment of Grey Goo. I agree that GG is almost completely “preparatory,” but I think there’s more depth there than you’re giving credit for. In fact, I think GG is closer to real-time strategy than even SC2 is. (I love and play both games). Coming to GG from SC2, I was continually beaten in the face until I started putting some serious effort into my macro. And by “macro” I don’t mean “harvest/build more stuff,” but build the right things, build the right defenses, etc. And that’s not static—you change it in response to enemy actions, etc.

    It is not for everybody. GG has no do-overs or panic buttons. But I quite like this—it really forces you to be disciplined and get things right ahead of time.

    Recently I’ve been playing some TEC in Sins of A Solar Empire, and have had much the same feeling.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s