【Factorio】Gleba Strategy | Factory Design That Never Stops, Built on Spoilage

On Gleba in Space Age, the Nauvis instinct to "just store everything" collapses instantly. Biological items start spoiling the moment they're created, degrading in chests, inside machines, and even in inserter hands. Early game success comes not from designs that hold inventory, but from designs that keep everything flowing continuously.

This guide walks through 5 steps to launch confidently right after arriving on Gleba (£0–0 approx cost in setup efficiency), then systematically explains how to connect spoilage timers, freshness inheritance, trash slots, small buffers, and recovery lanes. I myself wiped out completely on my first attempt by hoarding in chests, but the moment I cut buffers and tightened transport distance, the line became unbelievably stable.

After reading, you'll be able to treat spoilage not as a disaster but as a design premise, and replicate a non-stop Gleba production line independently.

Gleba Strategy Basics for Factorio | Space Age-Exclusive Spoilage Fundamentals

Target Version and Prerequisites

This section assumes the spoilage system unique to Gleba, introduced in the Space Age expansion (released October 2024). The Nauvis-centred mindset of "materials can just be stored" doesn't apply here. For official specification changes related to Space Age, check the Version history page and the official Factorio Wiki|https://wiki.factorio.com.

Let me align terminology first: freshness is "the percentage of remaining time until spoilage," trash slots are "temporary holding areas inside machines for spoiled items," and nutrients are "the basic fuel for Gleba-specific equipment, especially the Biochamber." The logic is highly consistent once understood. Items start decaying the moment creation occurs, the process continues through intermediate stages without stopping, and degradation directly affects quality and efficiency of downstream processes. Gleba stabilises the instant you switch to designs that accept this rule.

Regarding time-sensitive Gleba progression elements: the community view suggests "progression begins once the space platform first reaches the Gleba orbit." However, this point lacks clear official backing within the scope here, so it's safer to treat it as an operational concern rather than a definite specification.

Locations Where Spoilage Occurs and Why It Can't Be Stopped

The first critical concept for Gleba: spoilage timers don't stop regardless of storage method. There are virtually no exceptions. Spoilage begins at creation and continues inside containers, in machine input slots, output slots, and even in inserter hands.

I truly understood this mechanic when I watched items spoil while being transported by an inserter. That single moment made clear that "building more storage" is counterproductive on Gleba. Long belts, large chests, and idle time between processes all erode freshness.

As a concrete example, Spoilage mechanics - Factorio Wiki states that raw fish has a spoilage time of 2 hours 5 minutes 50 seconds, or 453,000 ticks. This sounds long, but many frequently-used Gleba materials decay in minutes. The question isn't "will it spoil," but "at which process should spoilage be factored in as inevitable." This is why Gleba values short-distance transport and immediate processing over large buffers.

Spoilage mechanics

wiki.factorio.com

Freshness and Freshness Inheritance Basics

The critical insight: completed items don't always start as fresh goods. In most Gleba recipes, input freshness is inherited by the output. Feed in heavily degraded materials, and the finished product emerges with a short remaining lifespan from the start. This is where design philosophy diverges from standard production lines.

Freshness is no mere display—it directly impacts research value and downstream function. Agricultural Science Packs, for example, have their research value affected by freshness. "We made it, so it's good" doesn't suffice. When you calculate the margins—10 seconds in early processing, 10 in transport, 20 waiting—the completed item's useful lifetime is consumed entirely. Thin-looking lines on Gleba run stably because they carry less inventory, preserving freshness.

One exceptionally useful exception in freshness inheritance: nutrients made from spoiled items start at 50% freshness. Not pristine, but quite manageable as emergency restart fuel. Though less efficient than processing fresh fruit directly into fuel, it's powerful for restoring minimum operation to a collapsed line. I view this "50%-fresh restart fuel" as insurance during unstable early operations.

