Kingdoms operations
Coming soonFair scheduling, exact-village navigation and isolated runtime state for Kingdoms accounts that keep growing.
Operational brief
A growing Kingdoms account creates a scheduling problem: capital work is important, frontier villages still need service, and one broken page must not hold the entire account hostage. TBot’s Kingdoms engine keeps a durable position across configured villages and combines fairness with real deadlines.
The result is a command-center view rather than a stack of unrelated browser tabs. Each village has its own observed resources, live queue, planned work and enablement state. The browser still acts serially—one verified context at a time—while the scheduler decides where useful work is due next.
TBot does not keep returning to the first few villages. Its durable scheduler rotates service across configured villages while still respecting urgent deadlines and navigation affinity.
URL state alone is not enough. TBot requires coherent Kingdoms routing and independent selected-village evidence before a mutation can proceed.
Kingdoms configuration, scheduler state, receipts and logs are separated from Legends workspaces even though access comes from the same TBot license.
The operating loop
The engine observes village identity, resources, queues and helper state without assuming that the last page is still valid.
Due times, readiness, failures and the rotating cursor determine the next eligible village instead of a fixed first-to-last loop.
Kingdoms routing and selected-village evidence must agree before any mutation-capable workflow proceeds.
Receipts, backoff and next-wake timing survive short cycles and restarts, preventing the account from starting from zero each time.
A shared license unlocks both games, but it does not blend accounts, villages or engines. Each workspace remains understandable on its own.
Before you enable it
No. A session represents an open TBot automation workspace, not every village inside that Kingdoms account. Your plan’s session allowance is explained on the pricing page.
No. TBot keeps a rotating durable cursor and considers due work, so the order is not reset to the first village on every cycle.
Yes, within the total concurrent-session allowance of your license. Each workspace selects its own game engine and keeps its data isolated.
The sessions in your existing TBot2 plan will cover Kingdoms at launch.
