Tutorial template

Copy this page into your game's docs, fill in the table, and build it with snippets/tutorial_steps.luau. The reasons behind each rule are in onboarding.md.

1. The step table

Aim for 5 to 7 steps, all of them the core loop. Cut any step that teaches a system the player doesn't need in the first 5 minutes; make it a one-time tip instead.

2. Per-step checklist

For every row:

• Text is one line, ≤ 8 words, no names the player hasn't seen.
• Done condition is checked on the server and counts actions done earlier.
• Goal is absolute (≥ N), not "N more than when the step started".
• Pointer is on the exact button, including inside panels.
• Pointer finds its target by name or attribute, not by list order.
• Pointer never covers the price or the label it points at.
• Wrong panel open → pointer on that panel's X.
• Target off screen → edge arrow. Target gone → fallback.
• If the step waits, the text says so and the pointer moves to the timer.
• No Robux button visible during this step.
• Reward pays once (paid[id]).
• Completion shows a check stamp, a "+$N" line, particles and a sound.

3. Whole-tutorial checklist

• A loading screen from ReplicatedFirst before anything else.
• Intro only on the first-ever join, ~15 s, action only, one tap skips.
• The tutorial fight (if any) is unlosable, decided on the server, and tested on many seeds and army sizes.
• Tutorial locks (no retreat, fixed target) apply only to the tutorial's own fight.
• World events, raids, diplomacy and random popups are off until the tutorial ends, and the next one is pushed a few minutes out.
• The card hides under big banners and popups and returns after a 1 s gap; no stacking.
• Low-cash tip in the counter slot when cash is below the next cost.
• Rejoin resumes the step, and the next tick re-checks it (a stale "win" goes back to "attack").
• Old saves with a different step list are mapped to the nearest new step.
• Skip on the card, with a confirm; skipping shows the done card.
• A done card the player taps, then one-time tips (max one per 40 s, never over a panel).
• After the tutorial, the pointer keeps showing the next good target.
• Robux surfaces stay hidden until ~10 minutes after the tutorial ends.
• Every other file that checks a tutorial step number is listed (raids off while step < X, etc.) and still correct after any change.
• Onboarding funnel steps for every sub-action (analytics.md).

4. Test plan

Run each of these on a fresh save and write down the result: