Easy Chapter Generator · OverFuture
Set the tasks, choose their order, and configure what happens when each one starts or finishes. Build linear sequences in the Unity Editor without writing the progression system from scratch.
You can also save it to your Asset Store wishlist.
How it works
Add chapters and define their tasks. Rearrange objectives, set conditions and choose a delay before each step begins.
A button press, reaching an area, placing an object: use the included components or tell the system when your own gameplay code has finished the task.
The editor flags missing assignments, duplicate objective links and incomplete settings, so you can find the affected item before testing your sequence.
See which objective is running, what's already complete and what still needs to happen. Follow the sequence in the editor while you test your game.
Use components for buttons, arrival zones, timers, destruction, object placement and tasks that require several actions. For a different mechanic, build your own component from the Objective base class.
Explore the objective components ↗Use UnityEvents to activate scene objects or call your game's functions when an objective starts or ends. Keep the dialogue, inventory and UI systems you already use.
When a chapter ends, you can also load another scene and choose the chapter or objective to continue from.
Set up actions and events ↗Use cases
A few examples of sequences you could build.
Introduce one mechanic at a time. Wait for the player to finish the current task before moving on to the next.
Use objective events to show the next instruction in your own UI.
Break a procedure into individual tasks so users can practise each step.
Your simulation checks the result and reports when the task can be marked complete.
Put puzzles in order and decide what unlocks when each one is solved.
Change the route through the room by reordering tasks in the editor.
Set up a linear mission that moves between conversations, gameplay tasks and scenes.
For example, your dialogue system can request objective completion when a conversation ends.
| You need to… | Easy Chapter Generator | Your game |
|---|---|---|
| Organize tasks | Tracks the sequence, the active objective and progression to the next step. | Defines what the player needs to do in each chapter. |
| Complete an objective | Provides components and methods for reporting task completion. | Configures the interaction or rule that makes the task complete. |
| Save progress | Stores chapter and objective progress. | Saves player position, inventory and world changes through your save system. |
| Add visuals and controls | Includes a demo for trying the system. | Provides the visuals, camera, movement and UI. |
Open a screenshot to see the controls and configuration warnings in detail.
Review the order, conditions and settings of each task.
Use Objective Link to choose which objective a scene component belongs to.
Find missing assignments and components pointing to the same objective.
You can set up a sequence with the included components and configure its events in the editor without writing C#. If your game needs a custom mechanic, you can add it through code.
Yes. Derive from Objective and request completion when your custom condition is met. You can also use the public API to control progression from other scripts.
It saves completed chapters and completed or skipped objectives. Storage uses PlayerPrefs by default and can be replaced. It is not a full game-save system: player position, inventory and world state are saved separately.
Your game must request the failure. The system marks the chapter and any active objective as failed and raises the relevant events. You decide what happens next, such as showing a screen, restarting or restoring a checkpoint. It does not restart or reload scenes automatically.
It is designed for linear sequences. You can configure many objectives, but a chapter runs them one at a time. Conditions can skip steps; a branching quest editor is not included.
Unity 6.3 LTS and a Built-in Render Pipeline project. The system uses Unity UI/TextMesh Pro. The demo also needs Cinemachine 3.1.7, Input System 1.18.0 and TMP Essential Resources. For the demo, set Active Input Handling to Input System Package (New) or Both.
Yes. The package includes a playable demo and English/Spanish documentation, with a quick start, C# examples and guides to components, saving progress and scene transitions. You can also contact OverFuture for help.
Get the editor, objective components and a playable demo in one package. See the full details on Unity Asset Store.
