Why combat in Fortress resolves simultaneously

For most of development, combat in Fortress worked the way you would expect: you attack, damage applies, then the opponent responds. It was legible. It was also boring, and it took us an embarrassingly long time to work out why.

The problem with going first

When damage applies in order, the player who moves first in an exchange wins it. That collapses the whole game into a race — get there first, hit first, win. Every interesting positional idea we built got flattened by the same question: can I reach it this turn?

Simultaneous resolution removes the reward for arriving first. Both sides deal their damage at the same instant, so attacking something that can hit back is genuinely dangerous even when you are stronger.

What it unlocked

Once trades became mutual, reinforcement started mattering. A piece alone dies in the exchange it wins. A piece with two allies beside it survives and the attacker does not.

• —Attacking became a cost, not a free action
• —Formations became defensive structures instead of decoration
• —Sacrifices became a real tactic, because you can price them

The rule that made the game harder to explain is the rule that made it worth playing.

The cost

It is harder to teach. New players attack something, lose the piece that attacked, and feel cheated. We added the combat preview specifically for this — before you accept a turn, you see exactly what dies on both sides. The preview did more for our retention numbers than any tutorial we wrote.