A good Beyond These Stars outpost is a small settlement with one clear purpose. Scout the system, identify what the world can provide, stabilize the city on Kewa, and only then send settlers. On the planet, build a local needs loop before the export chain. The outpost becomes valuable when its workers stay healthy and its product can travel all the way to a waiting consumer.
Scout and define the mission
Use System View to investigate a potential world with the Scout spaceship before committing a Settlement spaceship. Confirm that the target is settleable and identify the opportunity that justifies a permanent Peep presence. Write the mission in a short form: “produce a material unavailable on Kewa,” “support a required story objective,” or “establish a trade and logistics point.”
If you cannot name the mission, keep scouting. A new settlement adds homes, food, drink, labor, roads, storage, production, and monitoring. The planet’s visual appeal alone does not pay those costs.
Target
Confirm the world is settleable in the current System View and distinguish it from an event, barren object, or trade location.
Purpose
Name the resource, objective, or connection the outpost will provide to the wider journey.
Timing
Do not launch while food, Power, pollution, or Kewa health at home already needs direct intervention.
Capacity
Prepare the required ship and enough margin to establish homes, needs, roads, and the first production step.
Establish life before export
On arrival, inspect breathable and buildable space, water, fertile ground, deposits, and the route between them. Place accommodation so residents can reach the first essential jobs. Then secure food and drink, connect roads, and confirm a complete work-and-break cycle.
Do not begin with the valuable export factory if its workers have no stable home loop. A stalled remote producer is harder to diagnose because attention keeps returning to Kewa. Local resilience makes every later shipment more reliable.
Temperature and terrain can change crop and settlement decisions. Use the conditions displayed for that planet in the current client. Do not import a map or recipe assumption from the Demo, Playtest, or Before We Leave.
Build one end-to-end export chain
Run one shipment before doubling production. Follow the cargo from the local Building to storage, through the ship connection, into Kewa’s storage, and into its final consumer. Every invisible handoff is a possible pause point.
Manage two settlements without losing either
Set a compact check routine. On the outpost, inspect needs, staffing, Power, output, and export. On Kewa, inspect homes, essential resources, generator by-products, pollution, and Kewa’s condition. Alternate on a predictable rhythm rather than staying on one map until an alert appears.
Keep a reserve of common construction and repair goods where each settlement can access them. A broken or blocked essential Building should not require waiting for a long logistics chain before any recovery can begin.
If one settlement enters a crisis, pause optional growth in the other. A synchronized expansion can consume the same transport or management capacity at both ends.
Leave room for Kewa’s travel choices
Kewa uses Energy while traveling and may detour to eat. Temperature can also make a long stay undesirable. Do not build an outpost plan that assumes Kewa will remain beside the planet forever or depart at an exact moment. Finish the critical local needs and transport steps while the opportunity is available.
The official developer material emphasizes that Kewa is a partner with agency. A strong relationship and healthy biome support the journey, but the safe operational choice is still to make each settlement robust between visits.
Sources and boundaries
- Official Galaxy page for System View, ship roles, map points, and Kewa travel Energy.
- Developer settleable-planets article for the intended outpost role and return-to-Kewa relationship.
- Independent Planets and Outposts guide for current 1.0 player workflow. Exact planet inventories, ship costs, and capacities remain current-client checks.