TrvBot user guide

TrvBot is a Windows desktop app for one game account. The website manages your subscription; the desktop app manages your villages. Its controls are in English.

1. Extract the Windows package to a folder, then open TrvBot.exe. Close any older copy first. You do not need to install Python for the EXE release.
2. Enter the license key supplied by your provider and select Activate. An internet connection is required at startup and while using the app.
3. Open Account settings, enter your game account details, and select Save account.
4. Select Find villages. Open a village, review its settings, and add your development steps.
5. Enable the village, save its changes, then choose Account options → Activate account to begin automatic operation.

Activating your license unlocks the app. Activate account starts game automation. These are separate actions.

Use Account settings for both initial setup and later edits.

1. Account name is the label shown in TrvBot. Game server URL (HTTPS) is the address of your game world.
2. Enter the Username and Password used to sign in to that world, then select Save account.
3. When editing an existing account, leave Password empty to keep the saved password.
4. In Account options → Browser, choose Automatic to use installed Google Chrome or Microsoft Edge when Chrome is unavailable. You can also select either browser directly. One of them must be installed; TrvBot uses a separate game profile.
5. After changing the browser, pause the account and activate it again to reconnect.

Your website login, game login, and license key have different purposes. Enter game credentials only in Account settings.

The home page lists your villages. Select Open beside a village to work with that village only.

1. Use Find villages to discover your villages. Search by name or ID, or use the village filter. Select all shown follows the current search and filter.
2. In the village window, Enable this village allows automatic work for that village. The account must also be active.
3. With Use general settings checked, the village inherits shared defaults from Settings. Uncheck it to use the village’s own Settings tab; its private values are preserved when you switch sources.
4. Development queues and manual farming targets always belong to their own village, even when general settings are selected.
5. Use Save changes for village edits and Save general settings for shared defaults. Valid edits to an active village also save automatically after a short pause; an invalid value must be corrected.

Pausing the account stops automatic work for all its villages. Disabling one village leaves the other enabled villages available for automation.

The app collects supported information from game pages it visits and keeps a local copy for each village.

1. On a village’s first complete resource observation, the app saves field positions and types. Later observations update levels without assuming a standard layout, including for 9- and 15-crop villages.
2. Overview shows resources, capacity, tribe, Travian Plus and observation information. Building names and levels are updated when relevant pages are observed.
3. Saved inventory can appear immediately after reopening the app. It is cached information; Last refresh indicates the last observation.
4. Construction information shows ongoing upgrades and their remaining time. Incoming shows movement types and arrival times; movement counts are not the number of soldiers.
5. Countdowns update locally. A timer reaching zero does not itself confirm completion; the next scheduled observation confirms the game state.

Unknown or Not refreshed means the app has not confirmed that value. It does not mean zero resources, zero health, or no incoming troops.

Open the village’s Development tab. The table shows each target, its current and target levels, status, priority and order.

1. Choose Add fields in bulk. Select multiple fields, or use All, None, Wood, Clay, Iron or Crop. Set Target level and Priority, then add the selected fields.
2. Field names and type buttons become available automatically when a complete observation arrives. Keep the browser’s current task free to finish if the field list is still waiting for data.
3. For a building, choose Add building and select an observed slot. An occupied slot upgrades that building; an empty site lets you choose the building to construct there.
4. The app checks resources, prerequisites and construction capacity. A confirmed unavailable new building can be deferred while other queue entries are considered.
5. Save the queue and enable automatic development. With the village enabled and the account active, you do not need to press start for every upgrade.
6. Select rows with the checkboxes to edit their priority or delete them. Saved plans can be reused with Load plan into queue.

Deleting a local queue item does not cancel an upgrade already accepted in the game. An uncertain submission stays pending verification instead of being clicked repeatedly.

Normal queue operation gives each eligible item one upgrade per round, then returns to the start of the round.

