Kingdoms construction
Coming soonA Kingdoms-native planner for resource fields, buildings, new locations and explicit execution policies.
Operational brief
Travian Kingdoms construction is more than choosing the next building. The active village, available resources, open construction slots, prerequisites and the page’s current state all have to agree before an upgrade makes sense. TBot keeps those live facts separate from the plan you created, so you can see what Kingdoms has accepted and what still waits in the backlog.
This preview is designed for players who want repeatable village growth without turning their strategy over to a black box. You choose the work and its policy; the coming Kingdoms engine is built to handle the repetitive observation, navigation and verification around it.
TBot keeps the construction already accepted by Kingdoms separate from the backlog you want TBot to execute. That makes the next action, blockers and receipts understandable instead of blending intent with game state.
Before an irreversible action, TBot revalidates the selected account, village, route, location and plan revision. Afterward it looks for an exact queue, level or resource transition. Uncertain outcomes are reconciled before retrying.
Cost forecasting, resource-ready ETAs, dependency insertion and strategic Auto Build profiles are in active roadmap work. They are not presented as released until they pass the same verification boundary.
The operating loop
TBot refreshes the selected village, resource balances, construction surface and available locations before evaluating planned work.
The planner respects your ordered backlog and village policy, then rejects items whose visible prerequisites or context do not match.
Account, world, village, route, location and plan revision are checked again at the last responsible moment.
A queue, level or resource transition must be visible before progress is recorded. An uncertain result is reconciled instead of blindly repeated.
Automation should preserve the player’s decisions. The planner therefore exposes the backlog and execution policy instead of silently improvising a village strategy.
Before you enable it
Not in the current release. You define the planned work and policy. Strategic Auto Build profiles, dependency insertion and broader cost forecasting remain roadmap items.
The item remains visible as blocked or waiting. TBot does not treat a failed click as a successful build, and it can revisit the work in a later bounded cycle.
Yes. Planned construction and execution preferences are scoped to the Kingdoms village while the account scheduler coordinates when each village receives service.
The sessions in your existing TBot2 plan will cover Kingdoms at launch.