Quality-based improvements to spoilage duration exist, but for initial strategy, layouts that don't lose freshness are the priority. Direct connections, short belts, small buffers—these three win out in both feel and numbers.

Trash Slot Mechanics and Jam Conditions

Machines with spoilage-prone inputs or outputs gain a trash slot separate from normal I/O. Its role is simple: hold spoiled items inside the machine and prevent the main line from instant failure. This feature is why Gleba doesn't collapse immediately when spoilage occurs.

However, this system has a clear weakness: if machine output is full, the trash slot cannot function. This is the core jam mechanism. When "product extraction is slow," "byproduct export stops," or "recovery belt saturates," spoiled items can't escape. They remain lodged in input, fuel, or output, freezing the machine.

The breakthrough moment for me came when I watched an assembly machine freeze because it couldn't expel trash, causing upstream inserters to jam in a chain reaction. Since then, I've treated the finished goods transport line and spoilage recovery line as equally important design features. On Gleba, "how to make output" matters as much as "where spoilage escapes after."

Spores and Pentapod Threats

Gleba's difficulty extends beyond spoilage. The second pillar is spores and pentapods. As explained in Gleba - Factorio Wiki/ja, pentapods are attracted to spores—functionally similar to pollution pressure on Nauvis. Production raises local pressure, and neglect increases defense burden.

This interacts dangerously with spoilage: slow processing creates wasted inventory and stoppages, forcing larger facilities to restart, ultimately worsening spore conditions. Gleba subtly links defense and production. A short, fast, jam-free line supports both freshness maintenance and defensive efficiency.

The same applies around agricultural towers: fruit sitting inside loses freshness. Tower placement is colour-coded in UI by 3×3 sectors, but correct placement means nothing if extraction is slow. In Gleba strategy, treating畜畜 fields, processing, nutrients, spoilage recovery, and defense as a single non-clogging flow outperforms separate optimisation.

Gleba/ja

wiki.factorio.com

Five Steps to Launch Right After Gleba Arrival

Step 1: Secure Stone and Prepare Landfill in Parallel

The first post-arrival task: run stone collection and landfill preparation simultaneously. I initially thought "let me find a spot for agricultural equipment," but terrain constraints made clean placement impossible. Later, landfill creation stalled everything. Early Gleba depends heavily on securing layout freedom within the first few minutes.

The aim is straightforward: create terrain where you can place agricultural towers, biochambers, and primary processing nearby. Since long-distance transport itself costs freshness (as noted earlier), the order matters: "build terrain to co-locate equipment" before "place equipment where it fits." Stone serves double duty—raw material and landfill input—and landfill preparation lets you cluster processing around towers. This "cluster density" directly shapes later stability.

Step 2: Place Agricultural Towers in Good Soil Areas with Minimum Distance

Once landfill is stable, deploy the first agricultural tower quickly. Hesitation wastes time; getting one working creates fruit flow faster than careful site-hunting. Good soil zones are colour-coded and displayed as 3×3 sectors in the UI (see Agricultural tower - Factorio Wiki).

The priority is actual usable soil clusters, not aesthetically large clearings. A compact tower placement enabling adjacent processing beats sprawling flatland with distant facilities. I originally placed towers in visually expansive areas, but distant processing murdered freshness during fruit transport. Once I switched to "one-step-away primary processing," harvest spoilage dropped dramatically.

At this stage, a single-tower, minimal-scale setup suffices. Target: one tower in good soil, with processing placed a few tiles away. Gleba early-game gains more from harvest-to-processing speed than from plantation scale.

Step 3: Secure Spoiled Items or Plant-Derived Initial Spoilage

Once the tower runs, next secure spoilage for nutrient seed stock. This mental shift is huge: Gleba treats spoilage not as failure residue but as startup capital.

Acquisition splits two ways. First: use existing spoiled items directly. Second: intentionally extract initial spoilage from harvested plants or fruit-derived materials. Since bioitems spoil regardless of storage location, early design should build "a post-spoilage use path" rather than obsess over prevention alone.

