【Factorio】Space Platform Design & Operations: 3 Key Patterns

In Factorio: Space Age, the difference between space platforms comes down to whether they keep running smoothly, not just getting them built. This guide breaks down the journey from docked minimum setups through first flight to mass resupply in three stages, systematically tackling the pain points that catch most players: automatic requests, load conditions, ammo depletion, and the relationship between hull width and speed.

This is aimed at players attempting space travel for the first time, or those whose platforms launch but stall due to misaligned resupply chains. I've stripped the advice down to reproducible design steps. Space platforms don't get stronger just by being bigger—they stabilise when you separate necessary functions by stage and build each one properly.

What Are Space Platforms in Factorio? Prerequisites and Version Notes

Overview of Elements Added in Space Age

The space platform fundamentally changes Space Age's pacing beyond the vanilla feeling of "launch rocket, job done." Space Age is a paid expansion released on 21 October 2024, introducing space platforms alongside four new planets and a restructured tech tree designed around reaching them. As shown in Space Age - Factorio Wiki and Upcoming features - Factorio Wiki, post-launch production and logistics design shifts considerably under the DLC.

Space platforms aren't just orbital outposts. They function as factories and transports to other planets—that's the key distinction. Your first platform starts from a starter pack launched via rocket, beginning with just a hub and minimal floor. You then expand flooring, add power, production, defence, and propulsion. Unlike ground factories, platform floor management becomes an operational constraint, and losing your hub means losing the entire platform—a total-loss risk that shapes design decisions fundamentally. Floor removal mechanics and costs may vary by version.

Community practice often frames rocket payload capacity as roughly 1 tonne. Bundling small materials this way eases initial setup bottlenecks.

速度設計では、理論上の最大値に寄せすぎない方が結果的に強いです。
スラスター効率は非線形なので、ぴったり計算で攻めるより、分散供給と出力制限を前提に少し余裕を持った燃料系を組む方が、往復運用でははるかに安定します。
特に初回の惑星間輸送では、最高速よりも「燃料が尽きず、指示した往復を繰り返せる」ことの方が価値があります。

I fell into the trap of treating "rocket launch = late-game credits," delaying space engagement. But in Space Age, that's actually the entry point. Even a minimal docked platform in Nauvis orbit begins collecting asteroids and producing space science packs. In other words, orbit is better understood as a new logistics layer and new production tier rather than just flashy scenery.

Space Age

wiki.factorio.com

Target Audience and Prerequisites for This Guide

This page targets players who reached rocket launch in vanilla and are touching space platforms for the first time in Space Age. The level sits between beginner and intermediate—specifically for those saying "platform's built but operations aren't stable" or "ground supply and orbital demand don't align."

The assumed version is Factorio 2.0 + Space Age DLC. This matters significantly. Carrying vanilla rocket and old space science assumptions straight across breaks early narrative. For instance, space platforms become logistics hubs and production sites in Space Age, with research progression built around planetary progression. Beacon scaling also changed in 2.0, so the old "just stack them" approach easily leads to design errors.

Terminology Clarification

Here I'll establish definitions likely to cause confusion later.

Space platform is a Space Age-exclusive orbital base. Centre the hub, expand flooring, add equipment to industrialise it. Set a destination and it becomes a resupply post or interplanetary cargo ship. Operation feels like ground base meets rail system; destination UI parallels timetables.

Platform hub is the platform's core structure. It handles resource transfer and construction starts. Losing it means losing the whole platform. Think of it as mission control plus central warehouse—protect it before ancillary equipment.

Platform flooring is your footprint for equipment. You add it like ground landfill, but design freedom differs. Large cutouts later become awkward, and rework happens frequently. Flooring removal mechanics and costs shift by version—check the Factoriopedia beforehand.

Asteroid collector harvests nearby asteroids. Instead of ore patches, space uses incoming objects as resource entry points. Feed collected material to the next processing stage—that's space production's foundation.

