Lancer vs D&D: How Combat Actually Works Differently (And Why Sitreps Change Everything)

If you're coming from D&D and you sit down for your first Lancer combat, something will feel off. The hex grid is new but the concept is familiar. The tokens are there. You're rolling dice. But about ten minutes in, you'll realize you're playing a fundamentally different game - and it has nothing to do with mechs.

Lancer is a tabletop RPG by Miguel Lopez and Tom Parkinson-Morgan where you play mech pilots in a far-future science fiction setting. It's free (the core rules are available through COMP/CON), it's gorgeous, and it has some of the best tactical combat in any TTRPG on the market.

But if you approach it like D&D with robots, you're going to have a bad time.

Here's why - and what D&D can learn from it.

D&D Combat: The Comfortable Default

D&D combat follows a loop refined since 1974: roll initiative, take turns, reduce enemies to zero hit points, collect rewards. The DM builds encounters around Challenge Rating, action economy, and resource attrition across an adventuring day.

Objectives exist in D&D - protect the NPC, stop the ritual, escape the collapsing dungeon - but they're layered on top of a combat system that fundamentally asks one question: can you defeat what's in front of you?

Even when an encounter has a creative objective, the most reliable solution is usually "kill everything first, then do the thing." Protect the NPC? Kill the attackers. Stop the ritual? Kill the cultists. Escape the dungeon? Kill whatever's blocking the exit.

This isn't a flaw. D&D is heroic fantasy, and heroic fantasy means fighting monsters. But after a few hundred sessions, combat can start to feel same-y. Initiative. Fireball. Eldritch Blast. Healing Word. Repeat.

Lancer Combat: What's Actually Different

The Action System

D&D gives you an action, a bonus action, movement, free actions, and a reaction. Lancer's economy shares some of those bones but builds something completely different on top of them.

Every mech gets a move action plus either two quick actions or one full action, plus free actions and an overcharge option that lets you squeeze out extra actions at the cost of heat. Quick actions include things like skirmish (attack with one weapon), boost (extra movement), quick tech (one invade/hack), or activate a system. Full actions follow the same scaling principle but bigger - barrage (attack with two weapons), full tech (two invades), or stabilize (recover and cool down).

This means every turn involves real choices about how to spend your economy, not just "I attack twice." Do you skirmish and boost to reposition? Barrage to maximize damage but stay planted? Overcharge to squeeze in a third action and risk overheating? The decision space is wider on every single turn.

Initiative: Back and Forth

D&D rolls initiative once and locks in a turn order for the entire fight. Lancer throws that out entirely.

Players always go first. Then play alternates: one player turn, one GM turn, back and forth. But here's the key - the players choose which player character takes each player turn, and the GM chooses which NPC takes each GM turn.

This creates constant tactical conversation. "I'll go first to lock down that zone - then you follow up with damage." "No, let me go first to push that enemy into your line of fire." Initiative becomes a team decision every single round, not a number you rolled at the start. It rewards communication and coordination in a way D&D's static initiative simply can't.

If there are more players than NPCs (or vice versa), the larger side gets extra consecutive turns at the end of the round. If players end the round, enemies act first next round - so there's a real cost to having that numbers advantage.

Reactions: Per Turn, Not Per Round

In D&D, you get one reaction per round. Period. You use your opportunity attack on the first enemy that runs past you, and you're done until your next turn.

Lancer gives you one reaction per turn - meaning per each other character's turn, not per round. If three enemies activate near you over the course of a round, you could potentially react to each of them.

