Task duties

Duties

The per-instance setup board: the daily care an account needs, and the plan’s own task order and schedules.

The Duties tab is where you set an account up. It holds the daily care the account needs whether or not it is busy — a bubble on the keep, buffs kept up, the daily activities, the reward claims — and the Tasks card, which is the plan itself: which tasks this instance runs, in what order, and how often. The Plan tab is where you watch the result.

NeedsAn instance A city map, for anything that walks to a building

Find it at Instances ▸ open an instance ▸ Duties — the third tab, between Plan and Task setup. Everything on it belongs to that one instance. A duty is a row you switch on, and the bot fits it in around your plan; a task is a row on the Tasks card, with a place in the order. A change you make here reaches a running instance straight away — you do not need to stop and start it.

The Duties tab — the verdict line and jump rail on top, then one card per section.

In Standing Watch the page is one ruled duty sheet across its whole width. A pinned strip on top carries the verdict — as a stamp when it warns — the detail line and the profile chip, with JUMP TO and the jump buttons, numbered §1 to §6, under it. Below, each card is a band: a label column (the § number, N of M on, the title and its one-line purpose; on Daily activities also the gift box and today’s points) beside its rows, one ruled line per row — switch, icon, name, the summary, a status mark and chip, Reset run and the settings button. The band in view wears a red § number. In a narrow window the label column folds into a header line over its rows. Every control below works the same in all three themes.

Set it up

Open the instance and click the Duties tab.
On the Tasks card, click a chip under Add to plan for each task this account should run. Each one joins the plan at the bottom, switched on.
Drag the task rows into order of importance. The top row matters most.
Click a task’s name or its settings button to choose when it may run and how often, then click Done.
Down the other cards, switch ON each duty you want, then click its name or settings button to choose what it may use and when. Start with Protection.
Press Start in the instance header. The verdict line at the top of Duties tells you how the day is going.

The top of the page

Two lines stay pinned while the cards scroll underneath them.

Verdict lamp and headline

The one thing worth knowing about this board right now. The headlines, in the order they win: Solo — only task runs (orange) while a task is in Solo, or Solo — task is switched off (red) when the soloed task’s own switch is off; No duties enabled yet (grey); Protection lapsed (red — the bubble has run out and was not renewed); Attention needed (orange — a duty skipped, is retrying after a failure, or a bubble or buff is inside its renewal window); All duties on track (green); Duties waiting to run (blue — the ordinary start of a day, or every switched-on duty is held by its own settings).

Detail

After the headline, short facts joined by dots: how many of today’s switched-on daily rows are done (6 of 9 done), how long the bubble holds (bubble the keep holds until 14:32), and how many rows are skipped, held and due. While the instance is not running it ends with instance idle — duties resume when it runs. Under Solo the detail says what Solo does instead: Every other task and every duty stands down until you exit Solo. Protection will not renew. A long detail is cut short; hover it to read it in full.

Profile chip

At the far right of the verdict line: the profile this instance follows and whether it still matches — No profile, In sync, or a count such as 1 change or 3 changes. Click it to open Profiles. Switching a duty or changing its settings here counts as a change until you save it to the profile.

Jump rail

One button per card, in page order: Protection, Tasks, Daily activities, Common tasks, Reward claims, Buffs. Click one to scroll straight to that card.

Rail badge

A small number beside a card’s button counts the rows there that need a look: red for a bubble that has run out, orange for a row skipped today or a bubble or buff inside its renewal window. Hidden while the card is quiet. The Tasks button never carries one.

The cards, in order

Protection — Keeps a bubble on the keep so the account is never caught open. Bubble the keep, and the War events settings row.
Tasks — What this instance runs, in priority order — pick from the shelf to add, drag a row to set the order. The plan, authored here. See below.
Daily activities — Your daily to-do list in the game — every round done before reset, every reward collected. Its header also carries the reward-claiming gift and the day’s activity points.
Common tasks — Jobs you set once and the bot fits in when it can — not tied to the daily round. Daily Purchases, Transport Resources, Viking Challenge and Rally Monthly Card Spawn sit here.
Reward claims — Free things the game hands out — claimed before they expire.
Buffs — Keeps item buffs active and renews them before they run out.

Each duty card’s header shows N of M on for its rows.

Reading order is not running order. When several duties are ready at the same moment, Protection goes first, then Buffs (they burn down in real time), then Daily activities, Reward claims and Common tasks. That order only breaks ties — a duty whose own clock says it is due takes its turn whatever card it sits on.