At this stage, volume matters less than continuous operation. "Spoil it intentionally and flow it forward" beats "hoard it perfectly." Small chests feeding small-scale spoilage processing outperform large-volume buffering.

Step 4: Activate Fuel Line at Spoilage→Nutrients Ratio

Once spoilage is secured, immediately connect it to nutrient conversion. Community measurement suggests a rough "spoilage-to-nutrient ratio around 10:1" (though primary citations are unclear, so treat as operational guidance). The real goal: build sufficient nutrient supply to run one Biochamber continuously.

Raw numbers matter here: a single Biochamber consumes ~15 nutrients/minute. Math: 500 kW draw, 2 MJ per nutrient, so 1 nutrient lasts 4 seconds, yielding 15/minute. Early objective is not mass production but sustaining a single device continuously. Spoilage-derived nutrients are less efficient than fresh-material startup, yet they're excellent restart fuel. Harvesting spoilage locally with zero transport overhead makes spoilage-based starters tactically superior to long-distance fresh supply for initial ignition.

Keep this nutrient line small. Nutrients spoil too, so early design should be make-locally, burn-locally. Gleba's stable lines basically run on "instant production, instant consumption."

Step 5: Build Minimal Umako / Jellynut Processing Line Directly Adjacent to Tower

Once nutrients flow, build a minimal fruit processing line near the tower, connected directly. Umako and community-called "Jellynut" both benefit from local mid-stage processing over long-distance raw transport. Freshness preservation trumps setup aesthetics at this stage.

This minimum line needs no large output buffer—only that agricultural tower, primary processor, nutrient-using equipment, and spoilage escape route fit within a few tiles and close into a loop. Successful early Gleba reaches this point: a small, complete circuit before attempting factory expansion. Once this works, scaling becomes "add more of the same," not "redesign fundamentals."

Spoilage Resource Management | Three Design Principles to Keep Lines Running

Principle 1: Small Inventory, High Throughput

The deadliest Gleba mistake is storing everything "just in case" like Nauvis. Spoilage inventory behaves badly: if holding n items with spoilage time t, average spoilage generation is n / t. Larger stock = larger spoilage streams, automatically.

The official Spoilage mechanics - Factorio Wiki steel chest example is illuminating. One steel chest holds 48 stacks × 50 units of standard-quality copper bacteria. If it all spoils in 1 minute, that's an average 2400 items/minute spoilage stream appearing downstream. One chest becomes a massive byproduct line. The message: large spoilage buffers are not convenience—they're sudden production reroutes.

I initially thought buffers meant stability. Reality: buffers hide problems until they burst. Removing chests and switching to direct connection killed spoilage jams completely. Gleba favours small, continuous-flow lines over warehoused ones.

Principle 2: Short Transport and "On-Site Primary Processing"

On spoilage items, distance itself is a cost. Freshness inheritance means goods transported long distances emerge from processing already degraded, not refreshed. Processing after transport doesn't restore freshness—it inherits the loss.

Core design: process on-site immediately, move to next step. Agricultural tower → nearby primary processor → secondary processor → end consumer. Collocation, tight belts, or direct connection wins. Chests and logistics are flexible but lose freshness. Especially: transporting whole fruit over long distances costs more than it appears—the value melts en route.

Thinking freshness-first, process placement becomes "where can freshness drop?" High-freshness items stay close; items tolerating degradation move freely. Agricultural Science Packs need freshness preservation throughout; startup or backup fuel lines tolerate lower freshness. This split clarifies where tight placement is mandatory.

This calculation shifts layouts immediately: keep fresh items close, transport only items where freshness loss has been factored in. Gleba layouts based on this principle run smoothly.

Principle 3: Keep Outputs Empty at All Times

