【Factorio】Gleba Strategy Guide｜Factory Design with Spoilage as Prerequisite

Gleba in Space Age collapses quickly if you apply the "just store everything" approach from Nauvis. Biological items begin their spoilage timer the moment they're created and deteriorate in chests, inside machines, and even on inserter hands. For early game, the correct approach is not a design that holds inventory, but one that keeps material flowing continuously.

This article organizes five straightforward steps to establish yourself immediately after arriving at Gleba, then explains in order how to connect spoilage timers, freshness inheritance, trash slots, small buffers, and recovery lanes. I also completely wiped myself out on my first playthrough by hoarding in chests, but the moment I trimmed buffers and tightened transport distances, the line became remarkably stable.

After reading, you should be able to treat spoilage as a prerequisite condition rather than an accident, and reproduce a non-stop Gleba production line on your own.

Gleba Strategy Fundamentals｜Space Age-Specific and Understanding Spoilage Mechanics First

Target Version and Prerequisites

This section covers the spoilage system unique to Gleba, introduced in the Space Age expansion (released October 2024). Players used to focusing on Nauvis tend to think "materials can just be stored," but that premise doesn't apply on Gleba. For official specification changes related to Space Age, check the Version history page and the official Wiki.

Let me standardize terminology first: freshness is "remaining time as a percentage until spoilage," trash slot is "a temporary evacuation location for spoiled items inside a machine," and nutrients is "the basic fuel for Gleba-specific equipment, especially biochambers." The concepts look complex in text form, but the underlying logic is quite consistent. Time passes from the moment of creation, doesn't stop mid-process, and deteriorated items directly affect the quality and efficiency of subsequent stages. Gleba becomes stable the moment you accept this rule and switch to design accordingly.

Regarding timeline-related Gleba progression elements, the community tends to view it as "beginning when the space platform first reaches Gleba orbit." However, this point lacks clear official Wiki corroboration for this section's scope, so it's safer to treat it as an operational caution rather than a definitive specification.

Where Spoilage Advances and Why It Cannot Be Stopped

The first thing to internalize about Gleba is that spoilage timers cannot be stopped by storage method. There are virtually no exceptions where spoilage is safe—not "inside this machine," not "on an inserter's hand." Countdown begins at creation and proceeds in containers, machine input slots, output slots, and on inserter hands alike.

I truly understood this mechanic when I saw an item spoil while an inserter was carrying it. Seeing that teaches you immediately that "adding more storage won't help"—quite the opposite. Long belts, large chests, and material resting time all work against freshness.

As a concrete example, the Factorio Wiki entry on 'Spoilage mechanics' lists raw fish spoilage as 2 hours 5 minutes 50 seconds, or 453,000 ticks. This sounds long, but among materials you'll frequently touch on Gleba, many have shorter times, and some collapse in minutes. The real question isn't "does it spoil?" but "at which process do I plan for it to spoil?" This is why short-distance transport and immediate processing have more value than large buffers on Gleba.

Spoilage mechanics

wiki.factorio.com

Freshness and Freshness Inheritance Basics

What's important to understand about freshness is that finished products aren't always treated as brand new. In most Gleba recipes, material freshness carries forward to the next stage. In other words, if you feed in materials degraded to their limits, the finished product emerges with a short lifespan from the start. This is where production line design thinking shifts from normal planets.

Freshness isn't just a display—it ties directly to research and subsequent process value. Take agricultural science packs: freshness affects research value, so "we made it, okay" doesn't suffice. The math is clear: if you lose 10 seconds in early processing, 10 in transport, and 20 in waiting, the finished product's effective lifespan is consumed entirely. Gleba lines appear thin but run stable because they avoid inventory hoarding, preserving freshness instead.

An exceptionally useful quirk of freshness inheritance: nutrients made from spoiled items start at 50% freshness. It's not brand new, but it's quite usable as emergency restart fuel for collapsed lines. It may underperform compared to directly converting fresh fruit or processed goods into fuel, but it's strong for restoring minimal operations. Early on while my line was unstable, this "50% starting restart fuel" was insurance.