Anatomy of a duty row

Every row runs left to right the same way, so “what is on?” is a glance down the left edge.

ON / OFF

The duty’s switch for this instance. ON — this duty takes its turn whenever it comes due. OFF — this duty never runs, and nothing waits for it. Every duty row ships OFF, so a fresh instance does nothing here until you choose.

Icon and name

Click the name to open the duty’s settings window — the same window as the settings button.

Activity gift

Daily activities rows only, while reward claiming is on and the row is switched on: where that activity stands on the game’s own Activity board. See Daily activities.

Lamp and status chip

What the bot is doing about this duty, right-aligned so the chips form one column. Hover the chip for the reason behind it. The words are listed in the next section.

Reset run

Only on a row that takes one turn and then waits for you (Dwarf’s Lucky Apple). It appears once that turn has spent. Click it, and confirm Reset it, to allow one more turn — that turn spends for real, as much as the row’s settings ask for.

Settings (sliders button)

Opens the duty’s settings window. Tooltip: Settings for this duty — when it runs, and how it behaves. Absent on a row with nothing to set.

Summary line

Under the name: what you set, in short — for example Once per game day · before plan tasks or Always bubbled · renews 30m early · 8 hours · gems: never. When the row is skipped or held, the reason is added on the end, for example · Skipped: its task is switched off, or · Held: followed by what its settings are waiting for. Hover a cut-off line to read it in full.

What the status chip says

Off

The switch is off. The summary keeps your settings.

Due

Nothing is holding it and it is waiting for the scheduler to fit it in. Blue — nothing is wrong.

Running

It has the screen right now.

Done 09:14

It finished today, at that time. A row that takes one turn and waits for you reads plain Done after that day.

Until 14:32 · 5h 40m

A bubble or buff is up until then, with the time left. Green, turning orange once it enters its renewal window. One that ends on another day names the day, for example Until Sun 03:51 · 2d 18h.

Not checked

A bubble or buff nobody has read yet. It looks the next time it has the screen.

Held

Switched on, but its own settings stop it running. The reason is on the summary line.

Skipped

It could not run today. The reason is on the summary line.

Retrying 14:30

Its last turn failed and it tries again at that time. Orange, and it raises Attention needed.

Standing down

A task is in Solo, so this duty waits until you exit Solo.

Next check 14:30

A row that keeps a clock of its own — Garuda Trial, Rally Monthly Card Spawn, Viking Challenge — names its next look. Some say what they wait for instead, such as All claimed (Garuda Trial) or Boss up and Spent today (Rally Monthly Card Spawn). Green — nothing is wrong.

The Tasks card

This card is the plan. The top half is a shelf of everything you can still add; below the line, one row per task you have. The order of the rows is their importance, not a timetable: Evonex works out when each one actually runs from its own schedule, and when two want the screen, the higher row wins. A task that has missed its time gets a small boost until it runs; tasks with no clock at all simply run in list order.

Tasks header

The card title, its line What this instance runs, in priority order — pick from the shelf to add, drag a row to set the order., and N of M on for the rows below.

Add to plan

The shelf. N available on the right counts its chips. A task already in the plan is not on the shelf, and neither is a task switched off in Studio or one whose settings live on a Duties row. When there is nothing left to add it reads Everything in your library is already in the plan.

Task chip

Click to add that task to the plan — at once, with no dialog. It joins at the bottom, switched on. A chip ending in • (for example Champions •) has settings already prepared on the Task setup tab, and they are applied when it is added. There is no undo: the row’s bin button is how you take a task back out.

Bundle chip

Reads like Weekend bundle 2/4 … — how many of its parts are already in the plan, out of how many. Click it to choose which parts to add (below). Once every part is in the plan the chip stays, greyed out.

Row switch (ON / OFF)

ON — this task takes its turn in the plan. OFF — the plan skips this task entirely. A switched-off task’s name is dimmed.

Name

Click the name to open the task’s settings window (below). Clicking the rest of the row does nothing — the row body is what you grab to drag.

Standing down

Shown on every other row while one task is in Solo. Tooltip: Solo is on for another task — this one waits until you exit Solo.

Solo

Run only this task: every other task and every duty stands down until you click it again. Lit while on. See Solo below.

Settings (sliders button)

The same window the name opens. Tooltip: Settings for this task — how often it runs and how far it goes.

Remove (bin button)

