Alliance Tech is a coordination problem
City research is yours. Alliance Tech is not. If four governors donate into four different nodes, nobody finishes a rank in time for Alliance Brawl or a KvK prep week. The first question is always which tree is already live, not which tree looks nicest on a ranking graphic.
Open the Alliance Tech planner and add the slug officers named. Leave Include prerequisites on. Unmatched gates are listed as warnings — those ranks are not priced as extra rows until they exist in our tables.
A sequence that does not fight the officers
- Ask in alliance chat which tech is currently researching. If the answer is Adaptive Tools, load the Alliance Brawl week or Alliance Tools I-style start preset and adjust from/to to the ranks you actually have.
- If the answer is a deeper node, use the Alliance recommended path (prereq depth) preset as a starting point — it orders Adaptive Tools plus community prerequisites shallowest-first. That is our expand rule, not lore.
- Share the encoded rows from the Progression hub as an
a:segment so the rest of the alliance can open the same plan instead of a screenshot that goes stale after a patch.
When Alliance Brawl week is on the calendar
Brawl scores shared research, caravans, Truegold, intel and widgets. Donating into a tech you were going to rank anyway is the cheap version of “playing the event.” Inventing extra spend the alliance will not finish is the expensive version. The Alliance Brawl event page links the same planner.
If you are still in your first month, join an alliance on day one — the First 30 Days roadmap explains why gifts and help speedups matter more than a solo tree.
What we will not promise
We do not invent Alliance Tech trees that are missing from core JSON. If a slug is not in the catalog, skip it. Confirm live times in the alliance research screen; our totals are planning ranges with a Last checked date.