1. Priorities run High → Medium → Normal → Low. Set priority changes selected rows; the table rearranges accordingly.
2. Move up and Move down change saved order within the same priority. Priority changes apply at a task boundary, without interrupting an action already running.
3. Example: Wood target 5, Clay target 5 and Warehouse target 7 each receive one upgrade in the round when eligible, then the cycle repeats.
4. Check Force to target to keep an item’s turn until its target is reached or its final upgrade is accepted. It still waits for resources, prerequisites and a free construction slot.
5. Resources → Upgrade affordable fields allows an eligible later field to be considered when an ordinary field is short of resources. A forced item keeps waiting for its own requirements.
6. An item leaves the queue once the game confirms its final target upgrade has started. A building at level 2 with target 3 therefore leaves the plan when the upgrade to 3 starts; the ongoing construction remains visible.

Romans can use a resource-field lane and a building lane when detected capacity allows. Tribe and Plus are detected automatically; Force to target and unconfirmed submissions can still block another action.

Open Training in the village window. Edit training settings opens the settings source currently used by that village.

1. Enable training, choose the Training type, specify the Unit name and Troops per batch, and set Keep each resource in reserve. An empty unit name uses the first available unit.
2. Use Train once for one training task or Repeat training for repeated tasks. The account’s automatic operation also follows enabled training settings.
3. For settlers, select Settlers — auto-detect Residence / Palace. The app locates the village’s Residence or Palace automatically.
4. Set Settlers per batch (up to) between 1 and 3. The actual number still depends on the building, available resources and the game’s expansion requirements.
5. To cover a settler shortage, enable Use hero resources only when settler training is short and set the hero inventory reserve.

The settler option withdraws only the shortage needed for settler training. Hero → Resources is a separate option for filling village storage to a target percentage.

Open Settings → Hero in the general settings or the village’s private settings, then enable Enable hero automation. The Hero tab in the village window displays observed inventory.

1. Care: enable Send on adventures and set Minimum adventure health (%). Optionally configure ointments, a healing target, an ointment reserve and a revival policy.
2. Attributes: choose how free points are allocated, hero resource production, and whether the hero hides or defends. Automatic Book of Wisdom use requires an allocation policy.
3. Equipment: enable filling empty slots, and set the number of bandages or cages to keep equipped. Existing occupied equipment slots are left unchanged.
4. Items: choose scrolls and artworks per hero turn; zero disables their use. Tablets can be used while the village’s loyalty is below 100%.
5. Resources: enable Withdraw stored hero resources automatically, choose Fill village storage to (%), and set an inventory reserve.
6. Save before activating the account. Keep the same attribute policy across enabled villages when automatic Book of Wisdom use is enabled, since the hero is shared.

Hero tasks confirm one logical operation per turn, then return to the first village. Adventures wait if an earlier hero action is needed, health is unknown or too low, or the hero is unavailable. Appearance, auctions and crafting remain manual.

Settings → Task rewards controls automatic collection of earned rewards.

1. Enable Collect flagged task and daily rewards automatically.
2. Choose whether to include general task rewards, and set Maximum rewards per turn from 1 to 20; the default is 10.
3. Save the settings and activate the account. The collector checks flags on observed game pages before opening the relevant reward screen.
4. Each claim is checked before the next reward is collected. The app returns to the first village after the batch.

No reward flag normally means no visit to the reward screen. An earlier unconfirmed claim may require a verification visit. Unfinished tasks and already collected rewards are skipped.

Account options controls the base refresh interval and the additional random percentage.

1. Set Base refresh interval in seconds. For example, 300 seconds means five minutes.
2. Set Random extra delay with From % and To %. The next interval is base × (1 + selected percentage ÷ 100).
3. Example: a 300-second base and a selected 32% produces 396 seconds, or 6 minutes 36 seconds.
4. A new percentage is drawn after each village refresh. Each calculation starts from the base interval, so the delay does not grow cumulatively. Set both percentages to zero for the base interval alone.
5. Settings → Timing controls delays between actions and farming repeat intervals separately.

A refresh interval controls scheduled observations, not every navigation. Executing a game action, switching villages or returning to the first village still requires navigation. Busy tasks or sleep can postpone a refresh.

Open Account options → Sleep mode. Sleep settings apply to the entire game account and use your computer’s local time.

