CBCastle Busters
Command Archive

Field manual · September 10, 2026

Castle Busters Frontline and Backline: Hero Placement Conditions

Check Sir Rally, Leif, and Wolfie's documented neighbor and row conditions, plus the dated unit-swap fix and placement limits.

Commander's short order

Patch 1.16 gives relationships, not universal front or back slots: Sir Rally affects allies immediately around him; Leif revives fallen allies in his row after his own enemy-unit kill; Wolfie responds when a neighboring ally dies. Patch 1.17 separately reports a swap-placement fix.

Castle Busters logo
Castle Busters official logo; identification only, not evidence of unit placement.
01

Field order

Check the named relationship before a front or back label

Patch 1.16 names relationships and triggers, not fixed slots. It was not reproduced in a current client here; around and neighboring do not define reach or grid geometry.

Check the named relationship before a front or back label
HeroPublished conditionBoundary
Sir RallyHe boosts the damage dealt by allied heroes immediately around himPatch 1.16; no diagonal rule or multiplier inferred
LeifAfter he kills an enemy unit, fallen allies in his row reviveBoth his kill and the same-row relationship matter
WolfieAfter a neighboring ally dies, he transforms and gains attack strengthNot a front-row or enemy-death rule
02

Field order

Treat the swap fix as a dated release note

Patch 1.17 reports fixing placement after swaps. This dated statement does not prove current deployment everywhere or that every older recording showed the problem.

If an old clip and the live client disagree, record the version and positions. Keep the difference as an observation until matching evidence explains it.

03

Field order

Keep a position check small

1. Confirm the relevant hero is available and note the relationship named in the table.

2. Save the visible version and starting positions.

3. Move one unit, then compare only what the screen shows. This makes the observation easier to read; it does not promise activation or better defense.

4. Leave adjacency geometry, aiming, damage, and a complete formation unknown without separate evidence.

Use the related formation, unit, access, and patch guides for narrower source-backed details.

†

Records

Sources