Gleba stoppages stem from output jams far more than input shortage. Biochambers move spoiled stacks to trash slots, but if output is full, trash slots jam. Output fullness blocks trash function entirely, leaving spoilage and degraded items lodged in place, frozen.

Treat machines as fluid processors requiring continuous output extraction, not as input containers. Output-first design keeps lines running; input-first design breaks them. Spoilage recipes especially demand designing byproduct lines as carefully as main product lines.

I turned the corner when I stopped obsessing over supply ratios and started prioritising output clearance. Trash recovery designed into primary output solved most stoppages. Gleba priorities: production ability ranks lower than jam prevention.

Trash Slot and Recovery Lane Design

Trash slots are spoilage circuit breakers. Spoiled stacks shift here; inserters pull from here. Full slots freeze the line, so think of trash slots plus recovery lane as a single system.

In practice, set aside a dedicated recovery lane separate from finished-goods conveyors. Filter inserters pull trash from each Biochamber trash slot into this lane, which aggregates output. This way, one machine's spoilage doesn't clog the main belt. Mixing trash and finished goods is possible but adds selection complexity and makes root-cause analysis harder.

Where recovered spoilage goes matters hugely. Feeding it back into reuse loops restarts collapsed lines. But if reuse capacity saturates, recovery lanes jam. Practical solution: priority to reuse, excess diverted elsewhere. This two-tier approach prevents reverse-flow jamming downstream.

Think of spoilage as normal, continuous byproduct traffic not "exception handling." Stable Gleba lines have anomaly recovery lanes in the original blueprint.

Using Freshness Inheritance as an Asset

Freshness inheritance looks like constraint, but clever process ordering makes it powerful. Decide early: which stages must preserve freshness, which can absorb loss? High-value-when-fresh items stay nearby; freshness-tolerant materials move freely.

Example: research value depends on agricultural science freshness, so items should travel minimally before assembly. Conversely, restart fuel or backup loops accept degradation. This split clarifies where adjacency is mandatory.

I prioritise: keep high-freshness items local, transport only items where freshness drop is acceptable. This automatically determines machine spacing, chest placement, and buffer sizing. Without it, every distance feels "probably OK"; with it, placement decisions crystallise.

Gleba plants resemble fresh-food factories more than mass-production plants. So optimise for residence time, not storage volume, and total latency, not output quantity. Lines organised this way feel and run smooth.

Recommended Layout Comparison | Direct Connection vs. Short Belt vs. Logistics Chest

Direct Connection Layout: Minimum Distance, Minimum Freshness Loss

Direct-connection layouts—co-locating harvest, processing, and consumption—run most stably on Gleba, especially early-to-mid-scale. Freshness erodes primarily during "transport time" and "idle time anywhere"; tightening distance improves yield immediately.

The math is stark. Spoilage items live minutes to 2 hours. Short-lived items have zero slack for chests or long belts. And since freshness inherits to finished goods, time lost upfront can't be recovered later. Lines where freshness directly feeds research value (agricultural science) see dramatic gains from adjacency.

Direct connection also simplifies trash handling. Spoilage emerging from any machine processes quickly. My stoppage rate plummeted when I co-located everything. Gleba runs on small, fast operations better than large, high-throughput ones.

The downside: expansion becomes awkward. Modular block-building breaks down, and retrofits get congested. Yet early-game pain comes from stoppages, not lack of room. Build stop-free first; expand later.

Short-Distance Belt Primary Layout: Visibility and Adjustability

If direct feels too cramped, short-belt-primary—placing stages a few tiles apart and connecting with conveyors—balances well. Freshness takes a hit versus direct connection but remains strong. Visibility and maintainability improve.

This works especially well with parallel main-product and spoilage-recovery lanes. One sees status easily, jams are traceable, and the "keep outputs empty" principle becomes obvious. Direct connection can feel packed; short belts preserve readability.

The cost: distance increases spoilage loss. A brief stoppage spoils in-flight inventory; restart may reveal a wave of spoilage items. Still, this stays better controlled than chests hoarding large buffers. I'd run direct early, shift to short belts when production scales and readability matters.

