How to — Canyon & Desert Storm

1 · Canyon

Everything for Canyon happens on the Canyon page. It walks through three steps, and every step stays clickable at all times, so corrections mid-week are possible. The status line under each tile is derived from the actual data, not from a tick you set yourself. In step 1 the actual work sits inside the collapsible Admin editor (R4/R5) box; below it are the no-show report and the finished lineup for checking.

Step 1 · Lineup

1. Pick players in the left-hand 1 · All active members list. There is a search box above it and Select all / None next to it. The counter at 2 · Selected shows x / 60 — 60 is the target (2 teams × 20 mains + 10 subs): green at exactly 60, orange above, and extras end up in Group C as subs.
2. Rows shaded red and the “No-show KWxx” badge mean: that player was in the lineup for the last measured Canyon week, did not attend, and is not excused. “Excused” means excused.
3. ⚔ Distribute by combat power does the split: sorted by combat power, alternating Team A / Team B. Per team, Group A gets 6 mains + 1 sub, Group B 6 + 3, Group C 8 + 6. Leaders sit on positions 1, 6 and 7, the strongest eight get ** (key starters).
4. Adjust by hand in 3 · Groups: ★ leader (only one per group), ** key starter, S sub, ✕ remove, “+ add player…” to slot someone in.
5. Anyone selected but without a group slot shows up in the orange Not in teams box — swap them in from there, slot for slot.
6. Save & publish saves in two passes: 1/2 the lineup, 2/2 the groups. The message next to the button names both — only then is everything out.

Step 2 · Faction & plan

1. As long as the game has not announced the factions, both teams say “— not announced yet —”.
2. Set the faction per team — Rulebringers (alone vs 2) or Dawnbreakers (with partner) — and pick the plan: Whole map (3 phases), Split: left side or Split: right side.
3. Rulebringers always play alone — for them the page forces the plan to Whole map, whatever was selected.
4. Dawnbreakers split the map with the partner alliance. If that alliance does not take part, you play the whole map as well — that call is yours, not the page's.
5. Save faction & plan stores exactly these four values: faction and plan per team. The lineup from step 1 stays untouched.

Step 3 · Battle plan & announcement

1. ⬇ All images at once creates two images per team in one go: the lineup (the three groups side by side) and the battle plan with all phases. Each image has to be uploaded to the game separately, so there are as few as possible. On a phone the share menu opens with all of them; on a computer they download one after the other.
2. If a team still has no faction, the message next to the button says so explicitly. Go back and finish step 2 first.
3. The announcement text is built automatically from the saved faction and plan. ↻ Rebuild from selected plan builds it again; the text is freely editable.
4. The counter reads x / 500 characters — orange from 440, red above 500. Above 500 the game refuses the announcement.
5. 📋 Copy text puts it on the clipboard. Post images and text together — the images show who stands where and attacks what, the text says where to look.

Below: the battle plan per team

• Pick Team A or B below the share box. Both teams play at the same time and can be in different factions — which is why only one team's view is ever shown.
• Which plan applies comes from step 2 and is only displayed here. Change it there, not here.
• With the Whole map plan all three phases (0–7, 7–12 and 12–30 minutes) are shown at once: every building lists its group per phase. With a split map one assignment holds for the full 30 minutes.
• Below the map sit Group tasks (the target per group) and Rules & notes with war time, important notes, leader tasks and the sub/swap rule — the text the leaders should have read before the battle.
• 📷 Lineup image and ⬇ Battle plan image download only the two images of the team shown. The battle plan has all phases in one image: every building lists which group attacks it in phase 1, 2 and 3, below are the tasks per phase and group.

2 · Desert Storm

Desert Storm is planned on the Event Planner page — Canyon runs entirely on the page above. The calendar week in the header is the week that will be saved to.

2.1 · Collecting sign-ups

1. Under Add players type a name and take it over with ＋. The search ignores special characters. ＋ Add all active takes every active member in one go.
2. Faster by video: in the game, scroll slowly through the “Select participants” screen while recording (MP4) — or take screenshots.
3. On the page, unfold ⚡ Read sign-ups from video / screenshots (Gemini), choose the files, hit Read & add. Everyone carrying the red badge in the top-right of their row is taken over: “Request to Battle for Task Force A/B” (or “Teilnahme erbitten” in German).
4. Names the recognition could not match appear below with a dropdown. Assign them once — the assignment is remembered and reused next time.
5. Anyone matched but not active is skipped and listed at the bottom. That is the moment to double-check the member list.