Quality systems that extend spoilage duration exist, but for initial Gleba conquest, what matters most is layout that preserves freshness. Direct connection, short belts, small buffers—prioritize these three, and the improvements are massive in both feel and numbers.

Trash Slot Mechanics and Clogging Conditions

Machines with spoilage-capable input/output get an added trash slot separate from normal in/output. Its job is simple: evacuate items that spoil inside the machine and prevent the main line from instant death. Thanks to this, even with some spoilage, Gleba rarely stops instantly.

However, this mechanism has a clear weakness: if machine output is full, the trash slot cannot function. This is the core of jamming. In other words, "finished products aren't being pulled out," "byproducts aren't shipping," or "recovery belt is saturated"—any of these can prevent spoiled items from evacuating, leaving them stuck inside and causing shutdown.

My turning point came exactly here: an assembler with full output couldn't "excrete garbage," causing chain shutdown up to the feeding inserter. Now I never treat spoilage recovery the same as finished product output. On Gleba, "how to create output" and "where to dump spoilage afterward" are equally important design questions.

The Spore and Pentapod Threat

Gleba's difficulty doesn't end with spoilage. The second axis is spores and pentapods. As explained in the Factorio Wiki entry 'Gleba,' pentapods are attracted to spores—their role is quite similar to pollution pressure on Nauvis. Production increases surrounding pressure, and neglect raises defense burden.

This interacts with spoilage in a nasty way: slow processing lines generate more wasted inventory and shutdowns, requiring more infrastructure to recover, which in turn increases spore-related problems. Gleba ties defense and production together. Short, fast, jam-free lines offer advantages in both freshness maintenance and defensive load.

The same applies around agricultural towers: fruit sitting inside deteriorates. Tower placement is color-coded by UI in 3×3 sector units, but correct placement means nothing if transport is slow. Gleba conquest works better by treating the entire flow—farming, processing, nutrients, spoilage recovery, defense—as one unbroken stream rather than optimizing each separately.

Gleba

wiki.factorio.com

Five Steps to Execute Right After Reaching Gleba

Step 1: Secure Stone and Prepare Landfill in Parallel

The first task after arriving on Gleba is running stone recovery and landfill preparation side by side. On my first playthrough, I thought "find a spot for farming equipment first," but terrain made straightforward placement scarce, and I eventually stopped while creating landfill. Early layout freedom is crucial on Gleba.

The goal here is simple: create land where you can place agricultural towers, biochambers, and initial processing equipment close together. As mentioned, long transport itself becomes freshness loss on Gleba. So the order is: create terrain allowing nearby clustering, not "place what fits where it is."

Stone doubles as base material and landfill prep moves things forward, letting you crowd equipment around towers. This crowding is essential to later stability. The point is to prep terrain for compression—covering the ground work now so processing can happen right where harvest occurs.

Step 2: Place Agricultural Tower in Good Soil ASAP with Minimal Setup

Once landfill is underway, deploy an agricultural tower as quickly as possible. Better to get one running and establish fruit flow than spend time optimizing placement. The soil condition UI color-codes it in 3×3 sectors as shown on the Agricultural Tower wiki page.

What matters is finding good soil that clusters near your processing setup, not visually expansive areas. Beautiful open space is less valuable than being able to place processing equipment adjacent to the tower. I learned this the hard way: placing towers in scenic spots meant processing was distant, and harvest freshness evaporated in transit. Swapping to nearby processing meant fruits reached equipment while still fresh enough to be useful. I'd wasted time and run into completely spoiled input.

You don't need a massive farm yet. Just one tower in good soil with processing a few tiles away suffices. Early Gleba gains more from short processing time than from harvest volume. Maximize yield later; maximize freshness preservation now.

Step 3: Secure Initial Spoilage Material or Plant-Derived Spoilage to Bootstrap Nutrients

Once the tower is placed, secure spoilage material to seed the nutrient supply. On Gleba, spoilage isn't failure debris—it's a resource for line restart. Understanding this makes early setup much easier.

