Engineer

Engineering is the console the rest of the ship runs on. You do not fly, shoot or scan — you decide how much of a finite power supply each of those gets, and you put things back together when they break.

It is the role where good play is least visible and bad play is most obvious.

Power

Every component on the ship has a charge level, and three numbers that matter:

• Idle — what it draws doing nothing.
• Optimal — the level it is designed to run at. This is what "100%" means on your displays.
• Maximum — the ceiling, and it is higher than optimal.

That last one is the interesting part: components can be pushed past their optimal level. A shield generator designed for 1000 will take 2000. Overcharging is real, available, and paid for out of everything else — there is one supply.

Levels ramp rather than jump, so a big reallocation takes time to arrive. Move power before it is needed. Power shifted to shields as the first shot lands arrives after the second.

Component states

A component is in one of five states, and "off" is not one thing:

Enabled is separate from online. A component has to be online before it can be enabled, and an online component that is not enabled does nothing. Two different problems with two different fixes: an offline component needs repair, a disabled one needs switching on.

And a component may refuse to be enabled because of the ship's alert condition — shields below Yellow, weapons below Red. That refusal is reported to your console and to Tactical, and it is not a fault. It is Operations' job to fix.

Damage control

Your ship has a fixed pool of damage control teams, and you control two things about them.

Priority. You order the damaged component list. Teams work down it from the top.

Distribution. How concentrated the teams are:

These are genuinely different strategies, not difficulty settings. Top mid‑fight to get shields or engines back now. Even afterwards, to tidy up everything at once. And note that priority order only does anything in Weighted or Top — in Even mode the teams are spread regardless, so reordering the list accomplishes nothing.

Shields, from your side

Tactical fights with the shields; you own their supply and their tuning. Your console has shield frequency and the shield balance control, and both matter more than they look:

• Balance moves charge between facings. A segment allowed to reach zero takes several times longer to begin recharging than one merely damaged — so balancing a weak facing before it collapses is worth far more than restoring it after.
• Frequency can be retuned, and randomised. A scan of your ship reveals your frequency offsets; randomising is how you stop an enemy reading them.

Fabrication and stores

If your vessel has a fabricator you can build things from recipes, which is how a long mission replaces what it has used up. Work orders and the ship's store sit alongside it. On a short combat mission this is scenery; on a long haul it is a significant part of the role.

Being good at it

• Announce the trade. "More to engines means less to shields" is information the Captain needs before deciding, not after.
• Pre‑position power. Levels ramp. Anticipate.
• Learn the two distribution modes you will actually use. Top during, Even after.
• Check state before reporting a fault. Offline, disabled and jammed look identical from the bridge and need three different responses. Jammed in particular is somebody attacking you, not something breaking.
• Do not chase the alert lockout. If Tactical cannot arm, that is Operations, not you. Say so and move on.
• Balance shields between passes. The quiet moment is when this role earns its keep.
• Volunteer bad news early. A Captain told now that the FTL drive needs two minutes can plan. Told in two minutes, they cannot.