Threats, Storms & Defense
Damage compounds. A storm turns one unshielded building into an outage, an outage into system failure, and system failure into a dead crew. Shield the core, keep a repair crew idle, and clear roots before they spread.
An outpost in Star Trek: Outposts Unknown rarely dies in one dramatic moment. It dies the way real infrastructure fails: a storm strips a roof, the outage stops a pump, the pump was feeding the building that made the part you needed for repairs, and by the time anyone notices the crew is sick and the repair queue is four items deep. Understanding the threat list is mostly understanding the order things cascade in.
What can actually hurt you
| Threat | What it does | Cheapest answer |
|---|---|---|
| Storms | Damage, outages, blocked routes | Repair crew on standby, shielded core |
| Power outage | Stops production, starts system failure | Surplus capacity, redundant generator |
| Water outage | Degrades every crew stat | Storage buffer, second source |
| Building damage | Integrity loss, needs an engineer | Pre-emptive upgrades, free engineer |
| Tetryon radiation | Raises crew saturation, can kill | Shield emitters over crew areas |
| Hostile roots | Spread, block survey routes | Security or Science clear them early |
| Nausicaan raids | Direct attack on crew and buildings | Security on perimeter, shield the core |
| Cold (Korou) | Kills crew outside heated space | Insulated quarters, medical cover |
Everything in the left column is survivable. Everything becomes lethal when two of them land in the same in-game day, which is exactly what the game's own "Murphy's Law" achievement describes: an attack, a storm, a power outage, a water outage and a building needing repair all at once.
Roots: clear them before they spread
Hostile root growths are the game's first real antagonist on the surface. They sit in the terrain and interfere with surveying; there is an achievement for destroying 20 of them, and one quest chain asks you to investigate an "Inert Root" rather than destroy it.
The investigation is the slow part. Assigning two scientists to an inert root can take several in-game days, so treat it as a background task rather than a blocker: keep the crew on it, keep building, and do not pull them off every time something else needs doing. Pulling a specialist off a long investigation is how a two-day job becomes a six-day one.
Nausicaan raids
Raids are the one threat that targets people rather than infrastructure. Security officers respond, and having two on the roster is the difference between a scare and a roster hole. Surviving a raid is an achievement, which is a useful way of saying that raids are meant to be survivable — but not free.
The response pattern: pull civilians off the perimeter, put security on the approach, and keep an engineer near the Ops Center. If a raid takes a building down, the repair should start while the fight is still happening.
Outages are the real boss
Two achievements measure this directly: one for completing a scenario without a power outage, another for twenty buildings hitting system failure. Both exist to tell you what the game thinks the primary failure mode is.
The fix is boring and it works. Keep a buffer: one more generator than you need, one more water source than you need, storage for a day of inputs. A base running at exactly break-even is a base one storm away from a cascade.
Weather and radiation events are what turn a small outage into a lost crew. Official media: Magic Fuel Games / Playstack.
Tetryon radiation
Radiation raises a hidden-but-tracked stat, Tetryon saturation, on every crew member inside the affected area. It is treated by a medic, and it kills if ignored. Shield emitters are expensive because they are the only real fix.
Placement matters more than count. An emitter's value is the crew inside its radius, so cover quarters, the Ops Center and the compute cluster first. A ring of emitters around the perimeter looks defensive and protects nobody.
The repair queue is a staffing problem
Buildings that fail need engineers. Engineers are also your best harvesters, your best builders and your best maintenance crew. Every time you let a repair queue grow, you are paying for it twice: once in the repair, and once in the work the engineer could have been doing.
Two habits prevent most of this. First, keep one engineer unassigned as a standing response. Second, upgrade earlier than feels necessary — a maxed building fails less often than a fresh one and costs less to keep alive.
Threat response checklist
| Situation | Do this first |
|---|---|
| Storm incoming | Queue repairs, pull night crew in, check water buffer |
| Power outage | Free an engineer, prioritise compute and water |
| Radiation spike | Medical on the affected crew, shift work inward |
| Roots near a route | Clear the route, then the approach |
| Raid | Security to perimeter, civilians out, engineer near Ops Center |
| Two events at once | Protect water and power first; everything else waits |