Crusher converts harvested asteroids into resources. Rather than ore belts appearing instantly, space has a "collect then crush" stage. Recognising this difference clarifies why you need both collectors and crushers.

Space science pack is critical for Space Age progression. Though named after vanilla's satellite-based science, Space Age treats it as a platform production chain far more often. Conflating the two easily loses your post-rocket narrative.

Automatic request is when the platform requests resupply, launching rockets automatically from the ground. Crucially, the ground rocket silo must accept auto-requests and hold sufficient stock in your logistics network. Configure the source planet too, or requests sit idle—this junction is where most early stalls occur.

Cargo landing pad is your orbital receive point. It acts like a request chest but accepts only one stack per delivery. This constraint often becomes the real bottleneck, not transport capacity.

This section establishes prerequisites. Coming sections treat "docked and running" then "flying and delivering" in stages, deconstructing platforms as factories.

Setting Up an Initial Space Platform: Minimum Viable Configuration

Launching the Starter Pack and Initial Layout

Your first goal is docked outpost, not flying ship. Begin by launching the space platform starter pack via rocket. Immediately after, you'll have a hub and minimal flooring—less like a factory extension, more like "bare-essentials machinery in orbit."

Critical here: don't sprawl the initial flooring carelessly. As noted, platforms expand but don't easily allow you to re-route like ground factories do. Those first dozens of tiles heavily constrain future layout freedom. I initially laid out a plaza-like expanse before placing collectors and crushers, ending up with twisted conveyors needing complete rebuilds. Keep collector, crusher, and hubs close—gather reception and production near the hub, extend collectors outward.

Layout thinking is straightforward: hub centre, with four zones—power, collection, crushing, science—connected at minimal distance. Docked platforms need no propulsion or major defence initially. Nauvis orbit works well as a startup location; accumulate asteroid resources here, generating space science packs by stage one.

Community practice often frames rocket payload capacity as roughly 1 tonne. Bundling small materials this way eases initial setup bottlenecks. Official numbers vary by version and source, so confirm against Factoriopedia or official Wiki before committing.

Split ground reception early for stability. As Cargo landing pad - Factorio Wiki shows, pads accept one stack at a time. Receiving everything via one pad creates queue bottlenecks: floor material waits, then batteries, then inserters. My first platform stalled precisely here. Splitting by category—construction supplies separate from consumables—dramatically improved flow.

Cargo landing pad - Factorio Wiki

wiki.factorio.com

Power Assurance: Solar and Accumulator Placement

Initial platform power comes from self-sufficient solar + accumulators. No fuel generation needed, keeping logistics light and suiting docked startup well. Solar panels peak at 60 kW during day, average 42 kW; accumulators store 5 MJ each and discharge at max 300 kW.

Math makes placement clearer. To sustain ~500 kW continuously, roughly 12 solar panels (42 kW average) gives a rough baseline. Pair with accumulators at roughly 10 units following the community 25:21 ratio common on wikis. Accumulators discharge at 300 kW momentarily but hold only 5 MJ, so distinguish between "peak output" and "night duration"—conflating them breaks design.

Place solar on outer perimeter, accumulators hub-side for future expansion. Platforms need fewer pole-routing gymnastics than ground factories, so floor usage directly equals design quality. Reserve a power strip upfront; extending collection or assembly lines later just needs supply attachments, not rework. Central scattering breaks every time you expand.

For docked platforms, stabilise power first. Collectors and crushers halt when power drops, closing your resource gate. Extra solar here is pure production gain, not insurance.

Asteroid Collector and Crusher Loop

Once power flows, build the shortest collector-to-crusher loop. Orbit requires harvesting incoming asteroids instead of mining ore patches. Collector alone or crusher alone doesn't make a factory. What matters is an unbroken flow from collection through crushing to next stage.

Minimum viable: place collectors on platform edges facing outward, crushers immediately inboard, close together. Why? Inbound matériel spans extra floor, draining the 1-tonne launch budget. Shorter distances = fewer initial deliveries needed.