There are two paths: use existing spoilage directly, or intentionally source spoilage from harvested plants and fruit. Gleba's biological items spoil regardless of storage, so early on, abandon "never spoil" thinking and adopt "spoilage has a future use" flow instead.

At this stage, quantity matters less than continuous small circulation. Big chest hoarding backfires—if you recover spoilage but lack the next processing stage, you're stuffed again. Small intake, small throughput: Gleba tolerates this better.

Step 4: Start Nutrient Production from Spoilage at the Right Scale

Once spoilage is secured, immediately chain it into nutrient production. Community measurements suggest "spoilage-to-nutrients roughly 10:1" as a ballpark (though primary source attribution is unclear), so treat this as "approximately correct." The real goal is running a single biochamber continuously on spoilage supply alone.

The math: each biochamber constantly running needs about 15 nutrients/minute. Derivation: biochamber uses 500 kW, nutrients provide 2 MJ each, so one nutrient runs it 4 seconds, yielding 15/minute. The numbers are clear: early focus is getting one machine running non-stop, not bulk production.

Spoilage-sourced nutrients play less optimally than fresh-material ones, but as restart fuel they're extremely strong. They're also easy to source locally and don't depend on transport. Early Gleba thus favors getting nutrients started—even from spoilage—and running equipment over chasing high-efficiency processing far away. The first 1 easily beats the mythical 1000 made perfectly.

Keep the nutrient line itself small: nutrients also spoil, so early design should produce-and-consume in place. The stable Gleba line leans into this "make-consume-immediately" rhythm.

Step 5: Build Minimal Umako/Jelly-nut Processing Directly Adjacent to Tower

Once nutrients are flowing, build a minimal processing line right at the tower for harvested crops. Besides umako, the community calls another fruit "jelly-nut" (note: English names and official terminology may vary—check the Wiki during installation for English names). Both benefit from "process nearby rather than transport far, then use" thinking. Prioritize short distance and freshness preservation over line appearance.

This minimal line needs no large product buffer yet. Requirements are: tower, initial processing, nutrient-consuming equipment, and spoilage evacuation all within a few tiles of each other. Gleba's successful early setups close this small loop before expanding further. Once here, scaling becomes simple: just increase volume while keeping the core loop intact.

Managing Spoilage Resources｜Three Principles for Non-Stop Lines

Principle 1: Small Inventory, High Throughput

Most dangerous on Gleba is copying Nauvis instinct to "store items in chests." Spoilage-prone resources generate more garbage the larger the inventory. The math is simple: if inventory is n and spoilage time is t, average spoilage rate is n / t. Bigger hoards produce proportionally more waste.

The Factorio Wiki's 'Spoilage mechanics' steel chest example is instructive. One steel chest holding 48 stacks × 50 copper bacteria at standard quality, spoiling in 1 minute, averages 2400 copper per minute flowing through. That's not convenient buffering—it's suddenly owning a massive byproduct line. One chest does this, so large Gleba spoilage buffers are dangerously fragile.

I initially believed chests would stabilize things. Reality: buffers masked problems, and minutes later they detonated into spoilage jams. Ditching chest intermediates for direct connections cut spoilage jams visibly, lightening maintenance enormously. Gleba stabilizes via small inventory flowing constantly, not warehoused reserves.

Principle 2: Short Transport and "Local First-Stage Processing"

On spoilage resources, distance is cost. Freshness doesn't vanish independently for each item—it inherits through process stages. Shipping harvested fruit far, then processing it, doesn't produce "fresh finished goods." The long journey already consumed the finished product's lifespan.

Core design: process on-site first, then send immediately to next stage. Tower nearby first-stage processing, next to second-stage, then to consuming equipment. Short belts and direct connection thrive on Gleba for this reason. By contrast, chest and logistics, while flexible, disfavor freshness. Long fruit transport especially wastes value mid-journey, hidden by appearance.

