Data Tool Decision Table · UPDATED SEPTEMBER 4, 2026
Castle Busters Units, Skills, and Roles Database
A versioned Castle Busters unit index organized by role, placement behavior, evidence status, and practical substitution—not unsupported tier scores.
Use the database as a versioned role index, not a fake power ranking. The first verified set contains only units and behaviors explicitly named by official pages; every missing stat stays unknown.
Quick answer and scope
Use the database as a versioned role index, not a fake power ranking. The first verified set contains only units and behaviors explicitly named by official pages; every missing stat stays unknown. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
This page is for one task: solve the player task described by Castle Busters Units, Skills, and Roles Database It applies to the version checked on September 4, 2026. If the current screen differs, stop at the first mismatch and use the troubleshooting section instead of forcing the route. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
What the accepted sources actually prove
The official site describes real-time 1v1 battles, more than 30 units, squads of up to eight, movable castles, structures, wheels, helper items, and upgrades through multiple material tiers. Patch 1.16 adds three placement-sensitive heroes; patch 1.17 changes matchmaking, support access, upgrade behavior, and several combat or interface bugs. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
That evidence supports the game's identity and the named systems, but it does not make every neighboring value true. Official sources do not publish every unit stat or a universal tier list. Community posts prove that upgrade, synergy, and placement questions exist, but their recommendations remain player observations until corroborated. This page keeps that boundary visible so an unknown field cannot silently become a confident recommendation. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
The verified dataset for this task
This page adds a bounded verified dataset, a current-version evidence boundary, and a recovery path for Castle Busters Units, Skills, and Roles Database. It is designed to answer the named task without importing unsupported details from a similar game or an older build. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
Use the verified dataset as a decision aid, not as decoration. Read the required input, choose the next action, note the expected visible output, and keep the fallback beside it. If any required input is unknown, the safe action is to gather that evidence before spending currency or committing progress. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
Run the route without mixing variables
Start by naming the current bottleneck in one sentence. Then follow this bounded answer: Use the database as a versioned role index, not a fake power ranking. The first verified set contains only units and behaviors explicitly named by official pages; every missing stat stays unknown. Change only the element, item, unit position, ship choice, or progression action directly tied to that bottleneck. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
After the action, return to the same screen or encounter and compare the result. A successful outcome without a stable baseline is useful for play but weak as evidence. A failed outcome with a clean baseline is valuable because it tells the next player which assumption not to repeat. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
Decision table
Use four columns: current state, available choice, expected benefit, and stop condition. Current state must come from the live game. Available choice must be visible or explicitly documented. Expected benefit may be a hypothesis, but it must be labelled as one. Stop condition prevents an open-ended upgrade or experiment from consuming resources without solving the original task. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
Verify identity and system boundaries with the cited first-party source, then confirm version-sensitive conditions in the current client or with two independent current sources. A repeatable current observation may be labelled verified. One clean observation is partial. A missing label, result, or repeat remains unknown; none of those states should be converted into zero. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
What belongs in a trustworthy unit row
Each row needs an exact displayed name, current availability, primary role, placement dependency, visible skill behavior, source, version date, and evidence state. Numeric attack or health fields stay blank when the accepted sources do not publish them and the current client has not been measured. Blank means unknown, not zero. This distinction prevents filters and comparisons from turning missing data into a false weakness.
Role labels should describe what a player can observe: protects a firing line, deals repeatable damage, pressures a lane, controls movement, supports another unit, or depends on a specific row, column, or neighbor. A unit may carry more than one label, but the database should mark which behavior justified each one. Rarity alone is not a role and does not prove performance.
Handle patch 1.16 examples without overclaiming
The official patch page names Crabbo, Pharaoh, and ZapZap and describes behaviors tied to frontline attacks, a cat row, and a unit directly in front. Those statements justify placement tags and a patch reference. They do not justify exact damage values, a global ranking, or a claim that the heroes work identically after later balance changes. The database should display the official wording as a bounded behavior summary and schedule a current-client check.
When a named unit cannot be found in the live roster, mark availability unconfirmed for the current account or build. Do not delete the patch record. Limited access, progression gates, platform rollout, or later removal can all explain the mismatch. Preserving the dated official record lets the site show what changed once a second source or client capture resolves it.
Search and compare by job to be done
Players usually need a substitute, not an abstract list. Filters should answer questions such as which available unit can protect this damage source, which option can pressure an uncovered lane, or which behavior still works when a placement slot is unavailable. The comparison view should show shared role, different condition, upgrade burden, and the evidence behind the match.
A substitute is acceptable when it preserves the required function under the current formation. It does not need the same name, rarity, or animation. Conversely, two units with similar visual attacks may not substitute if one relies on a row or adjacency rule the formation cannot support. This makes the database useful even before every numeric field is known.
Database maintenance rules
Every change should be append-only at the evidence layer: retain the old value, record the new observation, attach the patch or capture date, and update the current view only after conflict resolution. Two independent current observations or one explicit official statement can promote a behavior to verified. A community recommendation may open a research task but should not directly rewrite a unit field.
Completeness is measured against a declared roster snapshot, not the marketing phrase 'more than 30 units.' Until the current client roster is captured, the page must call itself a verified partial index. Publish coverage counts by evidence state and surface missing fields as research needs. That honesty is more actionable than a false 100 percent badge.
Final verification checklist
Confirm the exact game, platform, current version, task, prerequisite, chosen action, expected visible result, recovery option, and evidence state. If all nine are clear, execute the smallest useful action. If one is missing, collect it before committing a scarce resource. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.
The short rule remains: Use the database as a versioned role index, not a fake power ranking. The first verified set contains only units and behaviors explicitly named by official pages; every missing stat stays unknown. Verify the visible result, save the date, and leave unsupported precision unknown. This claim is scoped specifically to Castle Busters Units, Skills, and Roles Database.