Alliance Strategy

“Ten members tapping daily out-research one whale, every time.” — from the Alliances guide; the Codex would phrase it as a proverb about stitches

Alliances covers the mechanics. This page is for leaders and officers — how to run one that compounds instead of stalling.

Tech routing

Three trees, 15 nodes each (ten cap at level 10, five at level 5) — you cannot rush everything, so route deliberately:

• First fortnight: Develop’s early production nodes. Alliance-wide economy bonuses multiply every member’s growth during the stage when growth compounds hardest. This out-values early Combat nodes for the same donations.
• Then Combat’s stat nodes, timed to when your core members start grinding tier 4+ snarls — that’s when alliance-wide troop stats start converting into real Font savings.
• Reign as needed — its reach/politics nodes matter more as future systems land; take its cheap early nodes opportunistically when bars fill themselves.

Declare a “node of the week.” Donations scattered across twelve nodes finish nothing; the same taps focused finish a node every few days. One pinned message in alliance chat is all the infrastructure this needs.

The boss window

The Devourer is the alliance’s paycheck, and windows beat drizzle for one structural reason: the weekly respawn resets the pool — damage that doesn’t accumulate to a kill before reset pays nothing. The playbook:

1. Fix a window (a recurring day + time band) and pin it.
2. Heal-out beforehand — announce it a day early so Fonts are empty when the window opens.
3. Everyone marches repeatedly, biggest engagement their Font absorbs, marches recycled as they resolve.
4. Post the payout in chat afterward. Nothing recruits internal participation like a visible payday.

A 20-member alliance running one disciplined window a week clears the boss reliably; the same members free-lancing usually don’t.

Recruitment & ranks

• Recruit for cadence, not power. A daily-login Sanctuary half your size contributes more taps, marches, and boss damage per week than a giant who visits on Sundays.
• Promote for function. R4+ exists to approve joins and start research — give it to your timezone-coverage players so bars never sit full overnight.
• Prune kindly but actually. Capacity spent on the long-inactive is capacity not compounding. A pinned “we prune after N quiet days, rejoin anytime” keeps it fair and unpersonal.

The officer’s daily five minutes

1. Approve/decline join requests
2. Tap the node of the week; nudge if the bar stalled
3. Start any full-bar research (you’re R4+ — that’s the job)
4. Scan alliance chat for unanswered help requests
5. Glance at the boss pool — if the week’s kill looks unlikely, call an extra window

Tip

Every mechanic on this page is a coordination multiplier with a human core: people stay where their taps visibly become shared power. Post the numbers — research completions, boss payouts — where everyone sees them, and the rest runs itself.