TBot2 Kingdoms field note
Travian Kingdoms quests and reward timing
A reward is not just a button. It can change the village state that the next automation decision depends on.
Key takeaways
- Daily and village quest jobs stay distinct
- Active-village context may affect the reward recipient
- Completion requires live evidence
- Potentially changed state is refreshed after a claim
Why claim timing matters
Travian Kingdoms allows completed quest rewards to be collected immediately or saved for a later moment. That choice can be strategic when resources, storage or a particular village plan matter.
Some reward effects depend on the village active at claim time. For automation, selected-village context is therefore a precondition, not decorative information in the header.
A village-aware claim loop
TBot keeps daily-reward and village-quest work in separate durable ledgers. When a job becomes due, the engine acquires a coherent Kingdoms village context before inspecting the live reward surface.
The helper can then evaluate the exact visible item, perform bounded interaction and look for disappearance or another typed terminal outcome. A navigation or DOM failure stays an operational error rather than being reported as ‘nothing to do.’
Refresh what the reward changed
Claiming resources can invalidate the balance used by the construction planner. Other rewards may affect buildings, troops or hero observations. Carrying the old snapshot forward could produce the wrong next decision.
The post-claim workflow therefore refreshes the state domains the reward may have changed. This makes the helper part of the same account operating loop as construction and Smart Sleep.
- Resource and storage observations
- Relevant building state
- Troop or hero state when applicable
- Next helper and village due times
Where player choice remains
TBot can reduce routine checks, but it cannot know every strategic reason to save a reward. Pause the relevant helper when you want to choose the recipient or timing manually.
Quest support is currently Beta. Consult the release ledger for the current application status and use the official Kingdoms documentation for game-mechanic rules.
Official game references
Continue with the product
Product and responsibility note
Kingdoms is coming soon and will be included with the standard TBot2 license at launch. All capabilities remain launch previews while production verification continues. Use of third-party software is at the player’s discretion; review the applicable game rules and current release ledger.