Freshness inheritance makes process layout a question of "where can freshness drop, where must it hold?" High-freshness items stay local; slightly-worn intermediate materials cross distance boundaries. Agricultural science, whose freshness = value, needs preceding stages tight. Restart fuel or insurance lines tolerate low freshness. This splitting makes system-wide design easier.

Self-discipline here: keep fresh goods local, transport only freshness-tolerant materials. Decision-making then becomes automatic. Gleba layout clicks when this distinction is drawn.

Principle 3: Keep Outlets Clear

Gleba stops from output jams more than input starvation. Machines like biochambers trash spoiled stacks to slots, but if output is full, trashing can't happen; the spoilage lingers and stops the machine. Worse: full output blocks trash function, so spoilage occupies input, fuel, or output directly.

Design machines as continuous-draw fluid equipment, not material input boxes. Input-first design stops. Output-first design runs. For spoilage recipes especially, spoilage discharge and finished goods pathways both require design attention.

I stabilized when swapping from supply-focused to output-clearing design. Stop-cause hunting was unclear before; it evaporated after reprioritizing output lanes and trash recovery. Gleba values "jam avoidance" over "production ability."

Trash Slot and Recovery Lane Design

Trash slots are spoilage line safety valves: spoiled stacks inside machines move here, then inserters recover them. If full, the machine stops. They work only as part of a dedicated recovery lane—not just existing.

Practical placement: run one recovery belt separate from finished product belts. Use filter inserters to collect trash slots from each biochamber into this lane, centralized. This way, spoilage from any one machine reaches a common drain. Mixing trash with product belts adds selection complexity and diagnostics difficulty.

Where recovered spoilage goes matters: return to reuse loops for restart strength. But if reuse can't keep up, the recovery lane clogs instead. Practically: primary is reuse, overflow uses backup paths for stability. Skipping this causes the recovery lane to reverse-jam anyway.

Conceptually, treat spoilage as always-present normal logistics, not exception handling. Stable Gleba lines include abnormal flows in the initial blueprint.

Leveraging Freshness Inheritance in Process Layout

Freshness inheritance looks like constraint but becomes powerful if weaponized via process order. Decide upfront: which process preserves freshness, which can tolerate loss. High-freshness-value items deep in the factory starve on transport time; choosing freshness-tolerant intermediates as hubs frees other design.

Research-value items like agricultural science need pre-processing and research site nearby: freshness carries forward, so only last-stage recovery is too late. Restart fuel or insurance lines permit low freshness at the cost of supply reliability. This sorting makes unified rules unnecessary.

My operative principle: long-distance sends freshness-forgiving items; fresh-dependent items stay local. Decisions then auto-determine which stages cluster, which separate. Freshness inheritance unknown = "closer seems right" vague; understood = "this stage must touch, that stage can drift" precise.

Gleba approaches fresh-good logistics. Think via transit time not moved volume, dwell not throughput, process distance not output volume. Layout assembles rapidly this way.

Recommended Layout Comparison｜Direct, Short-Belt, Chest-Logistics: Which Fits?

Direct Connection Layout: Minimum Distance, Minimum Freshness Loss

Direct connection layout connecting harvest, first-stage, and consumer adjacent is Gleba's most stable. It's the first choice from early to mid-game. Freshness loss stems largely from "transit time" and "dwell somewhere," so tightening distances alone improves yield significantly.

Ratio math clarifies: spoilage-prone resources live minutes to 2 hours, leaving no time to rest in chests or long belts. Worse, freshness inheritance means pre-stage loss carries forward. Agriculture-science-type lines feel direct connection's benefits hardest, where freshness = value.

Direct connection aids beyond freshness: trash recovery shortens, so one machine's spoilage processes quickly. On my try, moving from "a bit separate is fine" to adjacent dropped stop frequency visibly. Gleba prefers small factories run quickly to big ones run slowly. Expansion flexibility shrinks—post-setup rewiring gets tight—but early game's problem is stops, not space. Stable non-stop design prioritizes direct connection strongly.

Short-Belt Primary: Visibility and Adjustment Ease

