Factorio Space Age Complete Planet Strategy and Progression Order

Factorio 2.0 + Space Age introduces 4 new planets, and how you traverse them significantly changes factory growth. This guide is designed for players who want to strategically plan which planet to visit first, what to bring, what to produce locally, and what to export.

From my experience, Vulcanus tends to be the most stable first destination (though this is purely empirical). However, the developer doesn't specify a mandatory visit order, and the optimal sequence varies depending on your factory's bottlenecks. Keep this in mind as you plan.

During my first space platform mission, I ran short on supplies mid-orbit and had to patch things up on the next shipment before reaching stability. After that, I established minimum viable configurations for each planet and structured my progression to pre-emptively resolve common bottleneck points, rather than getting caught up in story progression.

Complete Planetary Conquest Overview and Recommended Progression Order

Target Version and DLC Scope

This guide covers Factorio 2.0 series + the "Space Age" DLC. As documented in Space Age - Factorio Wiki, the expansion adds 4 new planets—Vulcanus, Fulgora, Gleba, and Aquilo—along with a space platform system and redesigned technology tree. This represents a shift from "self-contained expansion on Nauvis" to "progressive planetary conquest where each world unlocks unique capabilities." Understanding this frame is crucial.

The official release date was October 21, 2024, and this guide aligns with that final version. When discussing progression, the key isn't "which planet is easiest," but rather which planet's specialized equipment, when brought back, compresses your entire factory network most effectively.

I view this DLC as less about "conquering individual planets" and more about sequentially unlocking planetary bonuses to remove factory constraints. For example, Vulcanus's foundry|Foundry (Furnace) provides +50% base production . Fulgora's electromagnetic plant similarly offers +50% base production, which directly improves electronic component and module density. Aquilo is the reverse—less about equipment strength and more about managing extreme cold while processing final-tier research on cramped terrain.

Space Age

wiki.factorio.com

Recommended Progression (Summary) and Decision Framework

Based on my experience, Nauvis preparation → Vulcanus → Fulgora → Gleba → Aquilo tends to avoid bottlenecks in most real-world scenarios. That said, this is situation-dependent guidance—adjust based on your specific factory constraints.

The logic is straightforward. First, on Nauvis, prepare enough resources and logistics to launch rockets and establish minimal self-sufficient outposts on the next destination. Then visiting Vulcanus first yields foundry benefits that compress iron and copper plate production by one tier. The +50% base production is strong on paper, but in practice, you'll see plate throughput visibly increase with the same ore and same building footprint. After Vulcanus stabilizes, plate supply becomes robust enough that downstream assembly lines become much easier to design and expand.

Placing Gleba afterward—not because it's weak, but because it carries higher design complexity—makes sense. Gleba revolves around unique agricultural chains. First-time players often get stuck asking "how do I prevent spoilage while keeping things flowing?" rather than "can I build it?" Having adequate material and electronic foundations before tackling agricultural logistics absorbs the trial-and-error cost much better.

Aquilo goes last because the reasoning is even clearer. Aquilo is an extreme-cold biome where heating is mandatory and buildable terrain is severely limited. As the late-game research hub, you'll want your logistics, power, and transport networks fully established before arrival. This isn't about difficulty scaling—it's about prerequisite infrastructure requirements being the highest of all planets.

Fulgora's strength isn't local resource abundance—it's density scaling via electromagnetic plant. The plant grants +50% base production, directly improving circuit/module yield. If Vulcanus is "plate-world transformation," Fulgora is circuit-factory compression. Same footprint, higher throughput.

Compressed into 3 decision criteria:

1. Does unlocking this planet's specialized equipment broadly improve production across other planets?
2. How hard is it to establish local self-sufficiency?
3. Does this planet reduce material transport load on later destinations?

From this angle, Vulcanus-first is strategically sound. While the developer doesn't mandate visit order, from a gameplay perspective: "Which planet's equipment, when brought home first, makes your next 10 hours easiest?" is the right question to ask.

Alternative Routes and Conditional Branching

However, this progression is not a locked solution. The developer intentionally doesn't mandate order. What I've outlined is the standard solution from a factory-design perspective. Realistically, optimal order shifts based on where you're bottlenecked.

