Botlings Production Lines Guide — Assemblers, Chains & Layouts

Production lines are where Botlings stops being logistics and becomes industry: assemblers chained into chains, chains clustered into districts, districts fed by the swarm. This production lines guide covers the chain patterns, layout rules, buffer sizing, and the throughput math that separates a workshop from a factory.

The Anatomy Of A Line

A production line is stations in sequence: inputs in, product out, with the swarm as the conveyor. The anatomy that works: one input buffer per station, one output buffer shared between neighbors where recipes allow, and stations spaced so carriers can reach any buffer without crossing the line. The anatomy that jams: stations back-to-back with no buffer room, shared input buffers between two stations (carriers queue at the contested drop), and lines painted along the line itself so carriers and products fight the same corridor.

Direction is a layout decision, not a preference. Lines should flow one way — resources enter at one end, products leave at the other, and the swarm's loops circulate the same direction as the flow. Counter-directed lines (carriers running against product movement) halve themselves; cross-fed lines (inputs arriving from the far end) spend their length in transit. The strongest layout in the game is the straight or gently curved line with its input district on one flank and its consumers on the other.

The chain rule: every station should consume its input faster than the station before it produces, or the surplus buffers grow forever. Chains are designed bottleneck-first — decide the line's throughput by its slowest station, size everything else to feed that station exactly, and let no upstream station out-produce the choke. A balanced line idles nothing and starves nothing; an unbalanced line converts your swarm's work into buffer inventory that sits and (worse) into idle carriers that wander.

Layout Patterns That Scale

The Spine is the first pattern: a straight line of assemblers along the mesh backbone, input drops on one side, output pickup on the other. It scales linearly — extend the spine, extend the swarm — and it reads at a glance, which is worth more than cleverness. Every factory should have a spine before it has anything else, because the spine is the pattern that teaches the others.

The Ring is the throughput upgrade: stations in a loop with buffers inside and carrier loops outside, products flowing station to station around the ring while inputs arrive from any angle. Rings suit multi-step recipes where intermediates shouldn't travel far, and they pair beautifully with the mesh — one ring per recipe family, mesh nodes between rings, couriers handling the family-to-family moves.

The District is the scale pattern: a cluster of spines and rings sharing a storage mesh, a builder reserve, and a choke exit. Districts are how factories pass two hundred bots without becoming unreadable — each district is a self-contained economy with one inflow point and one outflow point, and the factory becomes a map of districts rather than a map of machines. Botlings' late-game content (rebellion chokes, mesh spines) is all district-scale tooling, which is the game telling you where the design conversation ends up.

Buffers And Throughput Math

Buffers are the line's suspension. Size input buffers to cover the carrier round-trip — a station consuming one unit per ten seconds with a sixty-second carrier loop needs six units of buffer, or it starves rhythmically and you'll chase a jam that is actually arithmetic. Size output buffers to cover consumer downtime, and share buffers between adjacent stations only when the stations never want the same resource at the same time (the shared-buffer rule from the line anatomy).

Throughput math is one equation wearing different hats: output equals stations times rate times uptime. Uptime is the hat you control — it is starvation-proofing (buffers), jam-proofing (geometry), and rebellion-proofing (the checklist) combined. A factory at ninety percent uptime out-produces a factory with fifty percent more stations at sixty percent uptime, which is why this guide spends its length on flow rather than on station counts. Build fewer stations, feed them perfectly, and the numbers follow.

The line's honest dashboard is buffer trend: inputs trending empty means upstream starvation, outputs trending full means downstream blockage, both stable means the line is balanced and you can leave it alone. Botlings' factories fail in trend lines long before they fail in events — the operators who watch buffers read tomorrow's jam today.

Research-Backed Upgrades

The tech tree upgrades lines in a fixed order of impact: carrier capacity first (every buffer's round-trip math improves), station rate second (renumber the bottleneck, then rebalance), and the specialist unlocks last (rebellion chassis, mesh boosters — the systems-era tools). The mistake is researching station rate before capacity: faster stations on starved inputs just starve harder, and the tech points bought a bigger appetite instead of a bigger dinner.

Product research is the parallel track: new recipes unlock new products, and products decide factory shape — heavier products want heavies and short spines, high-value intermediates want rings close to their consumers. Research products when the economy can absorb their logistics, not when the tree first offers them, because a product unlocked without its routing built is inventory you can't move and idle time you invited.

Line Districts And The Grand Layout

The endgame layout question is district arrangement: where the spines, rings, and mesh spines sit relative to each other. The grand pattern that survives every patch of player wisdom: raw districts at the perimeter, processing districts at the middle ring, product and research districts at the core, with the mesh spine as the factory's main street. Flow moves inward — resources get denser and more valuable as they approach the core — and the courier economy runs the ring roads. The layout reads like a city because it is one, and cities that zone by noise (loud processing) and value (quiet research) stop fighting themselves.

District interconnection follows two rules. Choke everything: each district gets its one-or-two controlled exits, which doubles as rebellion insurance and as traffic governance — couriers queue at chokes by design, and the choke buffers absorb the timing mismatches between districts. And mesh-spine twice: the spine runs a loop, not a line, so no district's connection dies with a single cut. The dual rules cost little at planning time and buy the two properties that matter at scale — governable traffic and un-killable supply.

The grand layout's last virtue is that it makes the factory legible to its own operator. Botlings at scale is a management game played against your own ability to read your creation, and the zoned-ring layout means every screen answers "where am I and what happens here" instantly. The layouts that fail at two hundred bots are not the ones with wrong throughput math — the math always balances eventually — they are the ones where the operator could no longer tell what the machines were thinking. Build legible, and the factory stays yours forever.

FAQ

What is the best production line layout?

The Spine first, always — then Rings for multi-step recipes as the mesh arrives, and Districts when the factory outgrows one screen. The patterns stack; the order is the curriculum. Botlings players who master the spine learn every other pattern in half the time, because the spine teaches the one lesson the whole game repeats: flow in one direction, buffers between friends, and geometry before cleverness.

How big should buffers be?

Cover the round trip: consumption rate times carrier loop time, plus one for grace. Starvation with "enough" bots is almost always buffer arithmetic, not swarm shortage.

How do I know which station is the bottleneck?

Watch buffer trends: the station whose input always trends empty is downstream-starved by a bottleneck ahead of it; the station whose output always trends full is the bottleneck. The full-output station is your choke — upgrade it or feed it better.

Do products need dedicated lines?

Complex products want rings close to their consumers; simple products share spines happily. The routing rule of thumb: the more steps a recipe has, the less its intermediates should travel. Botlings' recipe depth is the layout's real syllabus — every multi-step product is a lesson in keeping intermediates close, and every factory eventually learns that the strongest production line in the game is the one nothing has to cross.

How do I expand a line without rebuilding it?

Extend the spine, re-staff the choke: lengthen the line in its own direction, add buffers at the new stations, and check the junction where the extension meets the mesh. Lines that grew well were lines built with direction left in them — Botlings rewards factories that leave room for their own futures.