Kingdoms rewards
Coming soonQuest-book and daily reward workflows with active-village awareness and verified completion.
Operational brief
Quest rewards look like account-level work, but their effects can depend on the active Kingdoms village. A resource reward claimed in the wrong context can change the wrong snapshot and disrupt the plan that follows. TBot keeps daily and village quest helpers distinct and carries the verified village context through the claim workflow.
The engine also treats a reward as a state-changing event. Resources, buildings, troops or hero observations that may have changed are refreshed rather than reused from before the claim. That makes quest support part of the operating loop, not an isolated auto-clicker.
Kingdoms applies certain rewards to the currently active village. TBot preserves that context and refreshes the state domains a reward can change instead of carrying forward a stale snapshot.
Quest work is represented by durable helper ledgers. The scheduler runs it when due and prevents repeated claims across short cycles, persistence failures and restarts.
Exact reward disappearance or a typed terminal outcome is the authority for completion. Navigation, DOM and click failures stay retryable instead of masquerading as healthy idle work.
The operating loop
Daily rewards and village quest-book work use distinct ledgers because their context and effects are not identical.
The selected Kingdoms village is validated before a claim whose reward may apply to that village.
A durable lease prevents a short scheduler cycle or restart from immediately duplicating the same attempt.
Exact reward disappearance or a terminal outcome closes the job, then potentially changed observations are read again.
TBot coordinates routine claims, but the user still controls whether helper work is enabled and which village strategy should benefit from a saved reward.
Before you enable it
Some rewards affect the village that is active when claimed. TBot therefore treats selected-village evidence as part of the workflow rather than relying on the last URL alone.
The helper uses durable timing and requires live completion evidence. Exact disappearance or a terminal outcome closes the work; ambiguous results are reconciled.
Your game strategy remains your decision. Keep the relevant helper paused when you want to choose the claim timing manually.
The sessions in your existing TBot2 plan will cover Kingdoms at launch.