Most individual reactions are still limited to once per round - your Overwatch (Lancer's version of an opportunity attack) can only trigger once per round, and a specific defensive reaction like Brace (halving incoming damage) can only fire once per round. But because different reactions have separate once-per-round limits, you could Overwatch on one enemy's turn and Brace on another's.

This makes the battlefield feel alive on every turn, not just your own. You're never "off" - there's always a decision to make about whether to spend a reaction now or save it.

Structure, Stress, and Heat

Mechs don't just have hit points. They have HP, Structure, and Stress.

When your HP hits zero, you take structure damage and roll on a table - your mech might lose a system, lose a weapon, pick up a debuff, or - if you've already lost enough structure - be destroyed outright. Stress works similarly but for your reactor: overheat too many times and your mech melts down.

Heat is generated by powerful weapons and systems. Accumulate too much and you overheat, taking stress damage and potentially shutting down. Your strongest abilities actively risk cooking you inside your own cockpit. A D&D wizard might run out of spell slots, but they won't explode for casting too many fireballs.

This staged destruction means mechs degrade in combat. A mech at 1 Structure and 2 Stress is falling apart - and that feels different from a D&D character at 1 HP who functions identically to one at full health.

The Real Difference: Sitreps

Everything above makes Lancer's combat feel mechanically distinct. But what makes it feel like a different game is sitreps.

A sitrep (situation report) is a pre-built mission framework that defines what you're actually trying to accomplish in combat. It's not a suggestion. It's the win condition.

And "defeat every enemy on the battlefield" is just one of many.

Control

Objective: Hold specific zones on the map. Score points for controlling areas at the end of each round.

Killing enemies helps - but only if they're contesting your zones. That mech on the far side of the map? Ignore it. The one standing on your control point? Priority target. Suddenly you're deciding which fights matter.

Holdout

Objective: Defend a position for a set number of rounds against waves of enemies.

You can't kill everything - they keep coming. Victory means surviving, not winning. Do you burn your best weapons now and risk overheating later? Do you give ground to consolidate, or hold the line and risk being flanked?

Extraction

Objective: Get something - or someone - out of the combat zone alive.

The fight is shaped around movement toward an exit, not damage. Enemies become obstacles to bypass. The player who specializes in crowd control and repositioning suddenly matters more than the one with the biggest gun.

Escort

Objective: Protect a person or object while moving it across the map. The escort doesn't move on its own - it moves with whoever is adjacent to it when they take their standard move.

The catch: enemies want to capture it, not destroy it. And if both sides have characters adjacent to the escort, it locks in place and can't move until one side clears out. This turns every escort fight into a tug-of-war where positioning and zone control matter more than raw damage.

Gauntlet

Objective: Move your team through hostile territory from point A to point B.

Standing and fighting is a trap. Every round in combat is a round you're not moving. The optimal play is often to suppress, push through, and leave enemies behind - a concept that feels wrong to D&D players trained to clear every room.

Recon

Objective: Infiltrate hostile territory and identify the true objective among multiple possibilities. The GM places several control zones across the map and secretly designates one as the real target. Players must push into enemy territory, spend actions scanning each zone, and hold the correct one by the end of round six.

This combines the tension of control with an information game. You're not just fighting - you're investigating under fire, splitting resources between probing multiple locations and holding ground once you find the right one.

And Yes - Defeat All Enemies

This sitrep exists too. Sometimes the mission really is "kill everything." But it's a specific scenario, not the default assumption. Because it's one option among many, it feels intentional rather than routine.

Why Sitreps Are What D&D Should Steal

The shift from "defeat enemies" to "complete objectives" sounds simple. It rewires how every part of combat works.

Builds matter differently. In D&D, optimization usually means maximizing damage. In a sitrep framework, a support character who can lock down zones, reposition allies, or shield the escort is just as valuable. Team composition becomes a real conversation.

Positioning becomes the game. When the objective is a location - a control point, an extraction zone, a defensible position - where you stand matters more than what you hit.

Combat has built-in pacing. D&D fights often follow a bell curve: ramp up, climax, mop up stragglers. Sitrep fights have tension baked into the objective. A holdout gets harder each round. An extraction has a ticking clock. A gauntlet punishes you for slowing down.

"Kill it" stops being the answer. When your win condition is "hold this zone for 6 rounds," killing that enemy might take 3 rounds you don't have. Pushing it out of the zone takes 1.

How to Use Sitreps in D&D Tonight

You don't need to switch systems. Steal the framework:

Define the objective before the monsters. Instead of "the party fights 6 gnolls," try "the party has 5 rounds to collapse the tunnel before reinforcements arrive." The gnolls are obstacles, not the point.

Make "defeat all enemies" impossible. Infinite reinforcements. Enemies that flee when losing (because they have their own objective). Foes too powerful to fight head-on.

Give enemies objectives too. The bandits aren't trying to kill the party - they're trying to steal the wagon. The cultists aren't fighting to the death - they're stalling while the ritual completes. Both sides racing toward goals makes combat write its own story.

Use a timer. Rounds until the bridge collapses. Rounds until the hostage is moved. A countdown reframes every decision from "what deals the most damage?" to "what gets us closer to winning before time runs out?"

So Which System Is Better?

Neither. They're optimized for different experiences.

D&D excels at heroic fantasy where your character's identity - their class, their abilities, their personal story - drives the adventure. Combat is one part of a broader game that includes exploration, social interaction, and narrative progression.

Lancer excels at tactical teamwork where mission variety, mech customization, and objective-driven encounters create a different kind of satisfaction. The narrative layer exists (and it's good), but tactical combat is the star.

If you try Lancer, you might find it fills an itch D&D never quite scratched — the desire for combat that feels like a puzzle rather than a gauntlet.

If you haven't tried Lancer, the core rules are free through COMP/CON and the full rulebook is available from Massif Press. Give it a shot. Your D&D encounters will be better for it either way.