Bottleneck here isn't processing speed but output placement. Place crushers without planning their outlet and immediate neighbours choke from internal backup, stalling collectors. I ignored this initially—collectors ran fine, but resources never grew. Truth is: collect → crush → buffer/next stage in one line stabilises faster.

Docked platforms skip perfect sorting. First: get one stable loop flowing. Abandon main-bus aesthetics; get flow-through working first. Expand by adding parallel collectors/crushers later, but the minimum single-line stability is the asset. Modular single lines help later role separation anyway.

Minimum-Viable Space Science Line

Docked platform success is continuous space science pack production, however thin. Space Age lets you run orbital science generation without travelling, making this the first completion milestone before planetary pushes. Assembly: asteroids collected → crushed → resources → optionally refined → assembled into packs.

Key here: unbroken material flow beats throughput volume. This isn't a high-speed mega-base. One stable feed matters more than parallelised assemblers. Ground shortage supplies via cargo pads (respecting their 1-stack-per-hit rate), so split request categories. Bundling all requests crashes pads with queue chaos; separate demand by supply function.

Practical layout: assemblers and output near hub; collectors and crushers toward platform edge; power mid-strip or background. Ground supplies complete hub-side; orbital resources flow inward. Resist micro-optimising ratios at this stage. Build that single thin continuous science line, not a production powerhouse. Scaling applies later when spinning off specialist ships, and independent minimal lines split cleanly.

Once science packs flow, your docked platform graduates from "floor in space" to "working factory." You've earned the foundation for resupply automation and travelling ship designs.

Core Design Philosophy: Hub-Centric, Vertical Layouts, Role Separation

Hub Protection and Redundancy

The principle to lock in first: platform survival beats production aesthetics. This is the sharpest difference from ground factories. Losing a hub doesn't disable part of the platform—it destroys it entirely, a total-loss scenario. Design around this before layout beauty.

Three defence basics: shielding, distance, and redundancy. Shielding means surrounding the hub with disposable structures—other equipment or plain flooring—to block line-of-sight. Distance places incoming-asteroid-heavy zones (collectors, crushers, ammunition) away from the hub, preventing spill-over damage. Redundancy avoids single points of failure in logistics, power, or supply. It's not duplicate hubs but splitting critical feeds across multiple paths.

Flooring strategy matters hugely. Platforms expand easily but punching holes later is hard. Densely packing core structures limits future supply lines and defensive additions. I packed the centre with equipment, then struggled when ammunition and fuel lines had nowhere to route except hub perimeter—weak and inflexible. Reserve hub-adjacent space as a future-use buffer, not immediate settlement. Plan supply inlets and fuel routing separately from launch day.

Docked setups skip some complexity, but good hub habit here transfers to every platform.

Why Vertical Layouts Win

Horizontal layouts look easier to fill. Initial solar, collectors, crushers line up nicely. Running it operationally reveals the downsides: speed suffers, piping long-routes across the width, and defence thinly spreads. I built horizontally initially, got slower ships, complex plumbing, and weak forward armour. Switching to vertical eliminated half my problems.

Here's why: width amplifies propulsion drag and muddies role boundaries. For travelling platforms, separating harvesting (bow), production (waist), and propulsion (stern) cleanly is essential. Horizontal sprawl blurs these zones, requiring ammunition and fuel lines to cross the width repeatedly. Each revision tangles it further.

Critically: thrusters can't attach to the south side of the platform. This design constraint strongly favours bow-to-stern layouts. You can't easily place functional zones aft of engines, so expansion naturally flows fore-to-aft—adding height and length instead of width.

This shape unlocks cleaner zones: bow defence and collection, waist hub and production, stern fuel and thrusters. Each region owns its purpose, damage is predictable, and piping runs linearly (fewer kinks, easier balancing). Upcoming features - Factorio Wiki platform specs suit this segmented approach.

