Studio

The Studio library

Your shared library of tasks, routines and detectors.

Studio is the app-level library shared by every instance — the subtitle reads Build the bot's tasks, routines and detectors — shared by every instance. A task is a flow: a tree of steps the bot runs top to bottom. Open one (or create one) to edit it in the Task Builder.

The Studio library, on the Tasks sub-tab.

Three sub-tabs

Tasks — everything an instance can run. Each is a card; the All tasks / Main tasks / Side tasks filter narrows the grid by run role.
Routines — reusable sub-flows that tasks (or other routines) call. They never appear in pickers or plans, so they carry no enable toggle.
Vision Lab — tune and save the detectors task steps look for (its own page: Vision Lab).

A task card

Each card shows the task's name, a Main / Side / Bundle chip and a one-line summary. Click the card (or Edit) to open it; the trash button deletes it. The toggle in the top-right corner enables the task (tooltip: Enabled — offer this task in instance setup).

A disabled task is hidden from every instance's Task setup and skipped at run time everywhere. You can't disable a task while a running instance still has it in its plan; Studio names those instances and asks you to stop them first.

Built-in tasks and routines

The tasks and routines that ship with Evonex can be edited freely — your edits stick — but they can't be deleted (deleting one shows a notice instead). Everything you rename, delete or bundle here shows up in any open instance's plan and Task setup immediately, no restart needed.

Bundle tasks

Bundle tasks (on the Tasks sub-tab) combines several tasks into one — you name it, pick Runs as Main or Side, tick the tasks to include, and Create bundle opens it in the Bundle Editor. A bundle stays "just one task" in the library and in plans.

Test before you rely on it

To try a task against a real emulator before you schedule it, open it and use Run flow in the Task Builder — a single run against a chosen device, with full logging, and your test inputs standing in for a player's settings.