Field manual · September 10, 2026
Castle Busters Arena Checklist: Matchmaking and Counter Limits
See what Castle Busters patch 1.17 actually says about matchmaking and bots, then record one match without inventing a universal counter.
Patch 1.17 announced a matchmaking experiment without publishing its formula and reported fixing bots that left the map edge. Those notes do not identify every opponent or prove a universal counter, so record the visible matchup, one change and the result before drawing a conclusion.
Field order
What patch 1.17 actually says about opponents
The September 1, 2026 patch notes say a new matchmaking approach was being tested. They do not publish the formula, its factors or whether that experiment remains active in the current client.
The same patch reports fixing bots that could leave the edge of the map. That confirms a bot-related fix in the dated patch; it does not say bots were removed, reveal the share of bot matches or provide a way to identify an opponent.
| Official patch note | What it does not establish |
|---|---|
| A revised matchmaking approach was being tested | The formula, weights or current deployment status |
| Bots leaving the map edge were reported fixed | That all opponents are human or bots were removed |
Field order
Keep a short record before calling something a counter
Start with what the match actually shows. Record the displayed version if available, the units and layout you can see, the first decisive event and the final result. Leave player-or-bot status unknown unless the client explicitly identifies it.
For the next comparable match, make one visible loadout or placement change if the client offers it. Write down the action separately from the result. This is an observation method, not a claim that the change counters a named opponent.
| Record | Use | Keep unknown |
|---|---|---|
| Version and visible matchup | Bind the observation to one client state | Hidden matchmaking factors |
| One visible change | Compare it with the baseline match | A universal counter |
| First decisive event and result | Describe what changed | Win rate or opponent type |
Field order
Keep the counter claim narrow
One favorable match cannot establish a universal counter or a matchmaking rule. A repeat under the same visible version and a comparable matchup can strengthen a limited observation, while the formula and hidden opponent data remain unknown.
Use the related guides for their separately documented patch, formation, unit and helper-item facts. A named arena counter still needs a current matchup, a specific change and a repeatable result before it belongs on this page.
Records