Flooring expansion rewards vertical thinking. Digging later holes isn't an option, so commit to fore-to-aft arterial flows and side branches early. Horizontal expansion consumes future "routing corridors." Vertical lets you keep those.

Width roughly pinches utility past 30-tile range in common practice, though specifics vary by design and play. Test narrow first; adjust mid-game if needed.

Upcoming features

wiki.factorio.com

Separate Docked vs. Travelling Design Philosophies

Critical: don't design docked and travelling platforms identically. Performance requirements differ completely. Docked platforms need negligible propulsion and focus on safety and production stability. The science outpost from earlier sections exemplifies this.

Travelling platforms need propulsion, defence under way, resupply while moving, and damage resilience. "Can it fit?" flips to "can it sustain flight?" Docked-derived designs look sound parked but reveal cracks immediately: thin thrusters, forward-heavy defence, fuel lines too long, no redundancy. I often tried extending docked platforms, only to find mid-flight failures.

Design separation's value: each gets optimised for its actual job. Docked platforms add production margin; travelling platforms add ammunition routing, fluid trunks, and defensive depth. Merging both into one half-baked frame wastes effort. Conversely, docked platforms yield solid science while you refine travel craft, then role-separated specialists handle long-haul with far fewer accidents.

The split approach—docked for goods, travelling for transport—integrates hub protection, vertical layout, and forward-to-aft role division cleanly.

Propulsion and Speed: Thruster Count, Width, Fuel Supply Strategy

Hull Width and Thruster Placement

When a travelling platform won't accelerate, first check width versus thruster coverage. Platforms sprawl horizontally easily, inviting broad builds. Actual cruise performance depends strongly on sustainable thruster density, not feature count. My wide designs felt capable but flew sluggishly until I rebuilt vertically.

The issue: wider ships need wider engine banks. Empirically, width past ~30 tiles invites disadvantage, though your mileage varies. The core constraint is that thrusters occupy stern space, so width also stretches engine placement. Slender hulls with dense stern engines accelerate better than sprawling ones with spread thrusters.

Optimal thruster arrangement: short and thick, not long and thin. Concentrate engines at the stern, keeping fuel trunks brief and managing the thruster section as one functional block. This pairs well with fore-to-aft layouts: production waist benefits, stern propulsion segregates, central hubs thrive.

Visually, wide feels "good for cargo." In practice, ships are propulsion-first vehicles, fitting cargo into remaining space. Speed failures and fuel problems often vanish when you tighten width before adding thrusters.

Fuel and Oxidiser Supply Ratio Principles

Overlooked: distribution across thrusters beats raw throughput to one. I assumed "concentrated fuel = stronger." Numbers suggest otherwise: thruster efficiency isn't perfectly linear.

In-game, thrusters at 120/s represent 200% efficiency—the sweet spot. Lower fill ratios get more effective push-per-unit. One engine maxed uses ~52% of a 37.5/s chemical plant output, versus 29% per engine × 2 = 58% total when splitting evenly. Distributed supply outperforms concentration.

Practically, 1 chemical plant feeding ~4 thrusters balances easily, tolerates uneven feed, and scales steadily. Avoid starvation and overspend by this metric rather than chasing theoretical maximum. Early-mid routes work comfortably on this ratio, relying on wiki efficiency bands rather than formula-perfect tuning. Effective bands matter more than ceiling values.

Speed Control: Pump and Circuit Throttling

Propulsion doesn't self-stabilise. Controlled fuel flow—only when needed, only as much as needed—prevents fuel starvation or pre-arrival waste.** Floating dead is caused by overconsumption as often as underfueling.

Pump + circuit control throttles supply. Gate fuel flow by tank reserves or arrival flags. Full acceleration during departure burn, cruise feed mid-transit, modest sip near target. This lets you segment power modes: launch, cruise, coast, idle. Pomp max throughput ~1200/s, so bottlenecking comes from conditional logic, not hardware.