2.2 · The sign-up list

1. The Ready for assignment list counts x / 60 — green at exactly 60, orange above.
2. 💾 Save sign-ups stores it for the current calendar week. Older weeks are left alone.
3. You rarely need that button: the list is saved automatically when you distribute, when you add to existing teams, and when you save the lineup — but only if it changed since the last save. The message next to the buttons says so.
4. The orange ● Unsaved changes dot next to the heading means the list differs from what is stored. It clears itself once one of those three clicks has saved it.
5. 🗑 Clear list throws the whole list away — but on screen only. It is stored again only after another click on 💾 Save sign-ups.

2.3 · Distributing the teams

1. Distribute (new teams) rebuilds both teams from scratch. At most 60 players are placed; anyone beyond that (the weakest) is reported explicitly and stays out — they do not fall off the end silently.
2. Add to existing teams only fills free slots and appends latecomers to the end of a team that still has room (< 30). Nothing is sorted — nobody else moves.
3. If both teams are full, the latecomer stays in the Not in teams box. From there you swap them in slot for slot: they take over position and building of the player you pick, who moves out into the box.
4. Below that both teams appear as a table: # · NAME · POWER · TASK. The header line says how many are in, how high the total power is and — important — top 20 = starters: positions 1–20 are starters, 21–30 are subs.
5. Every row has four buttons: ↑ Move up and ↓ Move down swap the player with their neighbour, ↔ Move to other team puts them at the end of the other team, ✖ Remove takes them out (they stay on the ready list and reappear under Not in teams). Each arrow therefore swaps two buildings as well — this is how you put someone on a specific building on purpose.

2.4 · Publishing the lineup

1. 💾 Save lineup asks for confirmation and then fully replaces the published Desert Storm lineup. Canyon is untouched.
2. What gets published is the lineup plus the building list for the current calendar week.
3. If only the building list changed, one save is enough — no player is moved.
4. 📷 Export images (A + B) downloads two PNGs, one per team, portrait and 760 points wide. That width is the reason they are readable on a phone — do not put both teams side by side.
5. If both teams are unexpectedly empty, nothing is lost: the page then offers the most recent week already played, with a Load it button. Check it — anyone who has left the alliance drops out and is reported — then save.

3 · Recording attendance and no-shows

In the menu under R4/R5 → Data Entry (Data Entry), then the Enter Data tab → sub-tab Events (D). Only once ticks are set here does the no-show report know who actually turned up.

1. The table has eight columns per player: M#1–3 (Marshall), Z#1–3 (Zombie), Canyon and WS. Each column header carries an All button that sets the whole column at once, next to it the counter (e.g. 0/90).
2. Faster with ⚡ Auto-fill from event mail (Gemini): pick the event at the top (Marshall #1–3, Zombie #1–3, Canyon, Desert Storm), upload the in-game event mail as a video or screenshots, then Read & check participants. Whoever is in the mail gets the tick, everyone else stays blank.
3. Then read over it: the recognition sets ticks, it never removes any.
4. Nothing is stored until Save data for the active tab at the bottom of the page.
5. Points: Marshall and Zombie 5 each, Canyon +10, Desert Storm +10 — 50 per week at most.

Once the week has ticks, the no-show report fills up — at the bottom of the Event Planner and in step 1 on the Canyon page. It carries the week in its title and lists everyone who was in the lineup but has no tick. The orange line under a name says how often that player has been absent before; excuse next to it excuses them.

4 · What the alliance gets to see

Under Events → “Desertstorm / Canyon” (Team Lineup) every member sees the published result: the lineup, the building per position for Desert Storm, and for Canyon additionally faction, plan, groups and map. A tab at the top switches between Desert Storm and Canyon, and at the bottom there is a Download section for the images. What stands there is exactly what was saved last — one more reason not to forget the save button.

5 · Tick-off checklist

One week, to work through.