The most common alternative is Fulgora-first. If you've already reached red/green/blue/purple/yellow research on Nauvis but find yourself saturated on circuit boards, control units, and modules while plate supply is still adequate, Fulgora first makes sense. The electromagnetic plant's +50% doesn't just make one machine stronger—it compresses your entire electronics line, allowing density gains even before beacon/logistics-robot heavy setups.

Gleba-first is harder to recommend for initial stability, though it's viable with clear intent. If you want to prioritize understanding agricultural chains early or build around agricultural technology, it's an option. However, Gleba exhibits "early design locks future expansion potential" behavior. If you over-prioritize processing capacity before supply, things jam easily—and later reconstruction becomes a full redesign. Players comfortable with ratio-based design risk importing vanilla ore-line thinking and breaking Gleba's balance immediately. More resources on hand makes trial-and-error more forgiving.

Aquilo-forward approaches only make sense when late-game research is the bottleneck. Even then, it's risky. This planet bundles extreme heating, severe terrain constraints, and power challenges all at once. The "add capacity locally if you run short" logic that works elsewhere breaks here. On the Aquilo-bound platform, preventing jams becomes critical—wasting items and monitoring belts are non-negotiable design requirements. It's less "difficulty scaling" and more "whether your operational design is complete."

Summarized, alternative routes break down as:

My framework: first-visit destination should be chosen not by "what's missing" but by "what closure removes the most cascading shortages?" From this angle, Vulcanus becomes the default, and Fulgora jumps to priority if electronics scarcity is already visible. Gleba and Aquilo are better framed as planets where design prerequisites must be satisfied first to unlock their true value, not as "strong therefore go early."

Pre-Departure Nauvis Preparation

Rocket Basics and Space Platform Fundamentals

Everything that follows assumes you've reached rocket launches and begun the space-exploration phase. In Space Age, the space platform becomes a waypoint hub for inter-planetary transport rather than final destination. Think of it less as "factory extension" and more as "small logistics relay in orbit."

The first thing to organize: separate materials you send to orbit from materials you produce locally. Community practice confirms that while rockets have payload limits, post-landing operations have much greater flexibility. So your first batch shouldn't be "grab everything"—it should be a function set for fastest local self-sufficiency. Early on, I was vague about this distinction, loading plates and machines haphazardly. Result: critical logistics components ran out mid-orbit while the main factory also stalled due to shortage.

Platform structure itself has principles. Per community-shared knowledge, tall/narrow layouts are superior for both interception and usability. You can concentrate fire forward, simplify ammo/repair flows, and keep bottleneck distances short. Wide platforms seem easier to place but scatter defensive and supply lines, making resupply errors common.

Mining strategy is also worth discussing here. s, large-scale mining drills exhibit a unique property: halved resource cost per unit mined. This matters not for raw throughput but for reducing resupply frequency to distant outposts. In early outpost phases where supply lines are thin, mining-side efficiency gains directly compress transport requirements.

First-Shipment Supply Template

What matters for first shipment: categorizing by function, not memorizing item names. I stabilized once I started defining reusable shipment modules—same bundle every time. Early outposts don't need a complete factory; they need power, construction capability, defense, logistics, and environment adaptation in working order.

Break inventory into 5 conceptual bundles: power setup (solar + batteries for bootstrapping), construction (assemblers + materials like plates/steel/concrete), defense (turrets + ammo + walls), logistics (belts/inserters/chests), and planet-specific adaptation. Aquilo-aware missions need heating and terraforming; otherwise, concrete is a baseline that earns its space everywhere—+40% walkspeed cuts manual setup labor significantly on long provisioning runs.

Quantities matter less as strict numbers than as range to bootstrap one outpost. Official specs aren't public; the table below is guidance, not gospel:

Easy to underestimate: steel and rail. My first run lightened these, then hit awkward distances between mining and base where short belt makeshift work devoured time. Outpost setup is really "how do I reach the first mine?" logistics, not production setup.

Under-Stocked Materials and Workarounds

Planets stall on foundational supply collapse, not exotic materials. Common shortages: steel, rail, belt, inserter, chest, ammo, wall, power pole, paving. Each type individually seems minor, but outpost setup consumes all simultaneously. Running out of one creates cascading halts.

Steel shortage throttles defense, logistics, and expansion. Rail gap prevents mining-to-base connection. Belt/inserter deficit traps visible ore behind un-buildable lines. Space Age planets especially punish "improvise locally" thinking—tempo collapses fast.

