You have read the combat rules. You understand Hits, DR, Dodge, Evade, Initiative. Congratulations. None of that will save your encounter from being boring.
Two groups trading Hits back and forth until one side runs out of boxes is mechanically valid and narratively identical to watching someone else do their taxes. Your players will check out of the fight, and then they'll check out of your game. Probably on the same night.
The fix is simple: describe what will happen if nobody acts. Then let the players prevent it.
Before anyone rolls anything, paint the threat. Not "the Zod charges"; that's stage direction. Nobody buys a ticket for stage direction. Paint the consequence.
"The Zod breach-team is cutting through the bulkhead. In about six seconds that door is coming down, and the two of you on the other side of it are going to be standing in a kill-box. What do you do?"
Now the players have a problem to solve, not a turn to take. One flips a table for cover. Another rigs the door to blow back on the breach team. The Sec-Ops kills the lights and lets the squad's thermal optics do the talking. The Medic pre-positions behind a support strut for the casualties they know are coming.
None of that is "I attack the nearest enemy." All of it is combat. And all of it came from the players, not from you reading stat blocks.
Within their initiative group, players choose their own turn order; and it should change round to round based on what the situation demands. The player with the best idea goes first, not the player with the highest stat.
If two players want to coordinate, one suppresses while the other flanks, let them act back-to-back and describe the result as one fluid sequence. Then throw them a Boon for it. Do this every time the squad works together. Be generous. Sprinkle Boons like confetti at a victory parade. Players who learn that teamwork is mechanically rewarded will start planning together instead of playing solo, and that's where the cinematic moments come from. Nobody remembers the round they individually rolled well. Everyone remembers the round the squad pulled off something ridiculous as a team.
When an NPC lands a hit, don't just announce "you take 2 Hits" like a parking inspector issuing a fine. Describe what that means.
"The round punches through your shoulder plate; you feel the impact before the heat. Your left arm goes numb for a second and your HUD flickers. Mark 2 Hits."
When a player fails a Dodge roll:
"You're half a step too slow. The burst catches you mid-stride and spins you into the bulkhead. You're on the ground, ears ringing, staring at the ceiling tiles. Mark it."
The mechanics resolve uncertainty and track consequences. They are not the experience. The experience is the story those mechanics produce. "I failed my AF roll by 7" is a number. "My armour is falling apart and I can feel the next one coming" is a reason to care.
A failed roll should never mean "nothing happens." Nothing happening is the most boring outcome in the universe, and you have an entire universe to work with.
A failure means something worse happens. The Rigger fails to hotwire the blast door? It doesn't just stay shut; it triggers a lockdown alarm. Or it opens on a three-second delay instead of instantly, which is a lifetime when something with claws is on the other side. Or it opens fine but the wrong panel sparks and the Rigger takes a Hit of electrical damage for their trouble. "Congratulations, the door is open. Also you're on fire."
Failures advance the situation. They just advance it in a direction the players didn't want.
Grids and squares exist to resolve tactical ambiguity. They are a tool, not the world. When you describe a room, describe the room; the flickering overheads, the chemical smell, the half-collapsed catwalk, the floor grating you can see through to the level below. If a player asks "can I get to that catwalk?", then you consult the grid. Not the other way around.
Give your environments things to interact with. Fuel lines to rupture. Consoles to overload. Cargo containers to topple. Airlocks to cycle. Conveniently labelled emergency venting controls that absolutely nobody should press. If the room is just walls and floor, your players have nothing to do except shoot, and combat becomes the tax return you were trying to avoid.
Enemies are not damage-delivery systems that politely wait their turn. They have objectives; breach the hull, capture the engineer, reach the escape pod, hold the corridor until reinforcements arrive. When NPCs act with purpose, players respond to that purpose instead of optimising damage-per-round.
A Zod that ignores the fighters and sprints straight for the reactor core is more terrifying than one that politely attacks whoever is nearest. A pirate crew that grabs a hostage the moment they start losing is more memorable than one that fights to the last Hit like they've never heard of self-preservation. And a cornered enemy that detonates the fuel cache out of sheer spite? That's the story your players will be telling at the next table.
When NPCs are losing, they should act like creatures that want to survive. When they're winning, they press the advantage with the kind of overconfidence that creates openings for the players.
If a player is deliberating too long, the situation changes. The breach-team finishes cutting. The grenade lands. The transport lifts off without them. Combat has momentum, and stalling kills it. A firm but fair "the clock is ticking; what do you do?" keeps the tension where it belongs: on the players, not on you waiting for someone to finish mathing out their optimal action economy.
If a round is dragging because every player is making four sub-optimal attacks at the nearest target, something has gone wrong upstream. Either the threat isn't clear enough, the environment isn't interesting enough, or the encounter has outstayed its welcome. Fix the cause. Don't just speed up the symptom.
Use the calculator below to model AF vs TL probabilities for different origin/armour combinations. Adjust the TL slider to see how the squad fares against different threats, and use the AF Bonus to account for feats, abilities, and situational modifiers.
Model defence (AF / DF / EF) and offence (ATK) probabilities vs a creature's TL.