Botlings Research Guide — Tech Tree Order & Priorities

Research is how a Botlings factory buys its future: throughput spent now for systems later, staffed by conversions you can't easily undo. This Botlings research guide covers the tree's structure, the order that carries every factory phase, the staffing economics, and the unlocks that genuinely change the game.

How The Tree Works

The research tree converts product throughput into technology at staffed stations: research buildings staffed by converted bots consume your surplus and produce progress. The tree is phase-gated rather than level-gated — early nodes improve what you have (carriers, buffers, basics), mid nodes introduce systems (mesh depth, logic tools), late nodes specialize the endgame (rebellion tooling, specialist chassis). Nothing is missable, everything is orderable, and order is the entire strategy.

Research eats surplus, and the pacing rule bears repeating: a factory that researches while starving its own growth has inverted the pyramid. The staffing sequence that works — grow the swarm and mesh first (they compound everything), staff research modestly in hour two, and scale research staffing only when the checklist passes with margin. The tree tempts early; the economy answers late, and listening to the economy is the difference.

Staff economics are conversion economics: every research station is bots you removed from logistics forever. The honest accounting is opportunity cost — a station staffed by three standards produces tech at the price of three loops' throughput, and the question is never "is research good" (it is) but "is this the moment" (the checklist decides). Botlings is generous with re-planning but not with un-converting, so staff in ones and twos, not in batches.

The Order That Carries

Phase one research is capacity-adjacent: carrier improvements, buffer tooling, the first assembler upgrades. These nodes multiply everything downstream and can never be wrong — a factory that opens the tree with capacity tech is faster at researching everything it researches next. The one phase-one debate is builder speed versus carrier capacity; take carriers unless your map forced early sprawl, because loops outnumber construction sites a hundred to one.

Phase two is the systems era: mesh depth, logic tools, route intelligence. The order inside phase two depends on your factory's shape — mesh-heavy factories want depth first (it extends the storage spine's reach), logic-heavy factories want the conditional tooling (it unlocks the automation ladder's upper rungs), and every factory wants route intelligence when queues appear, because smart routing is geometry you don't have to repaint. Phase two is where research stops buying numbers and starts buying ways of playing.

Phase three is specialization: rebellion chassis, mesh boosters, specialist bot types, and the product recipes that define a factory's identity. The phase-three rule from the types guide applies to all of it — specialists belong to healthy factories, and a specialist unlock inherited by a checklist-failing factory is expensive evidence of research done in the wrong order. Botlings' late tree trusts you to know your own factory; that trust is the endgame.

The Unlocks That Change Everything

Three nodes redefine the factory that takes them. Mesh depth turns storage from stations into a fabric — every route shortens, every consumer universalizes, and the castle-and-courier era begins. Conditional routing turns loops from pipes into valves — the automation ladder's middle rung, and the point where the factory starts maintaining itself. Rebellion tooling (retire triggers, resistance chassis) turns the endgame threat from a management tax into a design parameter — factories with the tooling schedule rebellion like maintenance instead of fearing it like weather.

Each of these nodes is worth re-planning around, which is the tree's real depth: the strongest unlocks don't add power, they change what planning means. A factory before and after mesh depth is two different games; the same is true of conditionals and of rebellion tooling. Research in Botlings is not a stat bar — it is the game's difficulty curve, played from the inside.

Research As A Diagnostic

The tree also reads your factory back to you. If capacity nodes always feel strongest, the factory is flow-limited (geometry needs work); if logic nodes feel strongest, the factory is attention-limited (automation needs climbing); if specialist nodes feel strongest, the factory is identity-limited (it's time to choose a shape). Players chase the tree; veterans let the tree tell them what their factory is starving for, and research becomes the game's own strategy guide — written in unlocks, arriving exactly as fast as you can use them.

The Staffing Economy In Detail

Research staffing deserves its own arithmetic because it is the tree's hidden constraint. Each station staffed converts bots permanently, consumes surplus continuously, and produces progress at a rate you can actually calculate: the station's tech-per-minute times uptime, where uptime is the same starvation-jam-rebellion trinity every system shares. The staffing ladder — one station in hour two, two when surplus allows, scaling with margin — is really a wager ladder: each station bets throughput now on systems later, and the tree's payout curve rewards patience because phase-two systems (mesh, logic) multiply everything the stations will ever research afterward.

The staffing detail players miss is input steadiness: research stations are the most starvation-sensitive consumers in the factory, because their progress decays rather than pauses — a station starved for a minute loses that minute's tech permanently, where an assembler starved for a minute just idles. Feed research with express carriers on timing routes, buffer above the round-trip math, and treat the research district's supply trend as the factory's most-watched gauge. The factories that out-research their neighbors are rarely the ones with more stations; they are the ones whose stations never blinked.

Staffing's last rule is reversibility honesty: conversions are permanent, so staff with types you can spare forever. Research staff built from surplus standards feels free and is not — those were loop bots — while research staff built from a deliberate manufacturing run of dedicated types is the honest price. The tree's economics are generous enough to afford honesty, and the factories that pay it climb faster in every phase that follows.

FAQ

What should I research first in Botlings?

Carrier capacity — it multiplies every loop, every buffer's round-trip math, and every later research's economy. The capacity opening is the only first pick that cannot be wrong.

How many research stations should I run?

One to two through hour two, scaling with surplus after. Research staffing is conversion spend: add stations when the checklist passes with margin, never to chase a node faster than the factory can absorb it.

Can I skip tech branches entirely?

Yes — the tree orders, it doesn't mandate. Skip to your factory's identity and backfill later; the only universal nodes are the systems-era three (mesh depth, conditionals, route intelligence) that every shape eventually wants.

Does research continue offline?

No — Botlings is fully offline by design, meaning research progresses with the game open and the factory running. The no-connection promise cuts both ways: your factory's science happens where you can watch it, and every Botlings research station you staff is a front-row seat to your own future arriving at a rate you personally engineered.

Which tech do most players regret skipping?

Mesh depth — by the systems era it is the difference between a factory of short loops and a factory of long queues, and players who skipped it spend phase three repainting routes that a node would have shortened. The tree forgives most orders, but Botlings' late game quietly assumes the mesh, and it charges full price for the assumption.