Teach the loop in the first session
Snapshot
~75 sec
The first session should rehearse the core loop until the player can intend → act → see a result → want another try. A feature tour that delays that rehearsal teaches menus, not a game.
You will learn
- Name what the first sitting must teach about the loop before adding systems.
- Spot a feature tour that postpones the first successful re-entry.
- Rewrite an opening so notice → try → succeed → want-again happens early.
Target outcome
You can design a first sitting that teaches the loop before decorating it with forks and menus.
Visual walkthrough
Visual walkthrough
~6 min
Four beats of a teaching first session
Notice
The player sees one clear invitation to try.
Try
They take one available action without a wall of options.
Succeed
A readable result proves the action mattered.
Want again
Re-entry into the same kind of intent is obvious before new systems appear.
Feature tour versus loop rehearsal
Approach Clarity Time to first success What they remember Show every system firstMenus, currencies, and meta screens appear before a complete loop. The player cannot name the repeating beat. First success is delayed or buried under setup. They remember screens, not a reason to try again. Rehearse the loop earlyOne invented loop completes several times before forks and meta layers expand. The four beats are felt, not only labeled. Success arrives early enough to teach re-entry. They leave wanting another try of the same kind. First sitting teaching chain
Keep the chain short. Each step exists only to make the next beat inevitable.
Notice
One invitation is visible without a feature dump.
invitesTry
One action is available and safe to attempt.
producesSucceed
A result proves the action changed something.
renewsWant again
Re-entry into the same intent is immediate.
repeats asWant again → Notice
Keep the chain short. Each step exists only to make the next beat inevitable. Reading order
- Notice
One invitation is visible without a feature dump.
- Try
One action is available and safe to attempt.
- Succeed
A result proves the action changed something.
- Want again
Re-entry into the same intent is immediate.
Connection explanations
- Notice → Try (invites)
Notice without a try is a billboard, not teaching.
- Try → Succeed (produces)
A try without a readable success does not teach the loop.
- Succeed → Want again (renews)
Success must renew intent of the same kind before new systems arrive.
- Want again → Notice (repeats as)
Want-again only closes the teaching loop when it returns to another clear notice of the same kind.
Audit an opening
A draft first sitting opens with a three-tab meta menu, two currencies, and a daily calendar before the player takes a single core action. What should change first?
Expected reasoning
Cut or postpone the meta layers until the player has completed notice → try → succeed → want-again at least once. Keep one invitation, one action, one readable result, and an immediate re-entry. Currencies and calendars can return after the loop is felt.