Instances & workspace

Profiles

Save a whole account's setup, apply it to many, and carry it between PCs.

A Profile is one account's whole setup, saved under a name and pushed onto as many other accounts as you like — the “set one instance up, then copy it to the rest” workflow. It travels by task name, so it works across different accounts, and it travels with your Evonex account, so it works across different computers.

The Profiles dialog — your profiles on the left, and on the right what the selected one holds, who follows it, and whether this instance is one of them.

Opening Profiles

Open it with the profile chip on the Task setup tab. It opens with the account you're in already picked, so Save and Apply default to it.

What a profile carries

A profile is the whole setup of an account, in three parts, and the dialog shows you a count for each before you apply anything:

Task setup

Each task's option values — the settings-form answers, keyed by task name.

Duties

Every row on the Duties board: which are switched on and how each one is configured.

Scheduling

Each task's rhythm — how often it runs, its goal, its stop rule.

It also carries the City map this account uses, so an account restored from a profile knows how to walk its own city.

What a profile deliberately does not carry is the plan layer: whether a task is switched on, its role, and its order. Applying a profile never touches those, and a task the instance does not have yet is added switched off — so its options are in place and nothing starts running by surprise. Duties are the exception: the profile wins for every duty it names, including switching one off, because "my setup, on this bot" has to mean a full restore.

Binding, and other computers

A profile can be bound to an instance. A bound instance follows its profile: save a change to the profile and every instance bound to it is brought up to date, and a running bot says so in its own Activity log rather than changing behaviour silently.

Profiles travel with your account, not with the PC, so a profile saved on one computer appears on the next one you sign in on — and so does the binding. Bind an instance here and the same account on another machine picks that binding up on its own. That is also what makes a profile the way to carry a setup through a reinstall.

Saving and binding

New profile from this instance saves this account's task setup, duties and scheduling under a name you give it.
Select any profile to see what it holds — Task setup, Duties and Scheduling, each with a count you can open — and which instances are already using it.
Bind to this instance makes this account follow that profile. It replaces the account's task setup, duties and scheduling, so the dialog asks you to confirm first.
While an account is bound and you have changed something on it, the profile offers Save to profile (push your change up, to every account that follows it) or Discard changes (take the profile back down).
Unbind stops the account following it. Its settings stay exactly as they are — unbinding changes nothing in the game.

Copy from another profile brings one profile's parts into the one you are looking at, so you can build a new setup out of two you already trust instead of starting again.

Binding leaves the plan alone: each task's options, rhythm and duties come across, while the account's on/off state, roles and order stay as they were. A task the profile carries but this account doesn't have yet is added switched off; a task not in the library at all is skipped, and the dialog names it rather than hiding it.