Studio

Task config

How a task runs by default, where it appears, and what callers can pass it.

Task config describes how a task behaves when an instance runs it: what kind of task it is, its default schedule, a goal it works toward, the marches it uses, where it is offered, and the inputs other tasks can hand it. For a routine it holds only the inputs and the return value.

NeedsA task open in the Task Builder

Open it with Config on the Task Builder's top bar. Apply keeps your choices in the builder; they are stored when you click Save task. These are defaults: each instance can still change a task's schedule on its plan.

Task config for a task, with Advanced open.

Set it up

Build the flow first. Task config reads it to detect the task's nature and whether it counts units of work.
Click Config. Check that Detected: reads what you expect, and leave Nature on Auto unless it is wrong.
For a task that does a job and ends, choose its Default schedule, for example Daily at server reset.
If the task sends marches, click Advanced (show) and set Marches used and March time.
Click Apply, then Save task.

Rhythm

The card opens with Rhythm - how this task runs by default. Instances adjust it in their Task plan.

Nature

What kind of task this is. Detected: shows what the flow looks like: a flow built around Loop until… is a background watcher, a flow with a Record march step is a march task, and anything else does a job and returns. The picker: Auto - use the detected nature (default), Background watcher - always on, March task - sends marches, Chore - does a job and returns, Manual - you run it. Override only when the guess is wrong.

Default

Shown for the Chore nature: when the task runs by default. Runs once each Start (default), Every N minutes (a minutes box, 1–1440, default 30), Daily at server reset, On a date (a date, starting a week from today), Just once, or Only when I run it.

Fact line

Shown instead of Default for the other natures: Runs in the background - always on, yielding the screen to chores when they are due., Runs whenever a march is free (set how many in Advanced)., or Runs only when you press Run.

Goal

Shown when the flow has a Report progress step (or a goal is already set). When the settings form has a number or list field, the goal comes From setup: — Sum or Count of a field you pick or type — with the note Target comes from Task setup - edit the number there. Otherwise set Target: (0–1,000,000; 0 = no goal).

Per day / Forever (never resets)

Whether the goal starts again each game day. Default: Per day.

Do N at a time / Split across N visits

How the plan works toward the goal: a fixed number per visit, or the goal spread over N visits, with the number beside it. 0 means no pacing.

Orange warning

When the nature is Background watcher but the flow has no Loop until… and no Checkpoint: This task can't be interrupted once running - chores will wait for it to finish. Add a loop or a checkpoint step to let Evonex share the screen. You can still apply and save.

Red error

When the combination cannot be stored, a line starting This rhythm can't be saved: explains why, and the dialog stays open.

Advanced

Click Advanced (show) to open these and Advanced (hide) to fold them away.

Marches used

How many march slots one run keeps busy, 0–8. Default 0, no marches.

March time

How long one march is out, 1–1440 minutes. Default 30. Counts only when Marches used is above 0.

Typical run time

Roughly how long one run takes, 0–3600 seconds. 0 = estimate it. Default 0.

Interval jitter

Spreads each Every N minutes run by up to this percentage so runs do not land like a metronome, 0–100 %. 0 = exact, the default. Applies only to an interval schedule.

All or nothing - never cut mid-run (a refresh you can't half-spend)

Ticked, the task is never interrupted part-way. Default: off.

Waits for you

A settings field (placeholder config path - e.g. cultivate_plan.mode) and a value (equals - e.g. open). While that field holds that value, the plan shows the task as waiting for you rather than running it. The line underneath reads it back: Waits for you while … is ….

Requires buildings

City Mapper building names this task walks to, separated by commas (placeholder e.g. academy, forge (optional)). An instance is held back until its city has those buildings mapped. Leave blank for a task that does not move around the city. See City Mapper.

Where it appears

Run from Duties only

For a task that is set up and run from a card on the Duties page. Ticked, the task has no chip on the plan shelf and no Task setup card, and the plan does not run it; a copy already in a plan stays listed but goes quiet, and unticking restores it exactly. It always keeps its Studio card. Default: off.

Tick Run from Duties only only for a task that a card on the Duties page actually runs. A task of your own has no Duties card, so ticking it leaves the task with nowhere to run.

Call options & returns

On a task this part is folded away as ▸ Call options & returns (for tasks that call this one), and opens by itself when the task already has options or a return. On a routine it is always open and the list is called Parameters, under Inputs this routine takes and the value it hands back - for the tasks that call it.

Call options / Parameters

Inputs a caller passes when it runs this task with Run task or this routine with Run routine. Each becomes a variable the flow reads. A standalone task usually needs none.

Option row

A label (placeholder e.g. Spins) that also names the variable, a type (Number, Text, Yes / no, List, Match, Coordinate or Image) and a default. Renaming a saved option keeps the variable name it already had. ✕ removes the row.

Add option / Add parameter

Adds a row.

Returns

The one value handed back: Nothing (default), Number, Text, Yes / no, List, Match or Coordinate. The flow produces it by setting a variable named return; the caller receives it through Store result as.

Cancel / Apply

Apply keeps the changes for Save task; Cancel drops them.

Declared inputs also appear as fields in the Run flow on emulator dialog, so you can test a routine with real values.

How it runs

When an instance adds the task, its plan row starts from these defaults; the plan can change them for that instance.
A Chore runs on its Default schedule. A Background watcher runs whenever nothing else needs the screen and gives way when other work is due. A March task runs whenever enough march slots are free. A Manual task runs only when you start it.
A goal counts the units reported by Report progress, per game day or forever, and the plan stops offering the task once it is reached.
Requires buildings holds an instance back until its city is mapped; the readiness check names what is missing.

Examples

A once-a-day reward collector: Nature Auto (detected as Chore), Default Daily at server reset, nothing under Advanced.
A task that sends two marches: Nature March task - sends marches; Advanced: Marches used 2, March time 90.
A routine that walks to a building: Parameters row Building · Text · blank default; Returns Yes / no; the flow sets return to true on arrival.

Troubleshooting

The Goal row is missing.

It appears only when the flow has a Report progress step. Add one where a unit of work is done.

Detected says Chore, but my task loops for ever.

Detection looks for a Loop until… step. A loop built another way is not detected: choose Background watcher - always on yourself.

The Default row is missing.

It is shown only for the Chore nature. The other natures follow their fact line.

My task vanished from the shelf and from Task setup.

Check Run from Duties only under Where it appears, and the task's toggle in Studio.

My change here did nothing.

Apply only keeps it in the builder. Click Save task to store it.