Takes the task out of the plan after a confirmation (below). Tooltip: Remove this task from the plan. Its setup answers are kept, so adding it back restores them.

Line 2

How the task is scheduled, in words — always watching, when a march is free, once a day, whenever the screen is free, once each time you press Start, every 2 hours, 10 a day · finish today, 3 at a time, only when you press Run — with any opening hours added, such as only 08:00-23:00. A row that reads Run from Duties belongs to a task whose settings live on a Duties row; it never runs from the plan.

Drag

Grab a row anywhere except its switch, name and buttons, and drop it higher or lower. The new order saves when you let go.

Empty plan

With no rows the card says No tasks yet — pick from the shelf above to start the plan.

Adding part of a bundle

A bundle holds several tasks. Its chip opens a checklist, and each part you tick becomes its own plan row, under its own name, with its own schedule.

Add from …

The window’s title names the bundle you clicked, for example Add from Weekend bundle.

Part checkboxes

One per part, ticked to start with unless the bundle says otherwise. A part already in the plan is ticked, greyed and marked (in plan). A part with settings prepared on Task setup is marked (configured) and keeps them.

Note

Each part becomes its own row, with its own schedule. Anything marked (configured) keeps what you already set up on the Task setup tab.

Add N

Adds the ticked parts and closes. It counts what it will add, and reads a plain, greyed Add while nothing new is ticked.

Cancel

Closes without adding anything. ✕ and Esc do the same.

Solo

Solo narrows the whole instance to one task — handy for watching a new task run on its own. While it is on:

The verdict line reads Solo — only task runs.
Every other task row, and every duty row that still had work to do, reads Standing down. A duty that already ran today still reads Done, and a switched-off duty still reads Off.
You can solo a task whose own switch is off. The mode holds, the verdict turns red — Solo — task is switched off, Nothing will run: Solo allows only this task and its own switch is off. Turn it on, or exit Solo. — and Start refuses until you do one or the other.
Click the lit Solo button again to exit. Removing the soloed task also ends Solo. A task that is standing down offers Exit Solo at the top of its settings window.

Solo stands Protection down too. Do not leave an account in Solo when it needs its bubble renewed.

Removing a task

The confirmation behind a task row’s bin button.

The bin button asks Remove task: Remove Champions from this plan? Its place in the order, its schedule and its run progress are removed. Its Task-setup answers are kept, and will apply again if you add it back. Click Remove to confirm, or Cancel. The task goes back onto the shelf.

A task’s settings window

Click a task’s name or settings button. The window is titled with the task’s name and holds how that task runs on this instance. What the task does — what to train, which bosses, and so on — lives on Task setup. Which sections appear depends on the kind of task, as listed below.

Champions’ settings window — a task with fixed timing, set to run only between 08:00 and 23:00.

Where it stands

A sentence at the top on what the task is doing right now — for example Ready — it goes next. or This one runs only when you run it. When the cause is something you can fix, a button sits beside it: Open Task setup or Exit Solo. Absent when there is nothing to say.

What kind of task

A muted line on the task’s nature: This task does a job and returns., This task runs continuously in the background — always watching., This task runs whenever a march is free (adding — how many go out, and how often they’re re-sent, come from its Task setup where its setup decides that), This task runs only when you start it. or This task works through a set amount. You choose by when, and how big one go is — Evonex works out the spacing. It then adds How often is fixed for this task: … where the game sets the timing, Runs only between 08:00 and 23:00. when you set opening hours, and Paused during SvS. when War events holds it.

When it may run

Any time, or Only between two times and (the boxes start at 08:00 and 23:00). An end earlier than the start runs overnight, for example 22:00 to 06:00. Two equal times mean no limit. Offered on every task.

How often

Pick one: Use this task’s own timing (with a note of what that is, such as — once each time you press Start), Every 1–999 min or hours (starts at 2 hours), Daily at server reset or a set time, On a date (starts a week ahead), or Only when I run it. Default: Use this task’s own timing. Not shown for Rally Joiner (always watching), Resource Gathering, Rally Setter and Solo Hunt (they follow your marches), Black Market and Cultivate Generals (they ask Finish it instead), or Champions, Tavern Recruit, Troop Training and Trap Building, whose timing is fixed — so among the tasks Evonex ships, none offers it; it appears on a task you author in Studio.

Finish it

Instead of How often, for a task that works through a set amount (Black Market, Cultivate Generals): All in one go, Today, Within a week or By a date, plus At most N at a time (1–9999, hidden under All in one go). Default: Today. A live line underneath works out the pace, for example About 3 at a time, roughly every 50 min until the reset — 4 sittings. Within a week fills the date box, so the window reopens on By.