Effective workaround: modular palletized first shipments. Construction module bundles: assembler + belt + inserter + pole + chest. Defense module: turret + ammo + walls. Power module: generation + storage. Per-module assignment eliminates forgetting kit pieces; shortage categories become visible immediately for next shipment prioritization.

Vulcanus furnace effect: +50% base production per official sources. Some community materials convenience-convert this to "approximately 2.25x equivalent," but that's secondary interpretation—ground truth is official +50%, mentioned in documentation. The real value comes in bridging material flow (Nauvis→Vulcanus→other planets): furnace boost only works if material fundamentals already exist to feed it.

Mental model: thicken base-material bundles before adding high-value equipment. Space Age's unique gear looks flashy, but outpost stability hinges on foundational parts. Stock these first, and remote expeditions suffer far fewer "resources visible but factory won't assemble" dead states.

Vulcanus Conquest: Why First-Visit Candidacy Is Strong

Initial Conquest Goals

Vulcanus shines as first destination not because of new resources in isolation, but because furnace bonus directly tackles the heaviest factory bottleneck: plate/steel supply constraint. Community expert guides (e.g., J's gaming blog's assessments) confirm practical stability; post-arrival direction is unusually clear. In my multi-planet comparison, Vulcanus read as most straightforward in "what do I produce to break even?"

The centerpiece: furnace. As noted, official specification is +50% base production, and in live play, plate supply visibly surges. Community secondary sources sometimes express this as "approximately 2.25x equivalent," but that's convenience math atop official figures—lead with official (+50%), footnote the extrapolation. Tangible effect: furnace-routed plate lines filled belts fast; same footprint suddenly showed downstream congestion issues. On Nauvis, "ore flows but plates starve" is common. Vulcanus inverts this—plates distribute, not production.

The exploit is immediate: Nauvis-to-Vulcanus pivot swaps bottleneck from "not enough input plates" to "how do I allocate plate output?" This visible constraint-flip is the core return value of early Vulcanus, hence the clear appeal.

The goal isn't self-contained planetary completion. Vulcanus shines as high-density industrial hub for heavy intermediate production, with electronics/fine construction materials partially backfilled from Nauvis. Initial conquest purpose: secure metallurgical foundation early, not universal settlement.

Local Resources (Coal / Limestone / Tungsten Ore) and Furnace Line Design

Priority resources: coal, limestone, and tungsten ore—per J's gaming blog and community field experience. This trio unlocks Vulcanus's role. Coal underpins steel/fuel. Limestone (via calcite processing) enables advanced smelting. Tungsten ore prevents Vulcanus becoming "plate factory only."

Design principle: furnace-centric, compressing heavy items first. I route iron/copper plate, then steel, toward furnaces. Rationale: high consumption, high rocket footprint. Compress density on-planet so return exports carry more value. Vulcanus repays furnace investment, then exports value.

Tungsten handling: advance to mid-products (plates/rods) locally rather than shipping raw ore. Furnace-processed materials travel higher value-per-mass. Design: increase furnace islands, not mining camps. Vulcanus realizes potential as smelting hub, not mine-and-ship.

Framework:

Key: commit furnace output to 3 targets (iron plate, copper plate, steel) first, then expand. Thickness alone fixes downstream line struggles.

Export Port Design

Vulcanus leverage hinges less on mining/smelting and more on export logistics clarity. On-world abundance means nothing if shipment ports are muddled—stockpile-trapped scenario. I separate local-consumption lines from export lines early.

Export priority: iron/copper plate, steel, then tungsten mid-goods. Wide applicability, high furnace-ROI products. Import candidates: electronics and construction materials. Keeps Vulcanus port flow organized.

Avoid feature creep. Three shipment yards—plates, steel, tungsten—max. Observing belt saturation and chest inventory instantly clarifies which line throttles. Shipment yards aren't warehouses; they're production capacity visibility.

Operationally, Vulcanus ships density, Nauvis returns fine-grain items. This division sharpens main-factory electronics and final assembly. Vulcanus port becomes the system-wide resource redistribution hub, not just one planet's outflow.

Fulgora Conquest: Amplify Electronics via Electromagnetic Plant

Electromagnetic Plant Value and Target Applications