Don't design for maximum speed. Non-linear efficiency rewards distributed feed and output limits over peak-value hunting. Early interplanetary routes value round-trip completion over speed records. Sustainable supply + commanded round-trips > theoretical maximum.

Logistics Design: Automatic Requests and Rocket Launching Without Gridlock

Activating Auto-Requests and Load Conditions

Space platform resupply's most common jam: "request issued but no rocket launches." Root cause: auto-requests enabled on the platform, yet the ground logistics network lacks stock meeting full-rocket load conditions. Despite "automatic" suggesting incremental refill, platforms need pre-accumulated groundside reserves. The network launches complete payloads once ready—not dribbles on demand.

This design thinking is critical. I expected request-chest-like behaviour: shortage triggers instant trickle. Reality: ground-side must accumulate launch-weight quantities. Concrete and belts are predictable consumers, but ammunition and repair kits scatter and fall short easily. The bottleneck isn't launch capacity but ground inventory maturation.

Space Network - jp Wiki and its mechanics section clarify: requests + ground stock must both exist. When rockets stay silent, audit ground logistics for full-load readiness before eyeing launch equipment. I lost time here; the culprit was load thresholds, not supply shortfalls.

Space Network - factorio@jp Wiki*

wikiwiki.jp

Small-Item Loads and Minimum Launch Weights

Another trap: small-quantity items don't auto-launch. Platforms requesting a few construction pieces or spare equipment encounter minimum-load cutoffs. Auto-requests handle bulk well, stumbling on small parcels. High minimums silence minor resupply—floor tiles, backup devices, repair stocks sit idle.

This catches you during platform expansion or emergency repair, the exact moments you need those items. Nothing looks broken (auto-setup looks complete), yet one item class starves silently.

Countermeasure: either manual-launch small batches or circuit-split small allocations. Trusting auto-requests wholly fails on diverse, low-volume goods. Bulk flows auto, consumables manual or circuit-routed—dual-system thinking, not monolithic.

Designating Source Planets and Orbital Slots

Unspecified resupply source breaks otherwise-configured requests. Auto-request alone won't work; declare which planet provides what. Multi-planet operations amplify this: inventory might exist on-network, yet wrong-planet assignment means no delivery. Separate demand by intended source—ores from Vulcanus, organics from elsewhere—into distinct per-planet requests, not pooled.

Receiving side: orbital landing slots simplify planet-side logistics, bundling deliveries coherently. But dumping everything into one slot creates queue overload, leaving "sent but stuck" appearances when really it's receiving backlog.

Cargo Landing Pad Role Division

Ground-side reception hinges on landing pads accepting one stack per hit. This is documented in Cargo landing pad - official Wiki and becomes the real bottleneck—rarely transport, usually receiving throughput. Supplements seem delayed when pads queue items.

Critically, mixed cargo on shared pads slows fast-turnover goods. Ammunition waiting behind occasional building supplies stretches all receive times. Separate demand by supply function—construction materials, ammunition, ore lines—into distinct pad chains. Cleanliness isn't the goal; unblocking critical flows is. My centralized pad choked until I split supplies, immediately clearing bottlenecks.

Platforms flow correctly when demand statement, launch condition, planetary source, and pad assignment interconnect. Stalls hide in requirement junctures—load thresholds, minimum weight, wrong planet, queue depth. Decomposing each step makes diagnosis far simpler.

Defence and Maintenance: Asteroid Countermeasures, Ammunition, Repairs in Practice

Nauvis Orbit versus Interstate Threat Profiles

Platform defence varies steeply by location and route. Nauvis orbit leans safe—docked small platforms survive on minimal interception. Alternate orbits and interplanetary routes present serious asteroid damage. Docked fleets handle glancing blows; travelling ships suffer cascading failure from single impacts—shield rupture, severed conveyors, blown power, ammunition starvation, all cascading.