Goal

For a task that counts what it does. On Black Market and Cultivate Generals the amount comes from the task’s own setup and reads like 10 a day — from your Black Market plan, with Edit in Task setup beside it. A task you author in Studio without such a link offers Target (1–100000) and a pace — do N at a time or split across N visits, with a number (1 = all in one go). A bar shows how far it has got; Reset progress starts it from zero when you click Done.

Stop after

For a task that loops (Rally Setter): Until it finishes or you stop it, or Run for 1–1440 min (starts at 30). Default: Until it finishes or you stop it.

Reset to default

Puts this task back on its own timing and clears the changes made here — opening hours, How often or Finish it, pace, and Stop after. Progress is kept. The window stays open so you can see what came back. Greyed out when nothing is changed.

Done

Saves and closes.

✕ or Esc

Closes without saving.

A task that works through a set amount asks Finish it instead of How often.

A duty’s settings window

Click a duty’s name or settings button. The window is titled with the duty’s name, and comes in one of two shapes:

Two tabs — Schedule and Task setup. A duty run by a task with options of its own, such as Patrol, Black Market or Troop training. Schedule is when it runs; Task setup is what it does. The window resizes to the tab you pick.
One page, headed Schedule. A duty whose options all sit on the duty itself — Bubble the keep, the six buffs, the alliance rows — or whose task has no options, such as Server gift.
Viking Challenge has a window of its own shape, described on its page.

A daily activity’s settings window on its Schedule tab.

The Schedule tab

Hint

Beside the tab (or under the Schedule heading): when and how often this duty runs. On a row the game meters, the game decides how often this one runs — this is where it takes its turn. On a row that runs once and waits, it runs once, then waits for you to reset it — this is where it takes its turn.

How often

Once a day (done until the game resets) or Every few hours (keeps coming back). Default: Once a day — except Alliance help and Server gift (every hour), Resource collecting (every 3 hours), Alliance donation (every 4 hours) and Produce material (every 6 hours).

Run before plan tasks

Shown for Once a day. Off — it 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 duty ticked the same way, in order. Default: off.

Come back every

Shown for Every few hours: 1–24 hours, counted from the last time it actually ran — a turn that was cut short does not lose its place. Default: 6, or the row’s own number above.

Run cap

Shown for Every few hours: Use up to N uses per Game day, 0–99 — the most times it may run in one game day. At 0 it reads No cap and runs as often as its schedule says. Drag the number sideways, click it to type, or use − and +. Default: No cap.

Retry when it fails

1–10 tries a day: how many times a failed turn is tried before it is left until its next window. The waits between tries grow. 1 means don’t retry. Default: 3.

The row’s own options

Some rows add controls after these, such as Grace of Star Trail’s two switches or Crazy Eggs’ egg board. They are described on each row’s page.

Rows with no How often

Where the game sets the rhythm — a once-a-day claim, a page that prints its own cooldowns — or the row runs once and waits for you, the page offers only Run before plan tasks, Retry when it fails and the row’s own options. On a row that runs on the game’s clock (Crazy Eggs, Expedition), Run before plan tasks cannot make the turn arrive early; it only lets that turn go ahead of the plan’s next task, and of the other duties waiting with it.

Reset schedule

Puts this page back to its shipped defaults, saves and closes. The Task setup tab is saved as it stands. On a row with no How often the button reads Reset.

The Task setup tab

The same window on its Task setup tab — the backing task’s own options.

Hint

this duty’s own copy — the Task plan keeps its own. The duty and a plan row of the same task can be set up differently. The hint is absent for a task that only runs from Duties, such as Patrol, because there is no plan copy.

The task’s options

The same form Task setup uses, starting from this duty’s own defaults.

Reset task settings

Asks Reset task settings: Put this duty’s task settings back to this duty’s shipped defaults? Its schedule is not affected. Click Reset to confirm; it then saves and closes.

The footer

Record line

Bottom left: what the duty has recorded about its own turns — Had its turn today, 2 turns today, Last turn at 09:14, Running until 14:32 · 5h 40m left, Lapsed at 16:50, Nothing running; looking again after 15:30, Backing off until 14:10 after 2 fails, 3 spent this game day — or Nothing recorded yet. A wait after a failure is listed first. Hover a cut-off line to read it in full.

Reset records

