← Bear Trap Builder

Territory & Bear Trap placement

Use checked templates as a starting point, then recheck coverage after every move, removal or terrain change.

Coverage rules

Facilities require connected alliance territory. Fortresses and strongholds are Fortress Battles registration objectives and do not require a connected banner, as explained in the official Alliance Territory guide.

StructureFootprint / coverage
City2×2 footprint; community tests report bonuses at 2/4 tiles. This builder now targets at least 3/4 (75%) as the alliance planning policy.
Banner1×1 footprint; 7×7 territory zone.
HQ3×3 footprint; 15×15 territory zone.
Bear Trap3×3 footprint; creates no territory. Planning target: all 9 tiles in connected territory. An exact official trap percentage has not been verified.
Alliance resource node2×2 footprint; needs at least 3 of 4 tiles covered to count toward alliance resources.

Overlapping coverage is counted once. Banners need a connection back to an HQ; a cluster of banners without an HQ does not qualify. Another alliance's land does not count as your coverage.

Solid territory outlines show HQ-connected coverage. Grey dashed outlines show detached planned coverage. In the Bear Trap builder, Check city coverage checks the 75% city planning target and full trap footprint. Publication checks every city position, including vacant previews.

Defensive packing

Two-tile territory coverage does not stop enemy teleports. Dense defensive templates also check for free 2×2 footprints anywhere touching their connected territory, including boundary-straddling footprints. That result assumes every planned city is physically present. A departed or unfilled city reopens a landing footprint; preview sprites and assigned names are not live occupancy checks.

Use View → Load dense defensive layout, then review the changed positions. View → Landing gaps switches between the full plan, assigned city positions, and no overlay. Test a city leaving temporarily removes one position from the gap check without changing the roster. Real vacancies need a replacement occupying city; troops parked on a tile are not treated as a permanent city blocker.

The checked options now vary in trap orientation and capacity. The 97-position square variants use 12 banners; Compact has 84 positions and 8 banners; HQ Defender has 120 positions and 12 banners. All pass the city/trap planning targets on unobstructed ground. Terrain, competing claims and actual occupancy still need review. Coverage-only and legacy templates remain available and may have landing gaps.

Automatic people and banner placement

Use Roster or Manage → Auto-assign by power. Preview the result, then apply. Active members are sorted strongest inward for their selected trap; Either/unselected members balance between traps. Offline/inactive members reserve available middle parking positions without displacing active members or taking first-ring spots. Extra parked members use other free positions. Over-capacity or unavailable-trap members are listed as unplaced.

The default proposal also adds connected banners to meet at least 3/4 city tiles and 9/9 trap tiles. Unknown terrain is not inferred. Coverage expansion can create more possible landing anchors; the review shows that rather than declaring the hive secure. Turn off banner planning for assignment-only work. Locked imported cities can retain their occupants; Undo restores this action. Offline flags come from the roster, not live game presence.

Red R1 launches at opening, green R2 at +1 minute, purple R3 at +2 minutes. These launch colours are not territory ownership. Red banner pins identify B1/B2/etc. Parked members have no launch time. Measure travel in game; moving a member or changing their target clears obsolete march measurements.

Build a useful hive

  1. Choose clear ground first. Mark mountains, water, occupied buildings and permanent alliance resources before allocating city positions.
  2. Keep your main rally captains close to the active trap. Place joiners around them and keep shared access to both traps where practical. Tile distance is only a planning estimate; verify actual march times in game.
  3. Reserve 1×1 banner positions and a 3×3 HQ footprint before players teleport. Do not use a prime rally-captain position for a banner if a nearby gap can provide the same coverage.
  4. Use the HQ's larger coverage efficiently, then extend connected banners into gaps. The builder prefers at least three covered city tiles; fully covered city footprints give more room for later adjustments.
  5. Keep the construction chain usable at every step: build outward from the HQ. Checked template markers B1, B2 and so on provide an HQ-connected banner construction order. Check what removing or relocating an HQ/banner would disconnect before doing it in game.
  6. Claim enough alliance meat, wood, coal and iron to sustain expansion. Resource nodes have the stricter three-tile requirement; do not apply the city's two-tile rule to farms.
  7. After each edit, check coverage and building collisions again. Auto-fix suggests connected coverage; it is not a proof of the fewest possible banners.
Teleport and territory cautions

An Alliance Teleport brings a city near the R5. A Territory Teleport brings it near the alliance HQ, choosing the Tundra HQ when available. Neither is a promise of an exact planner slot. Use the appropriate item and verify the game's destination preview.

HQ construction is allowed in Icefield and Tundra, not Fertile Land. Region unlocks and alliance technology still apply to expansion. This planner does not know your live unlocks, competing claims or build order. It conservatively avoids relying on corner-only territory connections.

Facilities require territory access; Fortress/Stronghold participation is a separate system. Do not extend an expensive chain solely because a Fortress icon appears nearby.

Sources and limits

Community authors describe a tradeoff between a clean three-banner trap arrangement and a closer but staggered one-banner arrangement. Compare those examples and an original layout author’s 2026 notes. These are planning references, not a guarantee every site fits.

The two-tile alliance-territory rule is supported by community reports. The official help article about allies' Domain Bonuses also mentions half a city, but that is a different buff system and is not used here as proof of alliance territory rules. Live placement previews remain the final check.