Easy Chapter Generator
EnglishEspañol

Core compatibility boundary

Core has no direct dependency on URP, HDRP, XR, Cinemachine, a dialogue system, inventory, pathfinding, waypoint tools, or a third-party inspector. Runtime progression uses Unity scene components, UnityEvents, scene loading, PlayerPrefs by default, and TextMesh Pro only in the included TimedObjective display field.

This release is validated in Unity 6000.3.8f1. Treat support for another Editor version as something to test in a copy before upgrading a production project.

Core, Demo, and integration matrix

DependencyCoreDemo or optional use
Built-in Render PipelineNot required by progression codePackaged showcase presentation target
TextMesh ProTimedObjective can display TMP_TextImport official TMP Essentials when UI needs it
NavMeshOptionalWalkTo path preview only; arrival works without a path
Input System / controller packagesNoDemo presentation may use project/sample controls
Path or NPC assetNoConnect through IPathMovementAdapter or INpcRouteAdapter
Save systemPlayerPrefs defaultCustom IProgressStore adapter for progression keys

Integrate optional assets safely

  • Keep vendor types in a project integration assembly, not in Core.
  • Implement the public adapter interface or forward a confirmed callback.
  • Use scripting defines or assembly references so absence of the vendor does not break compilation.
  • Do not redistribute vendor code, media, samples, or branding with this package.
  • Test adapter absence, invalid references, accepted calls, repeated calls, reset, and scene unload.

Render pipeline and Demo presentation

The documentation contains no pipeline-dependent screenshots or required media. The Demo scene is a presentation layer and may require material conversion if copied into another pipeline. Perform conversion in a project copy and never treat pink Demo materials as a progression failure.

For installation boundaries see Installation. For movement adapters see Movement and Route Adapters.