Docking designs aren't threats until you travel. Zero-gravity pusher designs collapse mid-burn under combat stress. This gap is easy to underestimate, causing early expeditions to fail spectacularly. My test run hit enemy asteroids, lost shield panels, and ammunition feed severed—game over in minutes.

Thus, don't transplant docked platforms to routes. Travelling craft need built-in defence and repair stocks from day one. Nauvis "minimums" aren't minimums elsewhere.

Gun Turrets and Ammunition Selection

Early asteroid defence favours gun turrets over energy weapons. Community consensus and reddit threads confirm: asteroids resist lasers and flame—energy just burns inefficiently. Docked-design lazers (power abundant) prove weak against rocks.

Produce yellow ammunition aboard. Sustained firepower through continuous ammunition production matters more than single-shot strength. Your guns must never run dry mid-engagement. Ship defence is supply-chain reliability, not weapon count.

I stabilised by dual-routing ammunition—each turret row backed by primary feed and emergency stock. Single feed rupture meant weapon silence; parallel lines kept suppression live. This parallels factory redundancy: routing resilience beats count.

Turret placement extends beyond bow-heavy. Secondary interception points along sides guard critical infrastructure. Aft positions defend towards thrusters. Distributing coverage makes penetration less catastrophic for downstream systems.

Repair Kits and Spare Parts

Repair kits alone don't bridge combat damage. Ground-side expectations don't apply mid-voyage. Platforms need spare equipment, foundation stock, repair kits.

Spares include turrets, conveyors, power plants—anything whose loss stalls the ship. Foundations are especially critical: floors lost = zero footprint for rebuild. Since platforms build on foundations, reconstruction stock earns its payload weight. Repair items alone can't reestablish systems without flooring.

Self-test: aboard my expedition ships sits floor materials, turret backups, conveyor bundles, power modules, wiring, and repair kits. Loss mitigation beats damage prevention—stopping-blood and holding-position beats perfect defence.

Emergency repair priorities: re-establish flooring, refire weapon systems, restore power flow, patch critical pipes. Cosmetic perfection takes a back seat. Damaged turrets stay broken if deck is missing—rebuild platform structure first. Maintenance and defence intertwine as one platform-sustenance problem, not separate.

Design Pattern Comparison by Purpose

Docked Type: Space Science Production

Simplest entry: permanent orbital science outpost. No movement, just harvest asteroids, crush, generate science packs. Propulsion unnecessary, defence light. Design difficulty drops; learning curve is shallow.

Strength: predictable failure modes. Moving platforms juggle fuel, ammo, timing; stationary ones mostly hit building shortfalls and power gaps. Debugging is clean: expand power, fix supply, repeat. ソーラーパネル baseline ~42 kW average; sustaining 1 MW needs roughly 24 panels. Accumulators 5 MJ each, 300 kW peak—straightforward maths.

Layout forgives width. Collectors, crushers, assembly, power all line horizontally. If later travelling, favour fore-to-aft growth—easier migrating modular blocks to specialist craft.

General-Purpose Transport Ship: Early 3-Planet Route

Most reproducible first-voyage platform: ammo + fuel + minimal cargo, all one ship. It's a step up from docked but short of complex—perfect for stabilising round-trip transport first, then branching roles.

Core lesson: survivability beats cargo volume. Fuel buffer, unbroken ammunition supply, repair stock matter more than cargo space. Failures cluster around ammunition depletion and fuel shortage, not space limits.

Vertical layouts become invaluable here. Front defence/collection, mid-logistics, aft propulsion segregate cleanly, aiding scale and repair. Horizontal sprawl chokes speed and complicates routing.

Resupply pairs well with this type—auto-requests light, manual supplements fill small-item gaps.

Large Resupply / Specialist Ships: Mid-Game Onwards

Stability growth: split roles into ammunition ships, fuel tankers, supply freighters. Each ship narrows purpose, improving design clarity and predictability.

