TBot2
Kingdoms · Coming soonPreview the new engine while final launch verification is completed.
Included with the same TBot2 key at launch
All Kingdoms features

Kingdoms hero

Coming soon

Adventure timing without village duplication.

TBot treats the hero as account-level work and coordinates due checks through the Kingdoms scheduler.

Operational brief

Your hero belongs to the Kingdoms account, not to every village the scheduler visits. Treating adventures as village work would repeat checks, waste navigation and create conflicting due times. TBot instead represents hero adventure work once at account scope and hosts it in a suitable village context when it becomes due.

Hero support remains a launch preview. The scheduling and execution boundaries are defined while broader policy choices and the complete hero state surface continue through production verification.

Job scope
Account
Launch status
Coming soon
Timing
Durable
TBot2 Kingdoms automation ledger showing scheduled account and village jobs
Hero work appears alongside other durable Kingdoms jobs, with a due time and outcome instead of a repeated check in every village.
01

One hero, one account job

Hero work should not run once for every visited village. TBot stores a durable account-scoped due time and hosts the job in an eligible village context when it is actually useful.

  • Account-scoped scheduling
  • Eligible village hosting
  • Durable due time
  • No per-village retry storm
02

Verified outcomes

A completed interaction is not automatically a completed adventure action. TBot distinguishes terminal outcomes, operational failures and uncertain submissions so it can recover without blind duplication.

  • Live preconditions
  • Bounded interaction
  • Typed outcomes
  • Uncertainty reconciliation
03

Release status matters

The helper and scheduling foundation is in beta while the full hero state machine and broader adventure policy set continue through production hardening.

  • Clear beta labeling
  • No unsupported health claims
  • Changelog-backed releases
  • Roadmap transparency

The operating loop

From live state to a proven result.

01

Store one due time

Adventure availability is scheduled as account work, avoiding one copy of the same task for every configured village.

02

Wait for useful timing

Smart Sleep can include the hero job in its chronological next-wake decision instead of continuously polling the page.

03

Acquire valid context

An eligible village and serialized browser ownership provide a coherent surface for the live adventure check.

04

Record a typed outcome

Success, a terminal game state, an operational failure and an uncertain submission remain different results with different recovery behavior.

Timing support, without pretending every decision is automatic

The planned launch workflow focuses on durable scheduling and verified outcomes. Players will remain responsible for account strategy, equipment, health decisions and reviewing automation behavior.

  • Enable or pause the account-level helper
  • See when the next check is due
  • Avoid per-village duplicate work
  • Keep failures visible for review
  • Follow release-ledger status as policies expand

Before you enable it

Questions worth answering.

Does TBot run an adventure check in every village?

No. Hero adventure timing is represented once for the Kingdoms account and is hosted only when the job is due.

Is hero adventure automation fully released?

No. It is coming soon with the rest of the Kingdoms engine while broader policies and the complete state machine are hardened.

Does TBot guarantee an adventure is risk-free?

No. Players should review hero health, equipment, travel conditions and current game state. No third-party tool can guarantee account safety or a particular outcome.

Coming soon

One key. Legends now, Kingdoms soon.

The sessions in your existing TBot2 plan will cover Kingdoms at launch.