If direct feels cramped, short-belt primary (stages few tiles apart, belt-connected) ranks second-best. Freshness concedes slightly but visibility and maintainability balance excellently, proving quite practical.

Perks: line state reads visually easily. Jams, surpluses, spoilage sources become obvious; adjustments are simple. Direct connection's strength diminishes when density gets extreme and diagnosis gets hard. Short belts ease that drawback.

Especially compatible: separate finished-goods and spoilage-recovery lanes. Distinct flows, easier exit management. Earlier sections' principle of "keep outlets clear" proves practical here. Trade-off: distance rises, freshness loss increases. Occasional stall converts belt buffer into degradation, restarting converts that to spoilage. But it's still gentler than hoarding in chests or distributed over logistics.

Personally: early direct, graduated to short-belt once volume rises and clarity needs boost. Difficulty is still stops, not room.

Chest/Logistics Primary: Management Hell, Inventory Spoilage

Chest/logistics primary boasts appearance freedom and expandability, but on Gleba it's accident-prone. Chests become "degradation waiting rooms," not storage.

Numbers show danger: steel chests hold 48 slots; Wikipedia example has standard-quality copper bacteria at 48 stacks × 50 converting to 2400 copper per minute (1-minute spoilage). Interesting conversion illustration, but rotate to freshness-preserving intent: large hoarding = large value loss rate. Accidental simultaneous spoilage = catastrophic inventory collapse.

Logistics robots suffer similarly: holding time degrades freshness. More endpoints and charging delays = hidden dwell accumulation. I once over-roboticized; spoilage happened mid-air, tripling trash-only output. Reverting to direct connection fixed it; stops and UPS both improved. Logistics isn't "smart" on Gleba; it's "slow degradation multiplier."

Chests and logistics aren't forbidden—seeds, non-spoilers, emergency reserves work fine. But spoilage-primary routing through them adds oversight: freshness monitoring, inventory caps, jam recovery, restart sequences. Early-to-mid doesn't need that overhead.

Why Long Spoilage Transport Fails

Long-distance spoilage transport loses on three fronts: freshness inheritance, distance loss, jam total loss.

First, inheritance: material freshness consumed in transit carries into finished goods. Agricultural science values prove this: source state = product cap. Long-before-process layouts pre-cut finished product ceilings.

Second, distance loss: Gleba spoilage times span minutes to 2 hours, so short-lived materials' primary cost is transit itself. Resting doesn't process; freshness alone erodes. Fresh → spoilage-sourced nutrient → post-transport material quality drops each step. High-efficiency hunts favor "make-use-nearby" over "ship-then-refine."

Third, jam total loss: long lines jam fully on single-point failures. Full belts, chests, or robot networks all become megabuffers when stopped. Gleba's fear isn't inventory itself—it's spoilage timer attached to suddenly frozen stock. Even restart won't restore that material value.

Ratios tell a story: expanding transport doesn't reward proportionally. Dwell points multiply, monitoring spreads. Spoilage resources solve via process-in-place to freshness-tolerant form, then move—not moving fresh. Layout elegance yields to spoilage practicality.

Spoilage Handling: Instant Nutrients vs. Emergency Reserve vs. Excess Discard

Spoilage's handling strategy dramatically changes restart readiness. I operationally split: instant nutrient conversion, emergency reserve, overflow discard or burn.

Instant nutrient conversion is most practical. Spoilage → nutrients → refeeding biochambers (which eat ~15/minute per unit) restarts fast. Hoarding is moderate, operation manageable.

Emergency reserve provides restart insurance: last-resort fuel when everything collapses. Risk: reserve growth means inventory bloat, cramping normal flow. Restrict reserves to "insurance only."

Excess burning minimizes space cost but surrenders restart material. I treat it as overflow path, not primary—reuse first, burn-extras second. This two-tier keeps both restart-able and jam-free.

Choice axis: stability = instant-nutrition primary, restart-insurance = small reserve, ongoing-clearance = controlled discard. Gleba generally prefers "discard-excess to protect flow" over "save-everything."