Advantage: if one role fails, others persist. Ammunition shortage doesn't starve fuel delivery; supply hiccups don't extinguish guns. System-level redundancy improves.

Trade-off: build cost and design complexity rise. Architecture must segment ammo loops, fuel supply, and cargo independence. Medium-level expertise required.

Vertical role-separation layouts shine here. Bow defence/intake, waist production/transfer, stern propulsion creates visible, manageable zones. Mid-game onwards prefers architecturally distinct ships—at a glance, you know what each does.

Common Failures and Fixes

Auto-Requests Fail to Launch

When rockets stay quiet despite requests: audit ground-stock, not launch equipment. Check if inventory meets full-payload accumulation. Shortfall ranges hide easily—fuel seems abundant but ammo is 20% short. Rocket won't fly until load conditions satisfied.

Second culprit: minimum load thresholds too high. Small-item resupply requires low minimums; cranked high, nothing ships until stockpile balloons.

Third: wrong source planet designated. Multi-planet networks blur quickly. Auto-request needs explicit source assignment.

Ammunition / Fuel Shortfalls

Transportation ships stall from ammunition drought or fuel starvation. Both sneak up mid-voyage and cascade. Defence fails, escort fire ceases, damage multiplies.

Resilience comes from split supply paths—direct turret feed and reserve stocks. Ammunition generation aboard helps immensely; partial local production smooths transport gaps. Continuous supply > peak capacity.

Fuel tracking: watch residual levels, set circuit alarms before critical. Starvation mid-route is recoverable with advanced planning but catastrophic otherwise.

Speed Insufficient / Width Culprit

Sluggish platform? Check hull width before adding thrusters. Wide designs look capable but fly like barges. Tighten width, compress stern engines, watch speed improve—often without adding hardware.

Vertical revision frequently solves speed issues. Lateral span to thruster bands becomes smaller; fuel trunks shorten; effective thrust improves.

Supplies Flood In Excessively

Over-delivery stems from minimum load and max-stock misalignment. Supply arrives constantly at volumes exceeding need.

First fix: lower minimum loads for low-consumption goods—build supplies, maintenance items.

Second: add circuit conditions—suppress launches when on-hand stock exceeds threshold. Dual-control (logistics + circuit) yields precision.

No Return Trip Planned

Platforms reaching destination but unable to depart. Fuel miscalculated, repair stocks forgotten, no way home. This stings once experienced.

Countermeasure: standardise return-trip packages in fixed cargo slots. Every ship launches with return fuel, return oxidiser, repair materials, replacement foundations. Blueprints lock this habit in place.

Treat travelling platforms as round-trip-first, cargo-second.

Advancing: Planetary Optimisation and Quality/Beacon Usage

Asteroid Distribution Per Planet and Harvest Efficiency

As you mature, single generic hauler designs grow tedious. Space Age introduces 4 planets, each with distinct asteroid distributions. Some favour iron, others chemistry. Collection-to-crusher layouts can specialise by destination for efficiency boosts.

Confirm destination asteroid bias via Factoriopedia, then specialise: iron-heavy routes keep crushers lean, chemistry-heavy routes expand chemistry processing. Harvest efficiency depends less on collector count than supply-line fit.

Defence profiles vary similarly. Dense asteroid routes require stronger forward interception; scattered distribution spreads turrets. Design craft to mission rather than expect one-size-fits-all.

Quality and Space Platform Synergy

Quality (Quality modifier) gains particular worth in orbit. Space urgently lacks floor, resupply margin, defence buffer. Each 1-unit output bump yields immediate footprint reduction—a direct advantage when space is expensive.

High-quality critical components (thrusters, guns, power) compress platforms and shrink resupply burden. Build critical systems quality-first, not everything equally.

My approach: critical-components-first prioritisation. Thrusters, defences, power grid—upgrade these, then main production. Quality becomes space platform's density multiplier.

Beacon Efficiency Under 2.0 Scaling

2.0 changed beacon stacking