Tribal Wars Bot / How it works
How it works
Your empire, up and running.
Download Tribal Wars Bot, connect your game, then start the free trial when the player shown by Tribal Wars has been recognized.
- 1 · Open setup
- Download and open the Windows installer. Create your Tribal Wars Bot account in setup, or sign in if you already have one. Verify your email; setup continues automatically with no licence key to copy.
- 2 · Connect your world
- Paste the address from your open game world, or enter a code such as en157 or de259. Open the dashboard and press Start bot. Sign in to Tribal Wars in the game window.
- 3 · Start the trial
- Once your player is recognized, press Start my 7-day free trial in the setup window. Choose the features you want in the dashboard. Downloading and creating an account do not use up your free days.
- Setup
- One guided installer for 64-bit Windows 10 or 11 and Google Chrome.
- Free trial
- 100% free for 7 days. No credit card; all available features are included.
- Afterward
- $29.99 USD in Bitcoin adds 30 days. It does not renew automatically.
- While it runs
- Keep the PC awake and the bot's Chrome window open.
The parts
Three pieces, two of them on your PC
Nothing here is a virtual machine, a container, or a bundled browser. It uses the Chrome already installed on your Windows PC.
The extension
A Chrome extension, installed into a separate profile on your normal Chrome by a policy the setup program writes. It reads the game screen you are on, carries out what has been decided, and draws the control panel in the corner of the page.
The helper
A small program on your PC. It holds your settings, serves the dashboard at 127.0.0.1:17323, keeps the log, and connects the extension to the operating system.
The server
Ours. It answers the question "what should this village do next" and serves the updates. The copy of the bot that installs from this site does not contain the decision code at all — it asks, and carries out the answer. You cannot copy an algorithm that was never sent to you, and that is the point of the arrangement.
One pass
What happens between two clicks
The numbers are the order it actually goes in. It repeats a few times a minute, per village, for as long as the window is open.
Read the screen
The extension reads the page you are already on — resources, queues, troops at home, countdowns — the same numbers you would read yourself.
Ask what to do
Those facts go to the server, which answers with a decision and how long it stays good for. Answers are fetched ahead of time and held, so no request is ever waiting when something is about to be sent.
Check again, at the last instant
A decision made two seconds ago rides facts that are two seconds old. So immediately before anything is sent, the live page is re-read and the action is dropped if the world moved — troops left, resources went, the target changed.
Do it in the page
Ordinary actions are carried out inside the game page in Tribal Wars Bot's separate Chrome profile.
Pause when the game needs you
If the game asks for your attention, Tribal Wars Bot pauses rather than guessing or pushing through. The dashboard tells you what needs attention.
Write it down, set the next time
The action goes into the log with what it was and why, and the village gets its next due time. The scheduler then goes wherever the next job is due — this village, another one, or another world.
Detection
What we can honestly claim
Nobody selling a bot can promise you it will not be caught. Here is exactly what this design does and does not buy you.
The browser is genuine. There is no user-agent switching, no platform or client-hint rewriting, no WebGL trickery. It is a real Windows Chrome reporting real values, on a real machine, with a real graphics card behind it. Spoofing is what produces the mismatches that get noticed; the absence of spoofing is the feature.
Checks stop the run. If the game asks for your attention, the bot pauses and surfaces that state instead of trying to conceal or bypass it.
It paces itself, and it can be told to stop. Every module's interval carries jitter, so the same job does not land on a metronome. Two further settings exist because "this account never pauses" is a shape a human reviewer can see: a daily rest window, and short step-away breaks through the day. Both are off unless you switch them on, because both cost throughput and that is your trade to make, not ours.
Overdue work is never delayed to look human. Jitter sits inside a module's own interval. A job that is already late is done in the order it came due — an artificial wait on overdue work makes the bot worse and does not make it look better.
And the part we will not dress up: automation breaks the Tribal Wars rules. The design is conservative, but no automation can promise that an account will never be detected.
Compared with a userscript
Why not Tampermonkey
Userscripts are how most Tribal Wars automation is done, and for planning tools they work well — we run one ourselves. As the whole bot, they run into four walls.
- A userscript has no companion process. It runs only inside the page and stops when that page stops. The same question, answered shorter →
- Someone has to be there. A script manager gives you a button; it does not decide when the next scavenging run is due in your eleventh village at 04:00.
- You maintain it. Pasting, updating, re-pasting after a wipe, and finding out from a broken account that a script went stale. Tribal Wars Bot's launcher installs its own updates when it starts.
- The whole thing is in the file. Every algorithm in a userscript is readable by anyone who opens it — including whoever is looking for one to block.
We do still use one. FarmGod, Warre's farm planner, is loaded from our own mirror to lay out farm runs, and the community mass-scavenge script does the same job for scavenging. They plan; Tribal Wars Bot presses. How we run FarmGod →
Your machine
What setup changes, and what stops it
Setup does change your PC, and we would rather say so than call it portable. It writes a Chrome policy so the extension installs, creates a browser profile folder for the bot, and installs the helper — which is also what puts each new build in place, on the launch after we publish it. The uninstaller removes the policy, profile and helper that setup installed.
Your everyday Chrome is untouched. The bot gets its own profile, so your browsing, logins and cookies are not shared with it and not visible to it.
When the PC sleeps, the bot sleeps. This is software on your computer driving a browser window: no machine, no bot. When you wake it, the bot picks up and works the overdue jobs in the order they came due. If you want it playing overnight, the machine has to stay awake — and the window it opened has to stay open.
When our server cannot be reached, it waits. The build you download asks the server for its decisions, so if the connection is gone it retries rather than guessing. A parked bot is a bad evening; a bot acting on a guess is a lost account.
That arrangement is recent, and the builds that moved each decision across are dated on the changelog. What each module decides once it has an answer is on the module list.
Read next