“Make it faster” is the most dangerous note in game design, because everyone hears something different. Players hear “fewer choices.” Designers hear “fewer rules.” What we meant was neither - and the misunderstanding has killed more good combat systems than any bad mechanic ever has. The confusion is understandable. Most slow games are slow because they’re complicated, so “fast” sounds like “simple.” But complicated and slow are two different problems wearing the same coat, and treating them as one is how you end up “fixing” combat by removing everything interesting from it.
Two Different Problems
Complicated is procedures between decisions: roll to hit, roll damage, check the chart, apply the modifier, make the save, resolve the trigger. Slow is waiting between decisions: your turn ended four minutes ago and the goblins are still going. You can fix either one without touching the other - and if you only fix one, your players will tell you the game still drags, and they’ll be right.
Picture two tables. At the first, the rules are simple - attack, defend, move - but twelve combatants take turns in order, and every round takes twenty minutes. At the second, the rules have real texture - weapons matter, armor matters, injuries matter - but the fight never stops moving and an hour vanishes. Ask the players which game felt “fast” and they won’t mention the rulebook. They’ll talk about the waiting.
What we wanted from Mayhem was never fewer decisions. We wanted fewer delays. The player deciding whether to press an advantage, change position, protect an ally, conserve effort, or take a risk - that’s the game. Everything between that decision and the next one is overhead. Overhead is what we attacked.
What Speed Achieves: the Answer Arrives While You Still Care
When one roll tells you what happened - the hit, where it landed, how hard, what kind - the interesting part of your turn isn’t followed by five minutes of administration. You stay in the moment. The fighter who chose to attack the ogre learns the outcome while the choice still feels like his.
That doesn’t just save time. It keeps the decision emotional. Ask anyone who’s waited ten minutes to learn whether their brilliant plan worked: by the time the answer arrives, they’ve already stopped caring. They’re not invested anymore - they’re just processing. Speed protects the feeling that your choices matter, because the game answers you while you’re still the person who made the choice.
What Speed Achieves: Detail That Earns Its Keep
Pain matters. Stub your toe on a table leg and you won’t die - but for the next few seconds you will be deeply, personally interested in your toe. A fight is full of moments like that: real, consequential, and not worth a spreadsheet.
So we drew a line. The injuries that change your decisions get tracked. The rest get felt and forgotten. That isn’t simplification - it’s triage. The texture stays. The accounting goes.
This is the standard we started applying everywhere: detail should earn the time it costs. A rule that adds a decision earns its time. A rule that adds a procedure between decisions has to justify itself. Most of them couldn’t. What survived wasn’t the simplest version of combat - it was the version where everything left on the page was pulling its weight.
What Speed Achieves: the Game Teaches Itself
And here’s the one people miss. Fast compounds. A game that resolves quickly gets played more in the same evening - which means players learn it faster - which means it plays faster still. Speed isn’t just pleasant. It’s how a tactical game teaches itself. The tenth fight teaches what the rulebook couldn’t, because you actually got to the tenth fight.
There’s a veteran’s fear hiding under all of this, and we should name it: if the game is fast and the rules are lean, does mastery still matter? Will the experienced player still beat the new one? Yes - but the mastery moved. It’s not in memorizing charts anymore. It’s in reading the fight: knowing when the advantage is yours to press, when it’s slipping, when the clever move is to stop attacking entirely. That kind of mastery doesn’t come from the rulebook. It comes from the tenth fight. Which you got to because the first nine didn’t take all night.
What Speed Achieves: the Epic Battle Becomes Playable
And then there’s the problem we raised back in the third article: the epic battle. A dozen enemies, a few allies, the great beast everyone’s been hearing about for six sessions - magnificent on paper, miserable in a turn queue, because every creature you add is another place in line. The bigger the battle, the longer everyone waits. Scale punished excitement.
Remove the line and that relationship inverts. Twenty participants stop being twenty turns and start being twenty things happening in the same roaring chaos - which is what an epic battle was supposed to feel like all along. The climactic fight can finally be climactic, instead of being the evening everyone remembers as “the one where we waited.” Speed doesn’t just make small fights pleasant. It makes big fights possible.
So here’s the distinction we keep coming back to: simple removes choices. Fast removes waiting. A game with deep choices about weapons, armor, injuries, and position can still move like lightning - if the time between decisions shrinks instead of the decisions.
We didn’t want a simple game. We wanted a game that respects your evening. There’s a difference, and your players will feel it in the first hour.
Next from the Engine Room
Which leaves the biggest question of the series. Can all of this - no initiative, no turns, real speed - actually be tactical? Or does tactics require the very machinery we’ve been dismantling? Next time: Can an RPG Be Tactical Without Being Slow or Complicated?