1. Choose the sleep mode and its values, then Save.
2. At sleep time, the current bounded task finishes and returns to the first village. The app attempts to log out and closes the game browser.
3. Keep the desktop app open if you want it to wake automatically. At wake-up it reconnects and resumes eligible work.
4. To resume early, change Sleep mode to Off and save.

During sleep, no game actions or page refreshes run. The desktop stays open to track wake-up time and maintain license checks. If logout cannot be confirmed, the browser still closes and the status reports it.

The village’s Tasks tab lets you select a task, run it once, repeat it, or stop it. The task table shows its state, next check, result and error.

1. Run once performs one task run; Repeat schedules it repeatedly. Stop task affects the selected task. Stop this village stops its work, and Clear waiting tasks removes pending tasks.
2. For saved game farm lists, enable Farming and enter Farm list numbers. Number 0 means the first list; leave the value empty when no list should be selected.
3. For manual farming, open Farming and enter one destination per line as troop counts | X | Y. Example: 5,0,0 | 10 | -20 sends the first listed troop type to those coordinates. Troop order follows the rally point.
4. Celebrations lets you choose Small or Great. Monitoring controls the check interval and storage alert threshold.
5. Protection settings include a safe destination, reaction thresholds and optional troop or hero evacuation. Review these values for the intended village before enabling them.

All enabled tasks follows the selected settings. A task must still meet its game requirements. Automatic paid purchases and NPC exchange are disabled in this release.

The website account and More → Subscription in the desktop app show license information. Each license supports one linked device and one running session.

1. Sign in to the website and open My subscriptions to see your status, expiry, linked device and remaining unlinks.
2. To move the license, close the app on the old device, then choose Unlink device on the website and confirm your website password.
3. Each key has 3 customer unlinks per calendar month. The allowance resets on the first day of the month at 00:00 Saudi time. Unused unlinks do not carry over; the first binding does not consume one.
4. If the previous device still has a valid operating permit, the new device waits for its remaining validity, up to 3 minutes. After that, open the app on the new device, enter the key and select Activate.
5. Unlinking does not change the subscription expiry. Contact your license provider for renewal or when you need help with the monthly allowance.

The one-time 5½-minute rollout message belongs to the transition to the protection system, shared by the whole service. It is not a new wait for every customer and is separate from the up-to-3-minute device transfer wait.

Use More for the supporting tools that do not need to stay on the main screen.

1. More → Activity shows recent task results and errors. Note the village, task and message when investigating a problem.
2. More → Backups provides Back up workspace and Export workspace. Keep a copy before removing local data or making a large change.
3. Backups and exports exclude passwords and license/device secrets. They are not a way to transfer device authorization.
4. Check queue or plan rows to delete selected entries. Select all shown on the village list applies to the current search and filter.
5. Remove account deletes the configured account’s local data after stopping its worker. Removing local villages does not delete them in the game; discovery can add them again.

Deleting a saved plan template does not delete the village’s current development queue. Deleting a queue item does not cancel construction that already started in the game.

Read the status and the latest Activity entry before starting the same task again.

1. Nothing is running: check Account options → Activate account, Enable this village, the relevant task switch, and whether sleep is active.
2. Fields are missing or show Unknown: allow the first complete observation to finish. If a task owns the browser, the read waits for a task boundary. Inspect Activity for a real reading error.
3. Development is waiting: check resources, free construction capacity, building prerequisites, priority and Force to target. An accepted final upgrade disappears from the plan while remaining visible as construction.
4. The hero is not adventuring: check Send on adventures, the minimum health, whether the hero is at home, adventure availability, and whether another hero operation is pending.
5. License already in use: close the other copy. Linked to another device: use the website’s Unlink device procedure. Expired or disabled: contact the license provider.
6. Device verification or connection error: use version 0.2.1 or later and retry with internet access. Version 0.2.1 corrects request timing from the server if the computer clock differs. If it persists, keep the full message for support.

A waiting or unconfirmed task is not proof that an action failed. Check its result before retrying so you do not request the same action twice.