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 robber intel

Coming soon

See the hideout clearly before you send.

Read-only robber-hideout intelligence and manual attack planning, with honest boundaries around automated sending.

Operational brief

Robber Hideouts and Robber Camps are not interchangeable. Hideouts are personal targets, while camps are shared kingdom challenges. TBot’s current Kingdoms support concentrates on reading visible hideout information and making manual planning clearer; it does not advertise unattended raid sending as released.

That boundary matters because sending troops is not safely represented by a click alone. A production workflow would need a persistent target identity, troop reservations, confirmation proof and outgoing-movement reconciliation. Those safeguards remain roadmap work, so the current page labels the available intelligence and the planned sender separately.

Launch status
Coming soon
Target
Hideouts
Auto sending
Planned
TBot2 Kingdoms command center used to review villages before manual robber hideout planning
Village readiness and troop context belong in the wider command center; automatic hideout dispatch is not presented as a released capability.
01

Hideouts are personal targets

Robber Hideouts are personal PvE targets that appear near eligible players’ villages. They are different from shared Robber Camps, and the product copy keeps that distinction explicit.

  • Visible target context
  • Inbound and outbound report direction
  • Target and source village details
  • Report-level summaries
02

Useful intelligence, no pretend automation

TBot can summarize visible hideout reports and send-form context, including available and prefilled troop information. The current planner remains read-only and never labels a manual form as safe for unattended sending.

  • Read-only report parsing
  • Available troop context
  • Manual-plan requirement
  • No automatic dispatch claim
03

Verified sends are planned

Persistent target ledgers, troop reservations and two-phase verified submissions remain roadmap work. They will move to beta only after duplicate-send and ambiguous-timeout cases are proven safe.

  • Target ledger
  • Troop reservation
  • Confirmation verification
  • Outgoing-movement reconciliation

The operating loop

From live state to a proven result.

01

Identify the target type

The interface keeps personal Robber Hideouts distinct from shared Robber Camps to avoid misleading strategy and product claims.

02

Read visible evidence

Available reports, source and target context, and visible send-form troop information can support a manual decision.

03

Keep dispatch manual

The currently released planner does not convert an inspected form into an unattended attack.

04

Advance only with verification

Automatic sending remains planned until duplicate-send, timeout, reservation and movement-proof cases meet the production boundary.

An honest line between intelligence and action

This feature is useful today because it organizes visible information. Its limitations are prominent so visitors do not confuse planning assistance with a verified raid system.

  • Inspect visible hideout report context
  • Review available or prefilled troop information
  • Keep the final plan and send under player control
  • Distinguish hideouts from kingdom-wide camps
  • Track future sender status in the release ledger

Before you enable it

Questions worth answering.

Does TBot automatically attack Robber Hideouts?

No. Current support is read-only intelligence and manual planning. Verified unattended sending remains planned.

Are Robber Hideouts the same as Robber Camps?

No. Hideouts are personal PvE targets; camps are shared kingdom challenges. The related guide explains the practical distinction and links to official references.

Why not automate the final send now?

A safe sender needs more than form interaction: persistent target identity, troop reservation, confirmation proof and outgoing-movement reconciliation must handle retries and ambiguous timeouts.

Coming soon

One key. Legends now, Kingdoms soon.

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