Easy Chapter Generator
EnglishEspañol

Start Here

Installation

Import the Core safely, decide whether the optional Demo belongs in the project, and verify the first clean compile.

What you will install

The package contains the runtime Core, Editor authoring tools, bilingual offline documentation, and an optional Demo. Keep Runtime and Editor to author Chapters; omit Demo when a production project does not need the example.

Core

ChapterManager, Chapters, Objectives, components, persistence, and the authoring window. Core does not depend on URP, HDRP, Cinemachine, XR, dialogue, or inventory packages.

Optional Demo

A Built-in Render Pipeline showcase. It uses presentation assets and Unity packages that are not part of the Core contract.

Before importing

  • Open the project with a supported Unity version; this release is verified with Unity 6000.3.8f1.
  • Save the open scene and create a backup or commit before importing.
  • Decide whether you need the Demo. If you import it, also install the dependencies listed under Compatibility and Dependencies.
  • Do not copy another project's TextMesh Pro folder. If Unity asks for TMP resources, use Window > TextMeshPro > Import TMP Essential Resources.

Import Core

  1. 1
    Import the download through Assets > Import Package > Custom Package or Window > Package Manager > My Assets, depending on the supplied format.
  2. 2
    In the import list, keep Assets/ChapterObjectiveSystem/Runtime, Editor, and Documentation. Clear Demo if you do not want the example.
  3. 3
    Select Import and wait for Unity to finish compiling. Do not open the product window while the progress indicator is active.
  4. 4
    Open Window > Chapter & Objective System > Welcome. Select Open Chapter & Objectives to verify that the authoring tool opens.
  5. 5
    Open Window > General > Console. The expected result is a clean product compile with no C# errors.

Add the Demo deliberately

Import Demo only when you want to follow the packaged examples. Its showcase scene targets the Built-in Render Pipeline. For Demo controls, set Active Input Handling to Input System Package (New) or Both in Player Settings, then allow Unity to restart if requested. Input System, Cinemachine, and Starter Assets references belong to Demo presentation; removing them from a production project does not change the Core API.

Do not turn the Demo into a game dependency

Copy configuration ideas, not its controllers, cameras, or materials, unless the project already owns those dependencies.

Installation check

The installation is healthy when

  • Window > Chapter & Objective System > Manager opens the authoring window.
  • Create Chapter Manager is available in a scene with no Manager.
  • The Console contains no missing-type, assembly, or disabled built-in module errors.
  • Welcome opens the packaged documentation while offline.

Continue with Ten-Minute Quick Start to author a real sequence.

If import fails

TextMesh Pro is missing

Confirm: the Console names TMPro or a font resource. Fix: install Unity's official package and import TMP Essential Resources.

Demo materials look wrong

Confirm: Core compiles and only the showcase scene is affected. Fix: use Built-in Render Pipeline for that scene or adapt its materials in a project-owned copy.

The menu is absent

Confirm: at least one C# error exists in Console. Fix: resolve the earliest error first; Unity does not load Editors while the domain fails to compile.