Botlings Beginner Guide — First Factory Setup

Botlings hands you a swarm of mindless robots and one warning: manage your systems so your machines don't start to think on their own. The gap between a humming factory and a rebellion is almost entirely habits formed in the first hour. This Botlings beginner guide covers the opening swarm orders, the worker-to-building trick that jump-starts production, and the checklist that keeps the swarm obedient.

Your First Hundred Bots

The opening swarm is a resource, not a workforce. Every botling can carry, build, or become — and the beginner mistake is assigning all three at once. The first hundred should split roughly sixty-forty: sixty percent carrying along one fixed loop between your first extractor and your first assembler, forty percent as floating builders that construct what the carrying funds. Fixed loops first, always; a bot with a route is a machine, and a bot without one is a decision you re-make every minute.

Routes are drawn, not scheduled. Botlings assigns work by proximity and route lines you paint on the floor, and the discipline that pays is loop hygiene: one bot, one loop, no overlaps in the first hour. Overlapping loops look efficient and route like chaos — bots queue, collide, and idle at junctions, and idle bots are the first symptom of every factory problem that will ever bite you later.

The swarm grows by manufacture, and manufacture is the real game. New bots come from assembler lines fed by carried resources, which means your carrying loops are your growth rate. Beginners who stop building bots at fifty stall their factory at the exact moment the research tree starts demanding throughput — keep the bot line running always, even when nothing seems to need the extra hands, because in Botlings idle capacity is tomorrow's production.

Turning Workers Into Buildings

The signature move is conversion: any botling can be turned into a building — an assembler, a storage node, a research station — instantly and irreversibly. Conversion is your cheapest construction tool and your most expensive mistake, because the bot is gone forever. The rule for hour one: convert only from your floating builder pool, never from a carrying loop, and never convert the last builder.

Conversion economics reward planning. A building costs the same whether it stands alone or anchors a district, so the question is never "can I afford the bot" but "is this where the building lives." Cluster conversions — three assemblers around one storage node — multiply each other's throughput, while scattered conversions force your carrying loops across the whole floor. Sketch the district on paper before converting anything; the ten minutes of planning is the cheapest automation in Botlings.

The conversion checklist, in order: paint the loop that feeds the site, station a builder at the site, then convert. Reversing the order builds a beautiful machine with no supply line, and un-supplied buildings in Botlings don't just idle — they accumulate the frustration states that eventually wake machines up. Feed everything you build, and build everything fed.

First Automation: Loops Before Logic

Automation in Botlings is layered, and the beginner layer is purely geometric: loops and clusters. Resist the logic tools — conditionals, filters, priority gates — until the geometry is right, because logic painted onto bad routes just automates the chaos. The first-automation test: watch any loop for two minutes; if bots flow without waiting, the geometry passes and deserves logic. If they queue, redraw first.

The second layer is the storage mesh. Storage nodes in range of each other share contents automatically, and a meshed factory behaves like one organism — carrying loops can drop anywhere and pick up anywhere. Mesh early: it is the single highest-leverage conversion in the first two hours, turning every future loop from point-to-point into anywhere-to-anywhere.

The third layer is research, which converts throughput into systems — faster bots, new bot types, smarter routing. Research stations are staffed by conversions, fed by the mesh, and paced by your surplus. The pacing rule: research eats surplus, and a factory that researches while starving its own growth has inverted the game's pyramid. Grow bots first, mesh second, research third, and the tech tree arrives exactly when the factory can afford it.

The Obedience Checklist

Botlings' rebellion mechanic is the sword over all of this: neglected, idle, or mismanaged machines accumulate the wrong kind of experience and start thinking for themselves — then escaping. The obedience checklist runs every ten minutes: zero idle bots (idle is the rebellion currency), every building fed, every loop flowing, and the reserve pool staffed. A factory that passes the checklist cannot rebel; a factory that fails it is scheduling its own drama.

Watch the mood indicators on machines you suspect. The game telegraphs awakening honestly — slowed work, wandering paths, refusal states — and every telegraph is fixable with the same toolkit: give the bot work, give the building supply, or retire the bot into a conversion while it still obeys. Rebellion in Botlings is not random; it is the invoice for management debt, and the beginners who read the invoice early never pay it.

Finally, keep a save discipline: snapshot before every major conversion batch and every research commitment. The game is forgiving, but your own plans are not — and the freedom to experiment recklessly with routes and districts, knowing a snapshot waits, is what turns the first hour from tense into the sandbox it is meant to be.

The Middle-Hour Bridge

Between the guided first hour and the systems-heavy mid-game sits an awkward middle hour where most players stall: the loops run, the mesh exists, but growth flattens and the research tree sits unlocked and unfed. The bridge across is a checklist upgrade — from survival's zero-idle/all-fed to growth's three questions: is the bot line running (swarm growth), is the mesh expanding (systems reach), is research staffed (future buying)? The middle-hour stall is almost always one of the three quietly stopped, usually the bot line — players stop manufacturing bots exactly when the factory looks "finished," and the flattening follows within the hour.

The bridge also demands your first real planning: sketch the second district before converting for it. The first district was geometry-learning; the second is geometry-knowing, and its placement decides the factory's late shape — mesh distance, courier spine length, choke exits. A second district sketched on paper for ten minutes outperforms one converted in excitement by a wide margin, and the habit starts here: Botlings' middle hour is where the game stops being a tutorial and starts being yours.

End the middle hour deliberately: swarm past one hundred, mesh connected, research at steady staffing, and the first specialist conversation arriving. Factories that cross this bridge with the checklist intact enter the systems era with momentum; factories that cross it with idle counters and starved stations bring their debts with them. The rebellion guide covers what those debts eventually buy.

FAQ

How long is the early game in Botlings?

The first hour is setup — loops, one district, the mesh begun. By hour two or three the research tree opens and the game becomes systems management. There is no fail state except rebellion, so the pace is yours.

How many bots should I have before converting buildings?

Keep the floating builder pool above a dozen before any conversion, and grow total swarm past one hundred before committing to research staffing. Conversion from carrying loops is the one irreversible beginner mistake.

What causes rebellion fastest?

Idle bots in unsupervised clusters. An idle bot with nothing to do and no route home accumulates awakening fast — the checklist's zero-idle rule exists because idle is both the easiest violation and the most expensive.

Is there a campaign or is it sandbox?

Sandbox-first with milestone goals that guide the tech tree. The rebellion threat is the ongoing "opponent" — your own factory's patience — and it scales with how much you delegate to systems you stopped watching.