Timberborn: How to Use Bots – Scaling, Fuel, and Lifespan

Bots are Timberborn’s late-game answer to labor limits. You do not recruit them like beavers and you do not treat them like a simple upgrade to population; you manufacture them through an industrial chain, then keep them running with faction-specific support. If you only need the short version, the safe way to start is one Bot Part Factory, one Bot Assembler, the fuel or charging support your faction requires, and a single pilot bot assigned to a job that benefits from round-the-clock uptime.

The big mistake is assuming the hard part is building the bot itself. In practice, the hard part is everything around it: intermediate parts, storage, logistics, fueling or charging, and steady replacements. Bots are extremely strong because they can work continuously and are not tied to beaver work hours or well-being, but they also have a fixed lifespan, so every bot program in Timberborn is really a production-and-replacement program.

Quick Bot Rules That Matter Most

• Bots are a late-game workforce that can replace or supplement beavers in most standard jobs.
• Folktails use Timberbots, which run on Biofuel.
• Iron Teeth use Ironbots, which depend on Charging Stations.
• Bots operate continuously, so they are best in jobs where overnight downtime hurts output.
• Bots have a 70-day lifespan, so you must plan ongoing replacements.
• A practical benchmark is about one bot every 36 in-game hours per production line, but that number is a planning heuristic, not a universal promise.
• The parts chain is usually the bottleneck, not the final assembly building.

What Bots Actually Do in Timberborn

Bots exist to solve a problem every mature Timberborn colony eventually hits: you can have enough food and water to support growth, but still not enough labor to keep every useful building running at the same time. Bots let you move past that ceiling. They can handle most standard jobs, and some automation-oriented duties are reserved for them as well, which makes them more than a simple convenience unit.

The reason they feel so strong is not that each individual bot is magical. It is that they ignore the day-night work rhythm that constrains beavers. If a production chain benefits from running through the night, bots can keep it moving. That makes them especially valuable in industrial districts where every idle hour causes storage gaps farther down the line.

This also means bots do not fix every problem. If your colony is short on raw materials, power, hauling space, or storage, bots will simply expose that weakness faster because they keep consuming inputs and producing outputs without the usual daily pause.

Timberbots vs. Ironbots

Each faction gets its own bot family, and the difference that matters most is the support system behind it.

• Folktails build Timberbots. These run on Biofuel, so your planning problem is fuel production and refueling access.
• Iron Teeth build Ironbots. These use Charging Stations, so your planning problem is reliable power and convenient charging coverage.

For Folktails, the important support building is the Refinery, which produces Biofuel from agricultural goods and water. That makes Timberbots feel tightly linked to an already healthy farming base. A Timberbot network can look fine on paper and still underperform if the bots spend too much time traveling for fuel, so Biofuel Tanks should be placed close to the jobs you want them to cover.

For Iron Teeth, the equivalent concern is not liquid fuel but charging access and power stability. If your power grid is shaky or your Charging Stations are badly placed, Ironbots lose the very advantage you built them for. The faction choice is less about which bot is “better” and more about which infrastructure burden fits your colony more naturally.

How to Get Your First Bot Without Stalling Your Colony

Stabilize the basics first

Do not rush into bots while food, water, storage, and power are still fragile. Bots are a multiplier on a stable economy, not a shortcut around one. If your beaver-run industry already stops because inputs are inconsistent, a bot line will only create a more expensive version of the same problem.

Build a pilot production line

The safest opening is one Bot Part Factory and one Bot Assembler. That is enough to test the system without committing to a full district-wide conversion. The goal here is not maximum output. The goal is to see whether your colony can keep parts flowing, keep the assembler supplied, and support the finished bot after it comes online.

Add the faction support immediately

Folktails need a Refinery feeding Biofuel production and enough Biofuel Tanks that Timberbots do not waste their uptime walking long refill routes. Iron Teeth need Charging Stations with dependable power behind them. Build this support before you try to scale. A bot that spends too much time refueling or waiting for charge is not a labor solution; it is a logistics warning.

Use the first bot as a stress test

Assign your first bot to a job where continuous uptime matters. That lets you judge the system honestly. If the bot improves output and the production chain stays supplied, you are ready to expand. If the bot keeps exposing empty inputs, missing fuel, or awkward travel distances, fix that before adding more bodies to the problem.

