Studio

The Bundle Editor

Group related jobs that share one way in.

A bundle groups several related jobs that all live behind the same door — the alliance window, an event centre, a daily-rewards screen. Each job is a sub-task: it has its own steps and its own settings, exactly like any other task, but it belongs to the bundle rather than sitting in the library on its own.

What they share is the way in. Instead of every sub-task working out how to reach its screen, the bundle carries one flow that does it for all of them — so you write that navigation once, and fixing it fixes every sub-task at once.

The Bundle Editor — the bundle’s own details, then one card per sub-task.

Open it from the Studio library: New bundle asks for a name and creates an empty one, or Edit a card that carries the Bundle chip. The hub has a name field, a Save bundle button, and a Form: pill showing whether the settings form is auto-generated or hand-designed (click it to reset back to auto).

Three surfaces

Manage sub-tasks — add, reorder and remove them. Each carries a name, a key (the short name the bundle flow uses to tell them apart — e.g. crazy_eggs), whether it is on by default, and a repeat count. On the hub, each sub-task card has Edit flow and Edit settings form.
Design bundle UI — the bundle's own settings form, built in the same drag-drop Config UI designer as any task. Left alone it is generated from the sub-tasks; designing it yourself flips Form to Custom.
Edit bundle flow — the shared flow, edited in an embedded Task Builder. It receives request (what is being asked — normally open, and exit when everything is done) and target (the key of the sub-task being opened). If it cannot get there, it says so by setting a variable named return to not_found — and that sub-task is skipped and reported as a failure, rather than running on whatever screen it happened to land on.

Moving between surfaces harvests your work back into the bundle; one Save bundle writes the whole thing back as a single ordinary task.

Adding a bundle to a plan

You schedule the sub-tasks, not the bundle. A bundle's chip on the Duties tab opens its sub-tasks as a checklist, and every one you tick becomes its own plan row with its own timing — so you can run one of them hourly and the rest once a day. Each appears under its own name everywhere: the plan, the activity feed and the reports. In Task setup you will see the sub-tasks that actually have settings; ones that take no configuration are simply not listed. That is how Alliance Helper works.