Robber Hideouts vs Robber Camps

Robber Hideouts appear as personal targets for eligible players. Their reports and attack context belong to that player’s account rather than becoming a shared kingdom objective.

Because hideouts are personal, visible target and report information can support an individual village decision. TBot currently focuses on reading that information and helping the user plan manually.

Robber Camps are a different mechanic: members of a kingdom cooperate against a shared challenge. Advice written for a personal hideout should not automatically be applied to a camp.

The distinction also matters for search visitors. A page claiming generic ‘robber automation’ without naming the target type hides important mechanical and product limitations.

Released support can summarize visible Robber Hideout report context and information exposed in the send form, including source, target and available or prefilled troop details where present.

This is read-only intelligence. It can reduce the work needed to understand a target, but the attack plan and final dispatch remain under player control.

A reliable sender needs durable target identity, troop reservation, confirmation proof and outgoing-movement reconciliation. It must also handle the case where the browser times out after the game accepted a send.

Until duplicate-send and ambiguous-timeout cases meet that verification boundary, TBot does not label unattended hideout sending as available. Follow the release ledger for status changes rather than relying on this guide alone.