Easy Chapter Generator
EnglishEspañol

Authoring

Create and Organize Content

Create, rename, duplicate, reorder, and delete Chapters and Objectives while preserving stable identifiers and Undo.

Create a Chapter from the product window

  1. 1
    Select the scene ChapterManager in the object field at the top of the window.
  2. 2
    Open Chapters and press Add Chapter. The tool creates the owned scene component, adds it to the Manager, and selects it.
  3. 3
    Set a concise Title. Keep the generated Identifier unless you have a naming convention to apply before any scene link or saved build exists.
  4. 4
    If this should be the fallback, return to Manager > Progression Defaults and choose it in Default Chapter.

Use the window's structural buttons rather than manually moving Chapter components between GameObjects. The commands record Undo, maintain the Manager array, and preserve a coherent selection.

Build and reorder the sequence

  1. 5
    Select the Chapter row and expand Ordered Objectives.
  2. 6
    Press Add Objective. Edit Title; treat Identifier as a permanent integration key.
  3. 7
    Use Move Up or Move Down to change execution order. The current selection follows the moved entry.
  4. 8
    Use Duplicate for a similar lifecycle configuration, then relink or create the scene detector for the new generated ID.
  5. 9
    Use Delete only after checking scene components that may still link to the row. Undo immediately if the deletion was accidental.

Attach detection only when needed

An Ordered Objective does not require a scene component if a UnityEvent or external script can complete it directly. When the mechanic is spatial or reusable, create or select the generated Objective container, add the appropriate component, then use Objective Link > Select Chapter and the assisted Objective selector. A healthy inspector reports Linked.

One Ordered Objective should normally have one authoritative detector. Several scripts may cooperate through a single MultiActionObjective, but accidentally duplicating two components with the same ID produces competing signals and a validation warning.

Validate the authored structure

Before Play Mode

  • The Manager has unique non-empty Chapter IDs and a valid default.
  • Every Chapter has at least one meaningful Ordered Objective.
  • Objective IDs are unique within the product scope and match their intended scene links.
  • Each row has a completion path: event, external call, included component, or custom Objective.
  • Required references for actions and completion transitions are assigned.

Open Validation and press Refresh. Double-click an issue to select its owner, correct the underlying field, then refresh again. “No Issues” means the structural checks passed; it does not prove that project callbacks or third-party systems emit their runtime signals.