Automations

Rule

A named set of stages that watches one pool of accounts.

Stage

One step of a rule, with its own conditions and actions.

Condition and action

A condition is what must be true. An action is what Kovex does when it becomes true.

The setup wizard starts from a template so you do not have to build the logic yourself.

• Move an account to the next category once the tutorial is complete.
• Stop or move an account when it reaches a total level target.
• Stop or move an account when it reaches a quest point target.
• Stop a managed client that has logged itself out, so the slot is reused.

The source category is the pool a rule watches and launches from. A rule can watch every account, but a category keeps behavior predictable.

A stage fires when any of its conditions is true, then runs every action you listed.

A rule can start clients itself, which is what turns it from a watcher into a pipeline.

• Maximum concurrent limits how many accounts one rule keeps running.
• Set the limit to zero to watch already running accounts without launching anything.
• Launch order can be newest first, oldest first, or random.

History is how you audit a rule. Every time it acts on an account, the event is recorded with the stage and the time.

• One-shot per profile makes each account complete a rule only once.
• Fire history lists the most recent events, newest first.
• Resetting history lets accounts qualify again for a one-shot rule.

1. 1Tutorial pipelineWatch a fresh category, auto-launch up to a few clients, and move each account to a ready category when the tutorial completes.
2. 2Level ceilingWatch a training category and stop each client at the total level you sell or use, leaving the account untouched otherwise.