Common Pitfalls and Fixes｜Seed Starvation, Nutrient Starvation, Spoilage Jams

Fruit Rots, Seed Loop Collapses

Gleba's #1 early pit: fruit produced but processing delayed → seed return falters, farm starves. Fruit alone isn't the loop; it must process to seeds and fuel. Mid-stage rot breaks the cycle, creating mysterious "inventory exists but seeds vanish, nutrients vanish" stops.

Worst setup: fruit → large chest → distant processing, yielding spoilage tsunami. Gleba materials spoil in minutes to 2 hours; short-lived ones lose in pure time. Processing delay = full spoilage loss.

I initially thought large pre-research chests safe. It wasn't: overstuffed chests spoiled catastrophically, tanking research and recovery simultaneously. Spoilage-avalanche weight grows with stock volume.

Fix: process fruit near harvest, immediately loop seeds back to planting, fuel to burners. Small nearby processing ≫ high-speed distant processing. Seed-loop continuity prevents farm collapse.

Machine Output Full, Trash Non-Functional → Stops

Machine output full disables trash slots—Gleba's signature jam. Slight blockage becomes permanent stop because spoilage can't escape, freezing input, fuel, or output in place. Skip recovery lanes, game over.

Biochamber example: spoilage stacks go to trash, but full output prevents their evacuation. Stuck spoilage = blocked machine. Feeding more inserters doesn't help if jam is "nowhere to dump garbage."

Fix: always-on recovery belt, separate from output, for forced spoilage removal. Even a single lane prevents output-jamming total failure. Recovery-lane buffer availability keeps machines running despite spoilage events.

Hand-Crafting Queues, Instant Spoilage

Often missed: large hand-craft queues spoil mid-production. Late items finish with near-zero freshness. Looks like crafting success; actually resource burning.

Gleba respects queue dwell-time heavily. 50-item queue means items 30–50 wait while 1–30 craft, freshness bleeding the whole time. Completion approaches zero-freshness by queue end. You didn't "make 50"; you "spoiled 50 while making 1."

Early experience: bulk-crafting felt productive but Gleba punished it hard. Large predictive batches break.

Fix: small queues, short cycles. Necessary volume only, cleared immediately post-craft. Hand-craft applies Gleba's "flow, don't hoard" principle too.

Long-Distance Transport → Zero Freshness → Total Loss

Gather, distant-transport, then process is designed for failure. Stacking dwell compounds: chest wait, belt transit, receiver clog; multiple chances to spoil entirely.

Biotech example: chestful of fruit waits, then travels, then sits receiving. Freshness = zero when finally processed. "Inventory exists" but value disappeared.

Gleba's advantage comes from short, fast, multi-stage proximity, not bulk logistics. Moving distance inherently throttles freshness. Solve via local processing first.

Blackout / Nutrient Starvation Restart

Gleba's restart challenge: nutrient supply ↔ nutrient production ↔ biochamber interdependency. Stop one, all three stop. Cold-start without reserves = infinite-resume puzzle.

Fix: modest emergency spoilage buffer, separate from normal stockpile. Minor reserves ignite a single biochamber, which seeds subsequent chains. Avoid mega-reserves (space hog); maintain minimal spark-plugs.

Restart sequence: fire one nutrient source, then seed-loop, then primary production. Parallel restart fails; sequence wins.

Blackout similarly: don't restart everything simultaneously. Prioritize fuel generation, gradually wake systems. Gleba's cold-start is a sequence, not a switch.

Spoilage Isn't Just Trash｜Recycle, Fuel, Emergency Reserves

Spoilage → Nutrients and 50% Freshness Bootstrap

Gleba treats spoilage as a resource ladder, not failure. Community measurement suggests "spoilage → nutrients yields ~50% freshness" restart fuel (caveat: primary Wiki source citation unavailable—treat operationally). This means restarted biochambers run on secondhand energy.

Math: biochambers burn ~15 nutrients/minute each. Constant restart doesn't demand enormous reserves, just reliable small trickles. Spoilage routes supply that ignition.

