Easy Chapter Generator
EnglishEspañol

Practical guide: transition to another scene and Chapter

  1. 1
    Add the destination scene to Build Settings and ensure it contains one ChapterManager.
  2. 2
    On the source Chapter, choose Load Scene and Start Chapter.
  3. 3
    Select the target scene and the exact Next Chapter. Use Restore Checkpoint instead only when a destination Objective is required.
  4. 4
    Subscribe short cleanup work to OnBeforeSceneLoad if needed.
  5. 5
    Complete the source and verify the destination handoff overrides its Editor testing and default selections once.

Use Load Scene with no Chapter handoff when the destination should deliberately use its normal startup rules.

Practical guide: reuse a project-specific Objective subclass

Create a detector derived from Objective, serialize only the mechanic's configuration, and call RequestObjectiveCompletion() when the authoritative condition becomes true. Override ResetObjective() to clear every transient field and call the base implementation. Add the component to each relevant Objective container and use Objective Link to choose the local Ordered Objective.

The same class can be reused in both source and destination scenes because progression identity is serialized per component. Do not hard-code a global Objective ID inside the class.

Example: repair a portal, then cross scenes

  1. 1
    Use a custom RepairNodesObjective to count repaired nodes and complete the final row of the source Chapter.
  2. 2
    Configure that Chapter to load the destination scene and start chapter_portal_exit.
  3. 3
    In the destination, link another instance of the same custom class to a different Ordered Objective if the mechanic repeats.
  4. 4
    Test duplicate repair callbacks, Reset, source completion, handoff consumption, and a later direct reload that should return to normal default startup.

Failure modes

Custom detector works in one scene only

Check the local Objective Link and that each scene's Manager contains the selected Chapter/ID.

Destination starts the wrong Chapter

Validate Next Chapter, store/flush results, and confirm the load goes through ChapterManager.

Old handoff repeats

A valid handoff is consumed and deleted. A custom backend that fails Delete or Flush may violate that guarantee.

Reset retains mechanic state

Stop coroutines and clear counters in the override; scene reconstruction remains project-owned.