Fulgora's strength isn't local resource abundance—it's density scaling via electromagnetic plant. Per specialized wiki documentation, the plant grants +50% base production, directly improving circuit/module yield. If Vulcanus is "plate-world transformation," Fulgora is circuit-factory compression. Same footprint, higher throughput.

Highest-impact targets: green circuits, red circuits, module substrates—high-consumption, multi-tier items. Density bump at tier-1 circuits cascades to all downstream. Tangibly, moving green-circuit production under electromagnetic plant, same footprint suddenly outputs noticeably more. Numerically, +50% base production; practically, multi-stage compression feels 1.5x+.

Avoid over-generalization. Don't push plate production or broad assembly to Fulgora. Furnace for plates, electromagnetic for electronics—role clarity keeps ports manageable. Fulgora = "light, high-value electronics concentration," not "do everything."

Electronics-Led Export Design

Fulgora logistics: optimize for lightweight, high-value retrieval. Prioritize green/red circuits, module substrates, electronics mid-goods. High utility across research, modules, and late-factory assembly—solid export quality. Import-wise, bring furnace materials and construction basics—prop up electronics factory, don't dilute with heavy production.

Role division:

This arrangement splits load: Nauvis handles plate/generalist assembly, Fulgora concentrates electronics. Result: main factory rarely starves circuits; module research flows smoother.

Timing Visit Window

Fulgora synergy peaks post-Vulcanus metallurgical foundation, mid-game. If plates/steel already run stable but electronics still bottleneck, Fulgora timing clicks. Early visit while struggling for raw plate wastes Fulgora's leverage.

Gauge readiness: Does factory growth repeatedly stall because circuit/board/substrate supply fails first? That's electronics as chokepoint. Switch to Fulgora then. This stage exists commonly—research and parallel module production creates sudden electronics pressure. Electromagnetic plant directly answers this. My experience mirrors this timing.

Sequentially, early Vulcanus stability is easier; later Fulgora works given visible electronics saturation. Fulgora isn't "early wins"—it's "hits hardest when electronics-scarcity becomes obvious." Metallurgical groundwork → electronics unlock mirrors natural factory progression.

Gleba Conquest: Agriculture/Spoilage Without Line Collapse

Agricultural Chain Minimum Viable Config and Mental Framework

Gleba breaks many players because vanilla ore-extraction thinking doesn't port directly. Per Space Age - Factorio Wiki, Gleba revolves around wetland / fertile soil / agricultural tech, not pick-and-smelt patterns. The key metric: dwell time, not just throughput. Bio-chain items corrupt if flow is long or processing stranded. Early design collapse is common.

My first attempt: vanilla main-bus thinking, flow all agriculture substrate into one line. Complete disaster. Surplus accumulated, overflow created spoilage, cascade failure became rebuild hell.

Gleba minimum: separate growth space, harvest reception, immediate processing, and spoilage disposal. Skip "beautiful single trunk"—embrace "small closed loops first." Community consensus on Reddit comments confirms "understanding took time," "early design didn't scale"—not because complexity, but because chunk boundaries are hard to get right.

Structured role division:

Critical: don't try to import agriculture. Gleba's nature-farming is the point. Instead, import control/logistics infrastructure—let local farming close, feeders manage overflow.

Modularization and Scalability

Strong Gleba design: mini-farm compartment replication. Post-rework, I treated each farm-module as atomic: cultivation, harvest-receive, short processing, overflow escape all bundled. Increase capacity by copying modules, not stretching main trunk. Expansion becomes horizontal.

Ratio thinking shifts: Not "how thick is main bus?" but "does one farm-module self-govern?" If yes, scaling is almost copy-paste. Crop-module isolation means stuck modules isolate; you fix one without chain-reaction rebuilds. Factory-design-wise: distributed-module approach vs. main-bus.

Early module design: embed jam detection. Gleba doesn't break when stopped—it breaks when stopped-then-restarted-wrong. Spoilage cascades. Watch for chest-overflow, belt-sludge, lopsided production to diagnose supply-vs-demand imbalance. Observation points per module make management intuitive.

This modular approach directly counters Reddit's "early design locked me out" complaint. Single-thread design seems efficient initially but resists mid-stream recipe changes. Farm-unit design: new processing stage? Bolt on fresh unit; existing main don't break.

Jam-Prone Failure Modes and Prevention

Typical failure: over-prioritize supply before demand scales. On Gleba, harvest increase isn't win if processing can't keep pace. Inventory climbs, spoilage sets in, whole line destabilizes. Vanilla wisdom ("buffer in chests") breaks when buffers rot.