Chest / Logistics Primary Layout: Management Hell, Spoilage Breeding Ground

Chest/logistics setups offer flexibility and expansion but are accident-prone on Gleba. Chests don't "store" spoilage goods—they become degradation wait zones.

Math again: steel chests hold 48 slots. Official examples: fill one with standard copper bacteria (48 stacks × 50 units) spoiling in 1 minute = 2400 spoilage units/minute downstream. One chest becomes a spoilage factory. If goods need freshness, the same volume erases value at the same rate. Massive inventory = massive spoilage loss.

Logistics robots face similar issues: items lose freshness while in transit and charging. I once overloaded robots; fresher-goods transport slowed as decay mid-flight, hitting bottlenecks downstream anyway. Reverting to direct connection restored stability and UPS. Gleba doesn't reward "flexible movement"—it rewards "short, reliable flow."

Chests and logistics work for seeds, non-perishables, emergency reserves. But routing spoilage items through them multiplies complexity: inventory watching, amount capping, jammed recovery logic, restart procedures. Unnecessary at early-to-mid scale.

Why Long-Distance Spoilage Transport Loses

Hauling spoilage or spoilage-prone goods far is inefficient because of freshness inheritance, distance loss, and total-loss risk combined.

First, inheritance: upstream freshness decay → downstream output degradation. A processed item inherits the freshness its ingredients lost. Long transport before processing sets the finished-good ceiling low before work even starts. High efficiency requires "process nearby," not "process far."

Second, transport cost: spoilage times span minutes to 2 hours. Short-lived items make transport itself the majority cost. Work isn't happening—only freshness is draining. Fresh items, spoilage-derived nutrients, and long-transported items rank in efficiency, and hauling erases the gap.

Third, stoppage risk: a jammed long line becomes a giant, time-sensitive buffer. Anywhere from belt to chest to robot stalls it; in-flight inventory instantly decays. Restarting doesn't restore spoiled stock to working condition. Long-distance systems amplify spoilage-burst risk.

The design logic: process in-place and degrade safely before moving, not after. If transported at all, treat it as already degraded.

Spoilage Handling: Immediate Nutrient Conversion / Emergency Reserve / Disposal Comparison

Spoilage strategies split into immediate nutrient conversion, emergency reserve, and discard/burnoff, each with tradeoffs.

Immediate conversion is most practical. Recovered spoilage feeds directly into nutrient loops, speeding restart. One Biochamber eats ~15 nutrients/minute, so even small spoilage→nutrient conversion helps. Inventory load is moderate; operational complexity is manageable.

Emergency reserve acts as restart insurance but hoards inventory, clogging workspace and main logistics. Use sparingly—treat reserves as "small safety stock," not "large spare parts bin."

Discard/overflow is least complex and space-efficient, but sacrifices restart speed. This works best as secondary outlet when reuse capacity saturates, preserving main lanes.

Pick per priority: favour immediate conversion for stability, small reserves for restart resilience, discard for jam prevention. Gleba stabilises when "reuse what's reusable, discard what isn't," not "save everything."

Common Failures and Solutions | Seed Depletion, Nutrient Starvation, Spoilage Jams

Fruit Spoils → Seed Cycle Collapses

The deadliest Gleba failure: fruit is harvested but processing is slow, and seed return thins, starving the fields.

Fruit isn't complete until processed into seed and fuel, restarting the cycle. Spoilage partway through breaks it lethally: visually, stock exists; functionally, seeds and fuel dry up. Plants run empty.

Classic mistake: big-chest fruit staging, then batch processing far away. Short-lived items decay before reaching processors. Result: seeds only return as spoilage; the cycle starves.

I once hoarded in pre-lab chests for "safety." Instant death: fruits degraded en route, spoilage avalanched downstream, lab stalled, everything choked. Large inventory = large spoilage waves. Seed cycles survive if fruit processes near harvest with seeds returning immediately.