Forgets what the duty remembers — the countdown it read, whether it ran today, what it has spent, any wait after a failure — so it may take another turn. It asks first (Reset records, confirm with Reset them), acts at once, and the window stays open. Nothing in the game changes and your settings are untouched. Greyed out when nothing is recorded.

Done

Saves both tabs together and closes.

✕ or Esc

Closes without saving either tab.

Reset records asks before it forgets anything.

When the Overview tab lists a duty under Needs setup, its Fix button brings you here and opens that duty’s window straight on its Task setup tab. Clicking a duty on the Plan tab scrolls this page to its row.

How it runs

Nothing on this page runs until the instance is started. Switches, settings and order reach a running instance straight away.
The plan and the duties share one screen. A duty that is due takes its turn between plan tasks. A duty that is only waiting fills free time in front of the plan’s next task — one duty, then the plan, then the next duty.
A bubble that is due may cut into a running task at its next safe point. A once-a-day duty still outstanding as the reset gets close does the same, so the day gets finished.
Duties with Run before plan tasks ticked go first, as one block, before the plan’s first task of the day.
A failed turn is tried again up to its Retry when it fails count, with growing waits, then left until its next window. The row reads Retrying meanwhile.
Six activities can be set up both as a plan task and as a duty: Black Market, Greet champions (Champions), General enhancing (Cultivate Generals), Resource gathering, Trap building and Troop training. For a plain once-a-day one, such as Champions or Troop Training, whichever lane gets there first does it and the other is held: already done today by the Task plan on the duty, already done today by Task duties on the plan.
An instance with no switched-on plan task still starts if a duty is on, with a Heads-up that only its Duties will run. With nothing switched on in either place, Start is refused: enable a task on Plan, or a duty on Duties, before starting.

Examples

Farm account “Silverpine”: Tasks — Resource Gathering at the top. Protection — Bubble the keep ON with 24 hours in use. Daily activities — the free ones ON at their defaults. Buffs — Gathering speed ON, running with Resource Gathering.
Rally lead “Northwatch”: Tasks — Rally Setter first, Rally Joiner second, Champions third. Protection — Always bubbled, 8 hours then 24 hours in use. Buffs — Attack, Defense and HP running with Rally Setter; March speed buff running with Rally Setter.
Trying out one duty on “Ember Keep”: leave every plan task switched off, switch on one daily activity with Run before plan tasks ticked, and press Start. The instance starts with only its Duties, and the row goes Running, then Done.

Set an activity up in one place. A plan task that repeats — a goal to work through, like Black Market or Cultivate Generals, or marches to send, like Resource Gathering — never counts as “done today”, so a plan row and a duty of the same task both keep running it.

Many duties spend something once they are switched on — gold, resources, items, sometimes gems. Open a duty’s settings before you switch it on, and read its own page.

Troubleshooting

I switched a duty on and nothing happens.

The instance has to be running — the verdict detail ends instance idle when it is not. A Due row is waiting for a free moment; tick Run before plan tasks in its settings if it should go first. A Held row names what its settings are missing at the end of its summary line.

Every row says Standing down.

A task is in Solo. Find the lit Solo button on the Tasks card and click it to exit.

The verdict says Solo — task is switched off.

You soloed a task whose own switch is off, so nothing can run. Switch that row ON, or click its lit Solo button to exit Solo.

A row reads Retrying.

Its last tries failed. Check the Activity Monitor on Overview for why. Once fixed, open the duty and click Reset records to let it try again straight away.

I want a daily activity to run again today.

Open its settings and click Reset records. If the row says already done today by the Task plan, the plan ran it — that record belongs to the plan row, not the duty.

A task I want is not on the shelf.

It is already in the plan, it is switched off in Studio, or its settings live on a Duties row. Look for it on the duty cards.

A plan row says Run from Duties.

That task only runs from its duty row. Remove the plan row with its bin button and switch the duty on instead.

The task’s settings window has no How often.

The task is always watching, follows your marches, works through a set amount (it asks Finish it instead), or has fixed timing. The muted line near the top says which.

Will removing a task lose its setup?

No. Its Task-setup answers are kept and come back when you add it again. Its place in the order, its schedule and its progress are removed.

Start says nothing is enabled.

Switch on a plan task or a duty. If Solo is on, the soloed task’s own switch must be on too.

The profile chip says changes.

Something on this instance — a duty switch, a duty’s settings, the plan — differs from the profile it follows. Click the chip to open Profiles and decide what to keep.