Second failure: chain assembly into one main line. Looks clean, works initially. Then any stage slows, all crops pile at same junction, spoilage cascades, breakdown diagnosis becomes nightmare. Gleba rewards line fission over fusion—split into closed compartments, each with independent monitoring.

Failure symptom recognition:

Gleba difficulty is expected. Agricultural-tech is genuinely separate from ore-tech. Understanding takes time. I myself abandoned one-line attempts, switched to farm-unit replication, and suddenly stability appeared. Gleba is less "complex" and more "demands compartment-centric thinking."

Aquilo Conquest: Extreme Cold and Cramped Terrain Management

Environmental Constraints and Heating / Power Design

First principle on Aquilo: this isn't "resource-harsh"—this is "freezing itself breaks machines". Per Aquilo/ja, entities not warmed by adjacent heat pipes freeze and halt. Surrounding terrain: ammonia ocean, fragmented by ice sheets—buildable land is scarce. Hauling "horizontal expansion on empty plains" thinking here breaks immediately. Logistics and heating collapse in tandem.

I first bottlenecked here: sufficient machine count, but lines slowed then stopped. Root: insufficient heating; production equipment froze. On Aquilo, power-check alone isn't enough. Itemize minimum-needed heat per production line, size thermal distribution first, then place machines inside thermal zones. Sequence: run heat trunk, compress machines inside its radius, not "place machines, retrofit warmth."

Power burden: Aquilo rejects solar-centric strategies. Heat + production both demand simultaneous power. Heat becomes co-generation: thermal AND electrical infrastructure unified. Warmth cuts = equipment halt = fuel/material starvation = electrical grid instability. Cascades hard. Avoid single-heat-trunk designs; split critical lineups into separate thermal loops—if one loop fails, core operations continue.

Aquilo

wiki.factorio.com

Space-Constrained Dense Layouts and Land Expansion

Aquilo's second lever: buildable terrain is minimal. Ammonia / ice / geography choke real estate. Horizontal expansion ("sprawl then retrofit") fails here. Compressed dense layout becomes baseline. Thermal distribution, processing, transport, storage—nest tightly; single block handles multiple jobs.

This is where concrete import and terraforming shine. On-world concrete production competes for space. I import it liberally here—not just for +40% walkspeed but to prep flat buildable surfaces, enabling heat-trunk routing, logistics folding, maintenance paths. Cramped terrain means terrain-setup is setup-enabler.

Heavy reliance on pre-compressed mid-goods from earlier planets. Assemblers sourced pre-built, belts pre-counted, smelting pre-loaded—stack compressed inventory before arriving. Aquilo's local factory skips low-tier generation; it focuses late-stage processes. Plate-production-from-ore locally wastes scarce heat and space. Import plates, compress into finals. Land optimization demands this split.

Logistics split:

Layout pattern: central heat source + main processing, periphery mini-stages in tight loops. One heat zone = one job. Thermal scarcity drives compartmental design naturally.

Cold-Science Pipeline Clarity

Aquilo visits target Cryogenic science pack unlock. Per Cryogenic science pack - Factorio Wiki, this planet gates late research. So factory layout should reverse-engineer from research demand, not "settle then expand."

Personal approach: core research line as spine, then "must-produce-locally" processes wrap around it. External imports serve as wrapping support. Once research trunk closes, side capacity becomes supplement. Aquilo stability hinges on whether the research pipeline has short, defended routing, not overall base magnificence.

Research constraint is real in late phases—visible symptom is "tons of machines but research line output is anemic." Aquilo amplifies this: cramped land makes sprawling networks infeasible. Solve by prioritizing research-output density over general production.

Realize: research unlocks unlock further research. Aquilo's endgame value is next-tier tech, not current-tech repetition. Shape layout around that unlock, then fit supporting periphery. This priority-inversion (late before surrounding) seems backwards but matches constraint reality.

Cryogenic science pack - Factorio Wiki

wiki.factorio.com

Space Platform and Interplanetary Logistics Essentials

Minimal PF Template and Validation Protocol

Platform design: skip elaborate endgame ships, prototype single-unit viability first. One unit: thruster+supply, power, defense, repair, logistics bundled. Replicable module: thrust/fuel, solar/battery, turret-line, self-heal method, logistics I/O coupled.