Fix: process harvested fruit onsite, return seeds to planting immediately. Place small processing near towers; keep seeds on the short loop. Treat fruit as seed-maintenance fluid, not storage commodity.

Machine Output Full → Trash Non-Functional → Permanent Jam

Classic Gleba stoppage: output fills; trash slots malfunction; machines freeze.

Biochamber spoilage goes to trash. Output fullness blocks trash evacuation. Input, fuel, or output stalls with jammed spoilage, freezing the line. Machine-feed inserters alone won't fix a no-exit jam.

Solution: ensure constant-operation spoilage evacuation. Place a recovery belt for trash removal even during normal operation, either feeding reuse loops or overflow disposal. One lane opening prevents full-output paralysis.

Single-machine stoppage affecting large lines shows Gleba's sensitivity. Ten Biochambers = 150 nutrients/minute. Brief jamming breaks fuel balance quickly. Treat trash extraction as primary infrastructure, not emergency patch.

Hand-Crafting Large Queues → Finished Items Spoil Instantly

Overlooked failure: large hand-craft queues = spoilage time stacks. While crafting first items, later items' freshness clocks keep running. Finished goods emerge already worthless.

This is operational mistake, not machine failure. Heavy queueing feels efficient but deadens item value on Gleba. Finished items often reach inventory near zero freshness, equivalent to direct spoilage crafting.

Fix: craft in small batches. Make only what's next-needed, send it forward, repeat. Small batch-loops prevent spoilage-stacking. Even pre-automation, throttled hand-crafting beats burst crafting on Gleba.

Long-Distance Transport Degrades to Zero → Total Loss in One Move

Design trap: stage-and-haul spoilage systems. Chests collect; long belts or logistics distribute; remote processing batches. Nauvis standard, Gleba suicide.

Dual lag: idle in chests erodes freshness; haul time erodes more. Stalls anywhere mid-transit trigger full-buffer degradation. Restarting yields no usable goods—loss is total. Long-distance staging doubles decay.

Gleba demands: process onsite only. Haul only non-perishable output. Transport degraded items, not fresh ones. Or don't haul spoilage at all.

Blackout / Nutrient Depletion Restart Struggle

Gleba hits hard on restart: equipment needs nutrients; nutrient production needs nutrients. Self-referential jam.

Insurance: keep minimal emergency spoilage stock separate from main recovery. Spoilage-to-nutrient conversion at 50% freshness fires up collapsed lines. Tiny spoilage reserves avoid inventory bloat while enabling first-restart spark.

Restart sequence matters: fire up fuel supply first → seed loops second → main production last. Like commissioning plants: auxiliaries before primary. Gleba success requires **staged recovery, not all-at-once.*

Spoilage Isn't Disposal Only | Reuse, Fuel-Making, Emergency Stock

Spoilage→Nutrients (Ratio) and 50% Freshness Start

Spoilage is operational asset, not mere failure. Gleba practically converts spoilage into nutrients and fuel. Community measurements suggest a rough "spoilage-to-nutrient ratio around 10:1" and "nutrient freshness ~50% post-conversion" (referencing details unclear, so treat operationally). Key point: restart fuel arrives at pragmatic freshness.

Math: Biochamber = 15 nutrients/minute. Restart needs not huge storage but continuous few-dozen supply. Spoilage→nutrient routes create ignition fuel self-sufficiently. Versus long-distance fresh supply, spoilage-origin startup is tactically better.

Nutrient Recycling Observations (Note)

Some community reports cite "spoilage recycling yields multiple nutrients per cycle" (e.g., ~2.5 nutrients per conversion). These reflect community measurement, not definitive Wiki documentation. Here, "recycling is useful" is emphasised; exact numbers fluctuate by environment and method. Treat recycling as secondary net behind main fruit supply, collecting overflow only, and line organisation simplifies.

