Studio

The Bundle Editor

Group related jobs that share one way in.

A bundle is one task that owns several sub-tasks: related jobs behind the same door, such as the tabs of one event window. Each sub-task has its own steps and its own settings form, and each is scheduled on its own. What they share is the way in: one bundle flow that gets any of them onto its screen, so the navigation is built once.

NeedsStudio open on the Tasks tab

Open it from Studio ▸ Tasks: New bundle creates one (see The Studio library), or click a card with the Bundle chip. Built-in bundles such as Alliance Helper and Event Center open here too.

The Bundle Editor hub: name, Form pill and Save bundle, the three editors, and one card per sub-task.

Set it up

In Studio ▸ Tasks, click New bundle, name it (for example Event rewards), choose Runs as and click Create bundle.
Click Manage sub-tasks, then Add sub-task for each job, such as Daily chest and Login reward. Leave the keys blank to derive them from the names, and click Done.
Click Edit bundle flow and build the way in: open the event window, then an If / Else per key that taps that sub-task's tab. Click Back to bundle.
On each sub-task card click Edit flow to build its steps, and Edit settings form if it needs settings. Click Back to bundle.
Click Save bundle.
On an instance, open Duties, click the bundle's chip on the Tasks shelf, tick the sub-tasks you want and click Add.

The hub

Studio

Back to the library. With unsaved changes it asks Discard changes? (Discard or Cancel).

Bundle name

The name field. An empty name saves as Untitled Bundle.

Form: Auto / Form: Custom

Whether the bundle's own settings form is generated from its sub-tasks (Auto, the default) or designed by you (Custom, set when you come back from Design bundle UI). Clicking the pill while it reads Custom asks Reset bundle UI?; Reset discards the designed form and returns to Auto.

Save bundle

Saves everything as one task: sub-tasks, their flows and forms, the bundle flow and the bundle form.

Manage sub-tasks

Opens the Bundle sub-tasks dialog described below.

Design bundle UI

Opens the bundle's own form in the Config UI builder, titled Bundle UI — per-instance form.

Edit bundle flow

Opens the shared flow in the flow editor, titled Bundle flow — the shared way in, with a guide line above it.

Sub-task cards

One per sub-task, in order: its name; its key (tooltip The target key the bundle flow branches on.); repeats ×N when Repeat is on; off by default when On by default is off; and Edit flow and Edit settings form. With none yet: No sub-tasks yet — use “Manage sub-tasks” to add one.

Bundle sub-tasks dialog

It opens with The tasks this bundle runs, in order. Each row is one sub-task; with none it reads No sub-tasks yet — add at least one.

Name

The sub-task's name, as it appears on the plan, in the activity feed and in reports.

key (auto)

The target the bundle flow branches on. Leave it blank to derive it from the name. What you type is shown back in its stored form, lower case with underscores, such as daily_chest. Keep it unchanged when you rename the sub-task.

On by default

Ticked sub-tasks start ticked when a player adds the bundle to a plan, and are on in the generated form. Default: on.

Repeat · ×N

Repeat lets the sub-task run several times per visit; ×N (1–99, default 1) is the starting count, which players change with Do this many times on Task setup.

Move up / Move down / Remove

Reorder the sub-task, or remove it. A removed sub-task's steps and form go with it when you save.

Add sub-task

Asks for a Sub-task name (placeholder e.g. Open alliance chest) and adds it with Create. A name already in the bundle shows Name in use.

Cancel / Done

Done applies the list to the hub; nothing is stored until Save bundle. When two sub-tasks would answer to the same key, Done shows Two sub-tasks share a key and stays open.

The Bundle sub-tasks dialog: name, key, On by default, Repeat ×N and the row buttons, for a bundle with two sub-tasks.

The bundle flow

The bundle flow is the one place that knows how to reach each sub-task's screen. Before a sub-task runs, Evonex runs the bundle flow with two variables, and reads a third back:

request

What is being asked: open before a sub-task runs, exit after the last one. A sub-task's own steps can also call the bundle flow with a request of your own.

target

The key of the sub-task being opened; empty for exit.

return = not_found

Set this to refuse: I couldn't get there. The sub-task is skipped and reported as failed, instead of running on the wrong screen.

return = skip

Set this when the screen is absent for a game reason, such as an event not running this week. The sub-task is skipped and reported as skipped, not as a failure.

Anything else

The sub-task runs. An empty bundle flow lets every sub-task run.

Set return with a Set variable step whose Scope is Function. With Scope Local inside an If, the value is thrown away when the branch ends and the sub-task runs anyway. The Return value step does not work here.

After a sub-task, the bundle checks what runs next. If another sub-task of the same bundle is next, it leaves the window open for it; otherwise it runs the bundle flow with exit so you can close the window.

Editing a sub-task or the bundle flow

Edit flow and Edit settings form open the sub-task's steps and its Config UI tab under the title name — sub-task. The Steps panel, Inspector and Log with Run flow work as in The Task Builder; the top bar and New function are not shown. A sub-task's steps can use Call function to run the bundle flow with any request. Back to bundle keeps your edits in the hub. Run flow here tests a private copy and does not save the bundle.

Adding a bundle to a plan

You schedule the sub-tasks, not the bundle. On an instance, open Duties and find the bundle on the Tasks shelf: its chip shows how many sub-tasks are already in the plan, such as Event rewards 1/2 …. Clicking it opens Add from Event rewards: tick sub-tasks and click Add, which counts them. Sub-tasks already in the plan show (in plan); ones with settings prepared on Task setup show (configured). Each becomes its own plan row with its own schedule. On Task setup, each sub-task that has a settings form or has Repeat on gets its own card.

Some built-in bundles, such as Alliance Helper and Event Center, are run from cards on the Duties page and have no chip on the shelf.

How it runs

A plan row runs one sub-task: Evonex runs the bundle flow with open and that sub-task's key, then, unless it refused, runs the sub-task's steps (as many times as its count when Repeat is on).
A refused or skipped sub-task still gets an activity row, marked failed or skipped.
Afterwards the window is left open for a sibling that runs next, or the bundle flow runs with exit.
Switching the bundle's Studio toggle off stops every one of its sub-tasks.

Examples

Event tabs. Sub-tasks Daily chest (key daily_chest) and Login reward (key login_reward). Bundle flow: find the event icon; if it is not found, Set variable return = skip with Scope Function; otherwise tap it, then an If per key that taps the right tab.
One sub-task hourly, the rest daily. Add both sub-tasks from the checklist, then set Help to every hour and Gifts to daily on the plan.

Troubleshooting

A sub-task ran on the wrong screen.

The bundle flow did not refuse when it could not reach the target. In that branch, Set variable return = not_found with Scope Function.

My refusal is ignored and the sub-task still runs.

return was set with Scope Local inside an If, or with the Return value step. Use Set variable with Scope Function.

The bundle has no chip on the Tasks shelf, or the chip is greyed out.

Check the bundle's toggle in Studio. A greyed-out chip means every sub-task is already in the plan.

A sub-task has no card on Task setup.

Only sub-tasks with a settings form, or with Repeat on, get a card.

How do I test only the bundle flow?

Open Edit bundle flow, go to Log ▸ Run flow, set Start at to the bundle flow function and add the arguments request = open and target = a sub-task key.