Build a playable sequence
Start with the ten-minute tutorial. You will create two ordered objectives, give each one a visible result, and verify the active state in Play Mode.
Build the first sequence
Start Here
Easy Chapter Generator
Clear linear progression for Unity projects
Author deterministic chapter and objective sequences in Unity, then connect scene interactions through components, UnityEvents, or a small public API.
Choose the route that matches your job
Understand the model
Read how one Manager owns Chapters, how each Chapter advances a single ordered position, and how scene components request—not own—completion.
Understand the system modelIntegrate a mechanic
Choose an included Objective component or derive from Objective. The reference explains fields, runtime behavior, reset, validation, and public calls.
Diagnose a problem
Begin with the visible symptom, confirm the actual state, and apply a bounded correction without recreating the progression graph.
Open Common ProblemsWhat Easy Chapter Generator owns
ChapterManagerselects the Chapter and coordinates persistence, failure, audio, and scene handoff
Chapterowns one linear sequence and its completion policy
Ordered Objectiveowns identity, eligibility, lifecycle actions, and state
Scene component / UnityEvent / project codedetects the game-specific condition and requests completion
The product deliberately stops at progression ownership. Your project continues to own input, dialogue, inventory, movement, save-game data, camera behavior, and visual presentation. Integrations connect those systems through UnityEvents, the public C# API, or small adapters; they do not introduce a second progression controller.
What you can build
- Linear missions, tutorial steps, escape-room sequences, training scenarios, and narrative Chapters.
- Objectives completed by UI, triggers, timers, object placement, destruction, arrival, combined signals, or project code.
- Start and completion actions that activate objects, call UnityEvents, or delegate transport without coupling Core to a movement asset.
- Explicit failure and restart policies, deterministic scene-to-scene handoff, and lightweight terminal progress.
- Custom Objective components that preserve the same authoring, linking, validation, and reset workflow as the included types.
Recommended first session
Install Core, complete the ten-minute tutorial, then inspect the Demo only after you understand the authoring window. That order makes it clear which behavior belongs to the product and which behavior is presentation supplied by the sample scene.
Core, Demo, and optional integrations
| Area | Included responsibility | Not implied |
|---|---|---|
| Core | Runtime progression, editor authoring, validation, persistence contract, built-in Objective components | No render-pipeline, XR, dialogue, inventory, or pathfinding dependency |
| Demo | A guided Built-in Render Pipeline showcase and diagnostic route | Not a production controller framework and not required by Core |
| Add-ons | Adapters discovered through public interfaces | No bundled third-party code or automatic package installation |
Continue to Installation for package boundaries, or go directly to Your First Complete Sequence if the package is already imported.