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 pacing

Coming soon

Sleep until the account needs you.

A global next-wake decision built from every village and durable account-level job.

Operational brief

Useful Kingdoms work is scattered across villages and account helpers. A construction slot may open in one village before a hero check is due elsewhere; a failed navigation may need backoff while another village is ready now. Smart Sleep combines those durable due times into one chronological next-wake decision.

The objective is natural pacing and bounded work, not artificial activity for its own sake. Each group receives explicit time, visit and verified-mutation ceilings. When nothing useful is due, the browser can rest instead of looping on the last page it happened to visit.

Decision
Account-wide
Work style
Bounded
Recovery
Serialized
TBot2 Kingdoms automation ledger showing next-run times and Smart Sleep scheduling
Durable village and account jobs feed one next-wake decision, with visible schedules rather than a continuous refresh loop.
01

One chronological decision

TBot combines scoped village events and durable account jobs into one next-wake decision. The last village visited cannot hide an earlier deadline elsewhere in the account.

  • All-village deadline aggregation
  • Account-job due times
  • Order-invariant decision
  • No zero-sleep loop
02

Hard budgets protect the account

Each Kingdoms group has explicit time, navigation and verified-mutation ceilings. Cleanup is separately bounded so one difficult page cannot monopolize the browser.

  • 90-second group bound
  • Configured visit ceiling
  • Verified mutation ceiling
  • Bounded cleanup restoration
03

Recovery has one owner

Login, lobby and world-entry recovery are durable account work. Non-cooperative startup tasks remain owned until they actually stop, preventing overlapping browser control.

  • Login and lobby guidance
  • World-entry recovery
  • Browser offline recovery
  • Serialized page ownership

The operating loop

From live state to a proven result.

01

Collect every due time

Village-scoped work and account helpers contribute their next useful deadline to the same decision.

02

Apply backoff and budgets

Temporary navigation failures and configured group limits prevent a difficult surface from creating a hot loop.

03

Choose the earliest useful wake

The scheduler selects chronologically across the account, independent of which village happened to run last.

04

Recover with one owner

Login, lobby, world entry and browser recovery remain serialized so two startup paths do not compete for the same page.

Pacing is observable, not mysterious

Smart Sleep exposes why the next run is scheduled and keeps hard limits around each work group. It is a runtime control—not a claim that automation is undetectable or risk-free.

  • See the next useful account wake
  • Include both village and account jobs
  • Back off from temporarily broken navigation
  • Cap visits, time and verified mutations per cycle
  • Pause work and retain durable schedules

Before you enable it

Questions worth answering.

Does Smart Sleep keep the browser active all the time?

No. It calculates when useful work is next due and avoids a zero-delay refresh loop when the account has nothing eligible to do.

Can one broken village stop the account?

The scheduler can apply failed-village backoff and bounded work, allowing other eligible villages to receive service in later decisions.

Does natural pacing eliminate all account risk?

No. TBot does not guarantee undetectability or account safety. Users remain responsible for how they use third-party software and for following applicable game rules.

Coming soon

One key. Legends now, Kingdoms soon.

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