A quest is a goal a player works through: an audience, a window, some tasks and a reward. In the studio you build it as a circuit: blocks connected from left to right, which you can read at a glance.
The six gates
- 1Who: the audience. Everyone, or players matched by id or by traits your site sends (plan, country, signup date).
- 2Appearance: conditions that must be true first, like having finished another quest, and how players join: automatically, or by pressing Start.
- 3When: an optional window with a start and an end, chosen days of the week (a Tuesday sprint), or rounds that repeat every N days or weeks. Each round starts over: progress resets and the quest can be finished again.
- 4What: the tasks.
- 5Completion: how players finish: automatically, or with a claim the player confirms.
- 6Rewards: what finishing pays. See points, badges and perks.
How tasks combine
Inside What (and Appearance), blocks combine tasks:
- All: every task, in any order.
- Any: one of them is enough.
- At least N: any N of them.
- One by one: in order. Each step only counts what happened after the step before it was done.
Blocks nest, so "the tutorial, then any two of these three challenges" is one circuit.
A player's quest
For each player, a quest is available (they may join), active (joined), ready (tasks done, waiting for them to claim it), completed, expired (the window closed first) or closed (you archived it). Your site gets the state, each task's progress like "2 / 5", and the rewards, in one call.
Try before you publish
The studio's Try it panel runs the draft on Luk Quest's real evaluator: pick traits, add events, and watch each gate pass or wait. A preview shows the quest the way the API will describe it to your site.
Next: publishing and versions.