Shown in the app's own themes — pick the one you run. Light or dark follows the toggle above.
Daily round
Alliance Helper
The shared automation behind four alliance activities — covering the Alliance help row in full.
Alliance Helper is the one piece of automation behind four alliance activities on the Duties tab — Alliance help, Alliance gift, Alliance treasure and Alliance donation — each its own row with its own switch and its own schedule. This page covers the Alliance help row in full, and explains the shared mechanism underneath all four; see Alliance Donation, Alliance Gift and Alliance Treasure for the other three.
Where to find it: Instances ▸ open an instance ▸ Duties ▸ Daily activities ▸ Alliance help ▸ ⚙. It is a duty, not a plan task: it has no card in Task setup and no chip on the plan shelf.
How often
Come back every
Run cap
Retry when it fails
Reset schedule
Record line
Reset records
Done
Alliance help’s settings window, on its Schedule.
Set it up
Open the instance and go to the Duties tab. Press Daily activities in the row of buttons under the headline to scroll to the card.
Flip the row's switch to ON.
Start the instance from Overview. Duties only take turns while the instance is running.
The row
ON / OFF
The row's switch, at its start. ON: the duty takes its turn whenever it comes due. OFF: it never runs, and nothing waits for it. Default: OFF. Your settings and its record are kept while it is off.
Alliance help
The row's name, beside its icon. Clicking the name opens the settings window, the same as ⚙.
Gift badge
A small gift icon right after the name, shown only while Reward claims is on and this row is switched on — it reports where today’s round of this activity stands on the game’s own Activity board. Faded: not looked at yet today. Plain: looked at, not done. Gold ring: the bot claims it, unconfirmed. Gold dot: done, with a reward waiting. Green check: the game confirms it. Orange cross: the bot ran it, but the game disagreed. With Reward claims off, the badge stays hidden — nothing is reading the board.
Status chip
What the duty is doing, in words, with a small lamp beside it: Off; Due (waiting for its turn); Running; Done 14:05 (had a turn today, at that time); Retrying 14:40 (a turn failed, and it is waiting before it tries again); Skipped (the bot could not start it, with the reason added underneath); Held (waiting on its own settings); or Standing down (Solo is on for a task). Hover the chip for the full reason.
Summary line
The line under the name repeats your schedule: Once per game day, or Every Nh on an interval (just Every hour when N is 1). It adds before plan tasks or up to N× a day when those are set.
⚙
The settings button at the end of the row, drawn as a set of sliders — the row's name opens the same window. Hover text: Settings for this duty — when it runs, and how it behaves.
The settings window
The ⚙ opens a window titled Alliance help. It opens straight onto Schedule — which alliance activity this row runs is fixed by the row itself, so there is no Task setup tab to switch to. Hover any control for its tooltip.
How often
Two segments, Once a day and Every few hours. Once a day takes one turn per game day, which ends at the daily reset (00:00 US Pacific time). Every few hours keeps coming back on an interval. Default: Every few hours.
Run before plan tasks
Shown only while How often is Once a day. Off, the row waits for free time and only pushes into a busy plan as the reset gets close. On, it runs before the plan's first task of the day, together with every other row you tick, in board order. Default: off.
Come back every
Shown only while How often is Every few hours. 1–24 hours, measured from the last time the row actually ran rather than from a fixed clock, so a turn that was cut short does not lose its place. Default: 1 hour (this duty’s own answer — help requests are worth catching often).
Run cap
Shown only while How often is Every few hours. Reads Use up to … per Game day: the most times the row may run in one game day, 0–99. At 0 it reads No cap and the row runs as often as its interval allows. Default: No cap.
Retry when it fails
1–10 tries a day: how many times a failed turn is tried before the row is left until its next window, with a longer wait between each try. 1 means don't retry. Default: 3.
Reset schedule
Puts this page back to its shipped defaults and closes the window.
Record line
Left of the footer buttons: what the row has recorded about its own turns — for example Had its turn today, 2 turns today, Backing off until 14:32 after 2 fails, Last turn at 09:14 — or Nothing recorded yet. Long lines are shortened; hover for the whole line.
Reset records
Forgets what the row remembers about its turns — whether it ran today, how many turns it took, any wait after a failure — so it can take another turn. It asks first (Reset them / Cancel) and acts at once, without closing the window. Nothing in the game changes and your settings are untouched. Greyed out while nothing is recorded.
Done
Saves the window and closes it. The ✕ in the title bar, or Esc, closes it without saving.
How it runs
It opens the alliance window from the button on the game’s main screen and taps into the Help page — no City Mapper building is needed, since the alliance window opens from the game’s own menu. It waits for a slow Alliance window to finish opening and taps once, never twice.
If any member has a pending request, it presses Help All once, which answers every pending request in one tap, and reports Helped alliance members.
If nothing is pending, it reports No help requests pending and backs out — a normal result, not a failure.
It spends nothing — helping never costs gems or resources.
If another alliance row is due at the same moment — Alliance gift, Alliance treasure or Alliance donation — it takes its turn straight after without leaving the alliance window and re-opening it.
When several duties are ready at the same moment, Daily activities goes after Protection and Buffs, and before Reward claims and Common tasks.
Every turn is written to the Activity Monitor on the Overview tab, in the words quoted on this page.
The shared automation
All four alliance rows drive the same underlying task and share one authored walk to the alliance window — switching one on does not switch on the others; each still has its own switch and its own schedule. They are split across two shelves by what they ARE: Alliance help and Alliance donation are work the account performs, so they sit here on Daily activities; Alliance gift and Alliance treasure are things the alliance hands over, so they sit on Reward claims. Nothing about running them together changes with the shelf — two rows due at the same moment still take their turns back to back without reopening the alliance window in between. Each row closes only the windows it opened, so the game’s exit prompt is never left on screen for the next duty.
Examples
Busy alliance (Northwatch): leave the shipped Every hour schedule so help requests rarely sit long unanswered.
Quiet alliance (Silverpine): switch How often to Once a day and turn on Run before plan tasks — one visit a day, done before the rest of the plan starts.
Troubleshooting
The row is ON, but it never runs.
Duties only take turns while the instance is running — press Start on Overview. If the chip reads Standing down, Solo is on for a task in the TASKS section; turn Solo off.
The Activity Monitor never says it helped anyone.
That means every visit found nothing pending — a normal result. If you know requests are waiting, check the account is genuinely in an alliance and that a game popup is not covering the Alliance button.
Can one row both help and donate?
No. Each alliance activity is its own row with its own switch and schedule — Alliance help and Alliance donation here on Daily activities, Alliance gift and Alliance treasure on Reward claims. When two come due together, they run back to back without leaving the alliance window.