Nutrient Recycling Notes

Some community reports suggest "nutrient recycling can yield ~2.5 spoilage items recovered per input" (note: primary-source attribution uncertain—apply with environment-awareness). Treat as concept validity rather than fixed numbers.

Design: recycling goes secondary, not primary. Main supply: fruit/initial processing. Recycling: cleanup network. Excess-handling via separate circuit = clean architecture.

Direct Plant Harvest and Startup Boost

Spoilage directly harvestable from plants jump-starts without completed line infrastructure. Pre-harvest gives ignition fuel before processing chains exist.

Strong for "restart from zero": direct harvest = outside-loop bootstrapping. Normal spoilage interdependency (spoilage-source needs machine using spoilage-derived fuel) has escape hatch: initial harvest cuts that loop.

Conceptually: ignition spark, not long-term fuel. One biochamber fires, then output fuels chains. Direct harvest bridges the gap before those chains stabilize.

Emergency Reserve and Overflow Design

Spoilage isn't infinite-storage-grade. Small reserves (restart insurance) ✓. Large reserves (inventory bloat) ✗.

Split roles: keep tiny emergency stock, channel normal recovery to reuse, discard overflow. Ceiling-bound reserves prevent space creep while keeping restart possible. Exceed threshold → dump excess.

Mentally: reserve = spark, flow = engine, excess = trash. All three purposes, none dominating.

Simple Flow: Fruit → First-Stage → Nutrients → Biochamber

Organized simply: skip complexity, execute flow.

1. Harvest fruit
2. Process nearby
3. Create nutrients, feed biochambers
4. Recover mid-spoilage
5. Recycle spoilage → nutrients for restart fuel
6. Excess discard

Spoilage isn't total loss; it feeds fuel pipelines. Two-tier: goods → main production; spoilage → recovery fuel. Gleba's design philosophy: nothing wasted, everything routed.

Advanced Topics｜Agricultural Science Packs and Off-World Operation

Agricultural Science Freshness and Research Efficiency

Agricultural science packs aren't "make bulk, stockpile far away." Freshness directly affects research value, so output quantity and quality diverge. Research stalls when packs arrive degraded, not undersupplied.

Effective: reduce distance before tweaking circuits. Production → research labs direct-adjacent, short-belt prioritized, chest-dwell eliminated. These three alone shift research scaling visibly.

Freshness inheritance matters too: pack materials' age becomes pack age, limiting research regardless of pack volume. Tweaking production timing matters more than optimizing later.

My observation: adjacent placement vs. slightly-distant layout yielded night-and-day research stability. Same supply count, but staggered jitter disappeared. Agricultural science is distance = research.

Biochamber Off-World and Challenges

Biochambers work off-world (Fulgora, Aquilo, etc.), leveraging 50% production bonus. Issue: nutrient supply. ~15 nutrients/minute per unit at scale becomes distribution problem.

Off-world adds transport: nutrients spoil during shipment, degrading on arrival. Machine-internal spoilage triggers trash jams. Long-haul nutrient supply fails gracefully.

Options: on-site nutrient generation + consumption, or short-haul, minimal, immediate use. Long-distance doesn't work reliably.

Tradeoff: biochambers are powerful, nutrient supply is weak. Off-world design pivots to "solve fuel first, then deploy machines."

Quality for

Summary: Gleba Is a Flow-Through Factory, Not a Storage Factory

The key takeaway for Gleba's opening stays consistent. Secure stone and landfill first, place agricultural towers, bootstrap nutrients from initial spoilage, and close minimal Yumako and Jellynut lines in short-distance direct connections. The goal isn't stockpiling -- it's continuous output assuming spoilage.

The design philosophy is the same: what wins isn't large-capacity buffers but high throughput, short transport distances, zero output jams, permanent reclamation lanes, and placement that doesn't break freshness inheritance. I've found that approaching Gleba as a "flow-through factory" rather than a "storage factory" makes both initial setup and restarts more stable.