Tribal Wars Bot / Changelog
Changelog
What shipped, and when
Version numbers are the extension version — the one the control panel shows at the bottom of the page. Something ships most days; this list carries the changes worth a sentence. New builds go to our own machines first and to everyone else once they have held.
Last updated 2026-09-08
Builds
Recent releases
0.5.971
2026-09-08
- Work that is already due is no longer waited on for a minute before it is done, and a decision no longer costs a log row of its own.
0.5.969
2026-09-08
- The scout gate sends the barbarian map to the server as the few fields the decision needs rather than whole. The payload was 841 KB, which is why those questions were never getting an answer.
- A refusal from the server says which rule refused, and says it once per page load instead of on every pass.
0.5.968
2026-09-08
- A scout task left with no next time reads to the scheduler as due now. It is given one.
0.5.967
2026-09-08
- The other half of the same fault, found first: a scout pass that got no answer stamped nothing, so it came due again fifteen seconds later, and again.
0.5.965
2026-09-07
- A farm cache key that could never match blacked out the whole run. The key carried the clock, so every lookup missed and the pass fell back to doing nothing.
- A service worker still starting up is no longer read as a failed question — it is asked again.
0.5.964
2026-09-07
- The premium exchange's sell pick — which resource, and how much of it — now comes from the server rather than from the copy on your machine.
0.5.963
2026-09-07
- Chrome could close itself after an update. A relaunched browser's only tab decided it was a duplicate of the tab that had just gone away and shut, taking Chrome with it. A tab is only a duplicate now if the other one is still beating.
- The helper's extension repair talks to Chrome over a single connection — a new socket per message was silently dropping the session it had just opened.
0.5.960
2026-09-07
- A defence order can name up to 1,000 target villages. The old cap was 40, which quietly truncated a tribe-sized order.
- The event module no longer tries to flush its queue on page unload without a token.
- "Use all my villages" was a dead control. The checkbox rendered, and the request it sent never carried the flag — so the order ran against the villages you had picked, not all of them. Fixed.
0.5.959
2026-09-07
- Every cached answer from the server survives a page load, so the scout gate stops re-asking about the same targets after each navigation.
0.5.958
2026-09-07
- The scheduler's answer from the server survives a page load, so it stops re-asking the same question on every navigation.
- A village still waiting for its first answer is no longer treated as a village with nothing to do — that mistake sent the rotation hopping between worlds.
0.5.953
2026-09-07
- Farming drops a paused village's rows before the send path instead of pacing them through it and refusing at the end.
0.5.950
2026-09-07
- The published build no longer contains the decision code. It reads the page, asks the server what to do, and carries out the answer.
0.5.946
2026-09-06
- An unpause-everything control, for when a night of manual play is over.
- A sweep for timers that overflowed a 32-bit value — an epoch in milliseconds does not fit in one, and the ones that did not fit went strange.
0.5.932
2026-09-04
- Support follows a noble train that left late, and cancelling a leg no longer suppresses the escort's own cancel.
0.5.930
2026-09-04
- The farm walker respects an operation's troop reserve instead of spending it on barbarians the night before.
- A volley train is sized to the troops actually at home.
0.5.929
2026-09-04
- A volley fires its late noble once the nukes in front of it are away.
0.5.921
2026-09-03
- The operation planner counts noblemen still in production, not only the ones standing at home — it was sizing every plan against half the account.
0.5.918
2026-09-03
- Wave two accounts for the defender's night bonus, which is set per player rather than per world.
0.5.915
2026-09-03
- The Horse Lords event is played like the other seasonal events.
0.5.911
2026-09-01
- The coin funnel got two sets of market routes: standing ones that carry resources into the minting village for good, and a coining run that fills an order and stops.
0.5.902
2026-08-31
- The coin funnel became a module of its own, with its own switch instead of borrowing the account manager's.
0.5.893
2026-08-29
- Recruit pace per unit: a maximum to queue in any rolling hour, per unit type, with 0 meaning no cap. Spear always, light cavalry four an hour.
0.5.892
2026-08-29
- A stronghold is never mistaken for a barbarian village.
0.5.891
2026-08-28
- The premium exchange gained a rule for which villages may sell, and a mode that covers every village on the world.
0.5.889
2026-08-28
- A world that defines its own unit list is taken at its word, so worlds without archers stop being asked about them.
0.5.888
2026-08-28
- The starter recruit package never overwrites one you set yourself.
Why the numbers jump. Not every build reaches everyone. Some go out to our own machines to be watched for a day, and the next number people see is the one that survived that. A build number moving backwards on your panel means a rollback, and it is deliberate. How updates arrive →
Several rows above describe a decision moving from the copy on your machine to our server. That is one change carried out module by module, and how it works explains why the download no longer contains the reasoning. What each module ends up doing is on the module list.
Read next