Troubleshooting & Reference
Support
Prepare a reproducible support request with the minimum project facts needed to diagnose product behavior.
Reduce the problem to one reproducible path
Start with Validation and the focused troubleshooting page. Reproduce in the real project, then in a minimal copy of the affected scene if possible. Determine whether the issue is authoring structure, Runtime acceptance, a project callback, an optional integration, persistence backend, or Demo presentation.
Never send credentials, private customer data, license keys, or an entire confidential project when a small reproduction is sufficient.
Include these facts
- Easy Chapter Generator version and acquisition channel.
- Unity Editor version, operating system, and target platform.
- Render pipeline and whether the issue is Core or Demo-only.
- Exact steps from a clean scene or clean progress profile.
- Expected result and actual result.
- First relevant Console error/warning with full stack trace.
- Manager, Chapter, Ordered Objective, and component types involved; stable IDs may be anonymized consistently.
- Validation result and public state snapshot.
- Optional assets/adapters and their versions.
- Whether the problem survives after disabling unrelated project scripts.
Build a useful reproduction
- 1Duplicate the affected scene and remove unrelated objects in small steps.
- 2Keep one Manager, one Chapter, the minimum Ordered Objectives, and the failing detector or bridge.
- 3Replace third-party presentation with a simple UnityEvent or stub while preserving the failing boundary.
- 4Clear the test profile and record whether the first run and hydrated run differ.
- 5Attach concise logs or a short recording only when they reveal timing that written steps cannot.
Classify the request accurately
| Category | Example | Useful evidence |
|---|---|---|
| Authoring | Missing or duplicate Objective Link | Validation text and selected hierarchy |
| Runtime | Exact active completion rejected | IDs, states, return result, callback order |
| Persistence | Terminal state not restored | scope/profile, backend, operation results, fresh/hydrated sequence |
| Integration | Vendor callback or adapter not invoked | assembly define, adapter type, source callback evidence |
| Demo | Material/controller presentation issue | pipeline and optional package versions |
A clear report receives a faster, safer answer because it identifies which owner can actually correct the behavior.