Events & rewards
Expedition
Claim twelve hours of expedition income the moment the bar fills.
Expedition claims your Expedition Income: up to twelve hours of resources and items the game hands over in one press, from the city wall. It claims only when the game's own Online Time bar is full, and it reads that bar to know exactly when to come back.
NeedsCity map with the Walls mappedAt least one expedition stage completed (in-game)Switched on under Duties ▸ Reward claims
Where to find it: Instances ▸ open an instance ▸ Duties ▸ Reward claims ▸ Expedition ▸ ⚙. It is a duty, not a plan task: it has no card in Task setup and cannot be added to the plan. It has no schedule to set — the game's bar is its clock.
Set it up
- Map the Walls in City Mapper, on the city map profile this instance uses.
- Open the instance and go to the Duties tab. Press Reward claims in the row of buttons at the top.
- Flip the Expedition switch to ON.
- Press Start in the instance's header. The first turn reads the bar; from then on the row knows when to come back.
The row
ON / OFF
The switch at the start of the row. ON: the duty takes its turn whenever it comes due. OFF: it never runs, and nothing waits for it. Default: OFF. Switching it off keeps your settings and what the duty has recorded.
Expedition
The row's name, beside its map icon. Clicking the name opens the settings window, the same as ⚙.
Status chip
The reading at the right of the row, a word with a small lamp beside it. Off; Not checked (nothing has been read yet); Until 21:40 · 7h 12m in green (the bar will be full at that time, which is when the duty comes back — a weekday is added when that is not today); Due (that time has passed, so it is ready to claim); Running; Retrying 14:40 (a turn failed); Skipped; or Standing down (Solo is on for a task). A reading shows even while the row is off — for example after a Server gift turn claimed the income for it. On an account that has never completed an expedition stage, the chip stays on Not checked for good instead of moving on to a time — the row stops checking after that first visit (see the FAQ below). Hover the chip for a one-line explanation.
Summary line
Always Claims the 12-hour expedition income the moment it fills. When the chip reads Skipped, the reason follows, tinted as a warning, for example · Skipped: its task is switched off.
⚙
The settings button at the end of the row, drawn as three sliders. Its tooltip reads Settings for this duty — when it runs, and how it behaves. It opens the settings window described below.
The settings window
- Run before plan tasks
- Retry when it fails
- Reset
- Record line
- Reset records
- Done
One page, headed Schedule — the game decides how often this one runs — this is where it takes its turn. The window's title bar carries the row's name and a ✕. Hover any control for its tooltip.
Run before plan tasks
A switch. Off, it waits for a free moment when its time comes. On, it goes ahead of the plan's next task the moment its turn comes round, and ahead of the other duties waiting with it. It never arrives early: the bar decides when its turn is. Default: off.
Retry when it fails
A number box, 1–10, shown as N tries a day: how many tries a failing turn gets in one game day. After a failure the duty waits a few minutes, then a little longer, before the next try. When the tries are used up it waits for the game's daily reset. 1 means a failure is not tried again. Default: 3.
Reset
Puts every control on this page back to its shipped default, saves that, and closes the window.
Record line
The muted line at the bottom left: what the duty has recorded. For example Running until Sun 04:05 · 9h 35m left (when the bar will be full), Lapsed at 04:05 (that time has passed and the bar has not been read since), or Backing off until 14:40 after 2 fails. A fresh row reads Nothing recorded yet. A long line is shortened; hover it for the whole line.
Reset records
Forgets the recorded bar reading and any wait after a failure, so the duty goes and looks again. It asks first (Reset them / Cancel), then acts at once without closing the window. Nothing in the game changes and your settings stay. Unavailable while nothing is recorded — which includes the moment the row reports No expedition has been started on this account: that mark on its own does not enable the button, so there is currently no way to clear it from this window. See the FAQ below.
Done
Saves your changes and closes the window. The ✕ in the title bar, or Esc, closes it without saving (a Reset records you already confirmed stays done).
How it runs
- It returns to the city and looks over the city gate. When the income is full, a red-and-gold chest medallion floats there, and one tap opens the Expedition Income popup.
- No medallion: it walks to the wall, opens its menu, and finds the Expedition option by its picture, so a damaged wall that shows a repair option does not get in the way. In the Expedition window it presses the Expedition Income chest (drawn inside the Online Time ring) in the window's bottom-right corner.
- Before pressing that chest, it checks the Expedition window's stage list. An account that has never completed a stage earns no income: the bot reports No expedition has been started on this account and stops visiting for good — see the FAQ below for what that means.
- In the popup it reads the Online Time bar, which counts up to 12:00:00.
- Full: it presses Claim, waits for the game's Congratulations list as proof, closes it, and reports Claimed the expedition income.
- Less than two minutes short: it waits in the popup and claims the moment the bar fills.
- Not full: it presses nothing. It records when the bar will be full, reports for example Income 9h 35m 42s short — claiming at Sun 04:05, and comes back at that moment.
- The expedition medallion was gone means someone claimed it between the look and the tap — usually you, by hand. That is a normal result.
- It goes back to the city afterwards. When several duties are ready at the same moment, Reward claims go after Protection, Buffs and Daily activities, and before Common tasks.
- Every turn appears in the Activity Monitor on the Overview tab, in the words quoted on this page. A failed turn's card opens by itself so you can see why.
Examples
- Set and forget (Northwatch). Switch it on. It claims each full bar as soon as it can after the bar fills — about twice a day while the instance runs.
- Claim first when it is ready (Silverpine). Switch on Run before plan tasks. When the bar fills, the claim goes ahead of the plan's next task instead of waiting for a quiet moment.
- New account (Ember Keep). If the account has not completed an expedition stage yet, one visit reports that none has been started and the row stops checking for good, with no way from this window to make it look again. Leave Expedition switched off until the account has finished its first stage in the game, then switch it on.
The game lets you claim before the bar is full, but claiming early starts the twelve hours again and throws away the rest. That is why this duty waits for 12:00:00 even when the in-game Claim button is lit.
A full expedition medallion sits in the same spot over the gate as the Server Gift chest, and hides it. So a Server gift turn that finds a full expedition claims it first — even while this row is off — and records the new time on this row.
- Record line — Nothing recorded yet
- Reset records (disabled)
- Done
Troubleshooting
The Claim button in the game is lit. Why has it not claimed?
It waits for the full twelve hours on purpose — claiming early restarts the bar. The chip shows when it will be full; it claims then.
Expedition never claims, and the chip never shows a time.
Look at the Activity Monitor on Overview. No expedition has been started on this account means the account had not completed a stage the moment the duty checked, so there was no income to claim — and once it reports this, the row stops checking for good. Reset records would normally clear a mark like this, but the button stays disabled here because nothing else is recorded, so it cannot currently be pressed. Switching the row off and on does not clear it either. There is no way from the app to make the duty look again once this fires; on a new account, wait until you have completed a stage in the game before switching Expedition on.
The Activity Monitor says Couldn't find the Expedition option on the Walls popup.
The wall opened but its Expedition option was not recognised on any look. The duty closes the menu it left open and tries again on its own. If it keeps happening, open the Walls menu by hand and check that an Expedition option is there.
The Activity Monitor says Couldn't find the Expedition Income chest in the window.
The Expedition window opened but its income chest was not found. Something may be covering the window; the duty tries again on its own. Tapped the income chest but its popup didn't open is the same visit one step later.
The Activity Monitor says Couldn't open the Expedition window from the city wall.
The walk to the wall or its menu failed. Check the Needs setup card on Overview for an unmapped Walls, and re-check the Walls in City Mapper with its Go to building button. The duty tries again on its own.
It says Couldn't read the expedition's online time.
The bar was on screen but could not be read, so nothing was pressed. The duty tries again. If it keeps happening, raise Screen delay in the instance's Settings so the popup has finished drawing before the bot looks.
It says The income is full but Claim isn't lit.
The bar read full, but the Claim button was not lit, so the bot refused to press it. It tries again later. If it repeats, open the popup by hand and check what the game is showing.
It says Couldn't claim the expedition income.
The bar was full and Claim was pressed, but the game showed no Congratulations list and the bar did not restart. The duty does not press again on the same look; it tries again later.
Server gift claimed my expedition income.
That is expected. A full expedition hides the server gift, so the Server gift duty claims it first and then takes the gift. It only ever claims a full bar, and the new time is recorded on this row.
The chip reads Retrying with a time.
A turn failed and the duty is waiting before it tries again. The settings window's record line says how many turns in a row have failed. Once the day's tries are used up it waits for the daily reset; fix the cause, then press Reset records to let it try straight away.