Direct Plant Spoilage Harvest and Startup Boost

Spoilage isn't just byproduct. Plants directly yield harvestable spoilage, enabling boot-strapping when processing infrastructure lags. Collapsed line? Plant-direct spoilage harvest supplies emergency restart without waiting for main processing.

This direct route fires the "first 1 machine" problem. Gleba's self-referential nutrient need breaks when spoilage is directly harvestable. I rely on it heavily for early restarts: quick spoilage grab → small nutrient batch → feed machines → main loop reconnection. Psychologically and mechanically, this feels like a restart spark plug outside the normal loop.

Plant-direct spoilage isn't primary fuel supply but minimum-viable ignition. Gleba reward jumps once nutrients exist; reaching that threshold defeats the hardest step.

Emergency Reserve and Overflow Disposal Design

Spoilage keeps value, but hoarding is counterproductive. Small emergency stock only; normal operation carries calculated amounts. Oversized stock squeezes inventory, balloons processing targets, clouds line visibility.

I split spoilage roles: tiny restart reserve, normal-run recovery, and overflow disposal. Decisive on overflow is key. Spoilage lacking reuse destination should burn or discard, not accumulate. With clear stock caps and surplus-handling rules, operations steady.

Comparing: spoilage-to-immediate-nutrient favours restart capability, backup hoarding aids resilience but bloats inventory, discard/overflow streamlines operation.

Simple Flow: Fruit → Primary Processing → Nutrients → Biochamber

Cleanest model: fruit doesn't sit; intermediate spoilage feeds forward.

1. Harvest fruit
2. Process nearby
3. Make nutrients, feed Biochambers
4. Recover spoilage in-transit
5. Convert spoilage back to nutrients for startup/reserve fuel
6. Discard excess spoilage

This converts spoilage from failure residue into operational loop. Fruit → Primary → Nutrients → Fuel cycle closes; spoilage becomes recovery resource. Gleba stabilises once "spoilage is reusable byproduct" replaces "spoilage is loss."

Advanced | Agricultural Science Packs and Off-World Operations

Agricultural Science Freshness and Research Efficiency

Agricultural Science Packs aren't forgiving like other sciences. Freshness directly influences research value. Same-count packs differ if aged versus fresh. Gleba SPM plateaus often from freshness loss, not count shortage. Early-game SPM stability depends on distance, not quantity.

Fix: minimise distance first. Co-locate production and lab, use short belts, cut chest idle. These three alone improve research spread. Direct connection wins, short belts suffice, chests/logistics falter. Freshness inheritance means "neat layouts for later" sacrifices research now. Worth planning adjacency early.

I tested: lab nearly adjacent cut output jitter drastically. Supply numbers stayed same; research curve steadied. Agricultural Science design = freshness architecture.

Freshness inheritance chains through materials, so mid-stage lag compounds. Pre-finished-good processing cuts losses, but only if full upstream chain is tight. Whole flow from raw to research must compress distance.

Version history/2.0.0

wiki.factorio.com

Biochamber Off-World Deployment and Challenges

Biochambers seem Gleba-exclusive but add value elsewhere. Specialised recipes are appealing, and 50% production bonus applies universally. Challenge: nutrients fuel them, and nutrient supply off-world is awkward.

One Biochamber = ~15 nutrients/minute. Ten machines = 150/minute. Off-world, nutrient supply becomes constraining. Nutrients spoil, transport distance harms freshness, and in-machine spoilage clogs trash slots. "Just send fuel" doesn't work.

Design splits two ways: on-site nutrient creation and local consumption, or short-distance-only, capped operation. Long-distance fails due to combined freshness+inventory+trash costs. Research or high-fidelity jobs demand input quality chests can't sustain.

Takeaway: Biochambers are capable but supply-constrained off-world. Decide upfront: "how many continuous machines?" → calculate nutrient need → choose local production or limited