Why the Part Chain Is the Real Bottleneck

Bot assembly looks like the headline building, but most scaling failures happen earlier in the chain. Bots require multiple intermediate parts, and that means the true challenge is not the last step of assembly. It is whether you can keep all required components arriving consistently enough that the assembler never sits idle.

This is why experienced bot setups almost always add dedicated part production, nearby storage, and cleaner internal logistics before they add more assemblers. If every input has to cross half a district by hand, the chain will look theoretically adequate while underperforming in real colony conditions.

A commonly used planning benchmark is one bot about every 36 in-game hours per line. That is useful for estimating replacement capacity, but it only holds up if the supporting part factories are actually fed. For a district aiming at roughly 5 to 10 bots, a practical starting point is around 2 to 3 Bot Part Factories and 1 to 2 Bot Assemblers, plus the fuel or charging support to match. Treat those numbers as field-tested heuristics, not fixed law. Map size, haul distance, vertical building layouts, and the rest of your industrial chain all change the answer.

If you are deciding between “more assemblers” and “better support for the existing line,” support usually wins first. A single well-fed assembler is more useful than several starved ones.

Where Bots Perform Best

Bots are strongest in jobs that punish downtime. Any building or route that you wish kept running overnight is a natural candidate. Continuous manufacturing chains, repetitive logistics, and always-on industrial support all get more value from bots than low-pressure daytime work that already fits comfortably within a normal beaver schedule.

That does not mean you should try to replace every beaver immediately. Early bot fleets work better when they are targeted. Use them to remove the most painful labor bottlenecks first, then let your beavers cover roles where flexible scheduling matters less. Bots are at their best when they stabilize the backbone of the colony rather than scatter across random jobs.

In current Timberborn, this also fits the broader late-game shift toward heavier automation. Bots pair well with colonies that already move materials efficiently and can keep industrial buildings supplied without constant manual correction.

Lifespan Planning: The Rule You Cannot Ignore

Bots are not permanent. Community reference material places their lifespan at a fixed 70 days, which means every bot you build is also a future replacement you are committing to. This is the single most important mindset shift for long-term bot play: do not count bots as permanent assets; count them as a workforce with scheduled attrition.

The practical math is simple and useful. A fleet of 10 bots needs roughly one replacement every 7 days just to stay even. That is why the 36-hour assembly benchmark matters. Even a small, steady line can comfortably maintain a modest fleet if the supply chain is stable. A flashy burst of production, on the other hand, can create a dangerous replacement cliff later.

If you assemble most of your bots in the same short window, many of them will expire in the same short window about 70 days later. Staggering production is often safer than building your whole fleet in one wave. It smooths replacement demand and makes the district easier to plan around.

Common Mistakes That Break Bot Districts

• Scaling the assembler before the parts chain. If inputs are inconsistent, adding final assembly does not solve anything.
• Ignoring refueling or charging travel time. A bot with long support trips gives away the uptime advantage you paid for.
• Skipping dedicated storage. Intermediate parts need short, reliable movement paths or the line bogs down.
• Using bots to cover a weak economy. Bots amplify stable production; they do not create stability from nothing.
• Building too many bots in one batch. Synchronized lifespans can cause abrupt workforce drops later.
• Treating community ratios as exact formulas. Benchmarks are useful starting points, but district layout and logistics decide the real output.

If Older Guides Mention Golems

If you are reading older Timberborn material, you may see bots referred to as Golems. That is older terminology for the same broad mechanic. The important part is not the name change but the fact that older advice can mix outdated terms with older balance assumptions. When following any legacy guide, trust the general logic of production chains and replacement planning more than any exact ratio it gives.

How Many Bots You Actually Need

You do not need a giant fleet for bots to matter. A single pilot bot proves the system. A small group can keep your most important industrial chain running through the night. A district-sized fleet only becomes worthwhile once part production, storage, and faction support are all stable enough that replacements feel routine instead of disruptive.

The best bot setups in Timberborn are usually not the ones with the largest headcount. They are the ones where assembly, fuel or charging, and replacement all run smoothly enough that bots stop feeling like special units and start feeling like dependable infrastructure.