Templating works because PF failures stem from subsystem gaps, not single-component shortage. Thruster alone means nothing without ammo supply; defense alone fails if power is thin. Bundle minimally-sufficient functions into standardized unit; expansion adds unit copies, not novel designs. Operational consistency beats flexibility optimization on early platforms.

Validation steps once template launches:

1. Short shakedown flight (test full cycle)
2. Resupply log inspection (where do surpluses pool?)
3. Jetsam handling check (does overflow escape cleanly?)

Key observation: ammo stall-zones, one-way belt saturation, unjammable request queue. Space Age logistics fail from design oversights harder than insufficient components. Embed monitoring from start; post-launch "let's see" thinking breaks.

Early template, tested patterns, modular expansion beat from-scratch rethink per mission. Consistency reduces re-engagement ramp.

Vertical Ship Bodies and Defense Line Clarity

Vertical (tall/narrow) hulls outperform horizontal (wide). Spaceborne threats approach forward-facing; tall geometry concentrates countermeasures. Narrow front = coordinated fire; wide front = scattered coverage. Ammo distribution tightens on vertical. Efficiency jump is noticeable.

Layout: front defense line, central ammo/repair, rear thrust/power. Narrow bow = fire concentration; rear-skewed mass = less-defended rear.

Vertical benefit extends to logistics. Cramped cross-section forces front-to-back material flow, simpler path-finding. Rework/refit diagnosis is quicker. Horizontal sprawl spreads subsystems, belt routing scattered, failure diagnosis fuzzy. Transport-focused design prefers vertical.

Ammo-Less Theory and Bullet Supply Strategy

Mental shift: machines don't "need armor," they need to avoid hits. No-hit-assumed design drops armor overhead, freeing payload for cargo. Defense priorities forward, processing midship, rear thrusters. Once front line is robust, rear-focused threats rarely matter.

Ammo sourcing: don't ship full stock each cycle. Feed sources: on-site generation (if PF resident capacity allows), or mothership production. Rotary cycle: consume ammo, resupply on return, repeat. Bullets as flow-system, not stockpile.

This matters because Nauvis supply is thin. Ammo per-trip limits throughput without bloating payload. Local PF generation or groundside production frees capacity. Early Vulcanus routes: groundside ammo factory → Nauvis stock → PF ferry per trip. Ammo behaves like any other conveyed item, not magic.

Ammo-design reframe: consumption rate should be even/predictable, not volatile. Erratic ammo draw breaks supply cadence, misaligns resupply timing. Efficient platforms exhibit smooth defense drain, enabling predictable logistics rhythm.

Common Pitfalls and Mitigations

Checklist: Initial Shipment Template

Novices bottleneck most when "resources exist but can't assemble them." Power/building/logistics pieces often vanish selectively, cascading stops.

Mitigation: template

References and External Links (Useful Resources to Read Next)

• Space Age - Factorio Wiki: https://wiki.factorio.com/Space_Age/ja

Official overview of the DLC and its planets.

• Foundry - Factorio Wiki: https://wiki.factorio.com/Foundry/ja

Official specs for the Foundry (base productivity +50%) and recipe details.

• Cryogenic science pack - Factorio Wiki: https://wiki.factorio.com/Cryogenic_science_pack/ja

Official info on cryogenic science packs on Aquilo.

• Aquilo - Factorio Wiki: https://wiki.factorio.com/Aquilo/ja

Aquilo-specific environmental constraints and heating rules.

Summary

The progression order of Vulcanus, Fulgora, Gleba, then Aquilo is the most practical baseline because it builds naturally on each planet's strengths. But in practice, working backward from whatever bottleneck your factory actually hits is the strongest approach. The design principle isn't about making each planet self-contained; it's about role specialization and interplanetary logistics -- processing heavy resources on-site and finishing lightweight, high-value components on whichever planet does it best.

When I think about Space Age, I find it helpful to separate DLC-specific elements like Foundries, electromagnetic plants, cold protection, and space platforms from the base factory you run with Transport belts and Assembling machines. The idea is "use new mechanics to remove constraints, then stabilize with proven mass-production techniques." For detailed specs, keep the Space Age - Factorio Wiki page open as a reference. Start by designing your entire star system as one factory rather than thinking planet-by-planet, and you'll avoid most common pitfalls.