Studio

The Studio library

The shared library of tasks, routines and detectors every instance draws on.

Studio is where the bot's work is built, and it is shared by every instance. A task is something an instance can run: a flow of steps the bot follows from top to bottom. A routine is a reusable piece of flow that tasks call. A detector is a saved instruction for finding something on the screen or reading a number, which steps use by name.

Aurora and Prism head the page with Studio, the line Build the bot's tasks, routines and detectors — shared by every instance. and the tabs Tasks, Routines and Vision Lab. Standing Watch draws Studio as a desk under one head band: STUDIO, the three tabs as square icon keys, and the same line at the right. While a task is open in an editor on a wide window, Standing Watch also keeps the library beside it as a column on the left — one row per card, with New task (or New routine), the role filter and New bundle — and clicking a row there leaves the editor the way Studio does.

123456789123456789123456789

1. Tasks tab
2. Role filter
3. New bundle
4. New task card
5. Enable toggle
6. Main / Side chip
7. Bundle chip
8. Edit
9. Delete (trash)

1. Tasks tab
2. Role filter
3. New bundle
4. New task card
5. Enable toggle
6. Main / Side chip
7. Bundle chip
8. Edit
9. Delete (trash)

1. Tasks tab
2. Role filter
3. New bundle
4. New task card
5. Enable toggle
6. Main / Side chip
7. Bundle chip
8. Edit
9. Delete (trash)

Start a task of your own

1. On the title bar, click the Studio icon, just after the Calculator icon. The Tasks tab opens.
2. Click the New task card, the first card in the grid. The Task Builder opens with an empty flow named New task.
3. Add steps from the Steps panel, click Save task, name the task, choose Runs as, add a description and click Save.
4. Click Studio at the top left to come back. Your task has a card, and its toggle is on.
5. On an instance, open Duties and click the task's chip on the Tasks shelf to add it to the plan (see The task plan).

The library page

A task card

Built-in tasks and routines

Every task and routine that ships with Evonex has a card here and opens like your own. An edit you save to a built-in is used by every instance on this PC until the next update of Evonex: the first time a new version starts, every built-in task and routine is put back the way that version ships it. Built-ins cannot be deleted. A few built-in tasks that are run entirely by a duty card, such as keeping a bubble on the keep, are not listed in Studio.

New bundle dialog

The dialog explains: A bundle groups tasks that share one way in — open the window once, then hop between its tabs. Each sub-task is scheduled on its own in an instance's Task plan.

123123123

1. Name
2. Runs as
3. Create bundle

1. Name
2. Runs as
3. Create bundle

1. Name
2. Runs as
3. Create bundle

How it works

• Studio edits the one shared library. Saving, renaming or deleting a task updates every open instance's Tasks shelf and Task setup at once.
• Each instance keeps its own settings for a task (what you fill in on Task setup), so one task can run differently on every account.
• A switched-off task is skipped wherever it would run: from a plan, from a duty card, or from another task's Run task step.
• If you quit Evonex with unsaved changes in the Task Builder or Bundle Editor, it asks Studio has unsaved changes — quit without saving them? (Discard & quit or Cancel).

Examples

• Try a task on one account first. Build Close event popup, save it, and add it only to the plan of Northwatch. Silverpine and Ember Keep are untouched until you add it to their plans too.
• Pause one of your tasks everywhere. Stop the instances that run it, switch its card toggle off, then start them again. Its plan rows stay put and pick up again when you switch it back on.
• See only your main-lane tasks. Set the filter to Main tasks.

Troubleshooting