Full Faith

What needed solving.

A long narrative campaign needs reliable mission progression, dialogue import, save compatibility, and enough visual consistency to make scenes navigable.

1. 01Screenplay + mission definitions
2. 02Unity scenes + validated resources
3. 03WebGL campaign checkpoint

Simplified from the implementation and project notes.

How it fits together.

The source screenplay is retained separately from imported dialogue and mission definitions. Unity runtime systems handle perspective changes, conversations, combat, rescue, investigation, and ship operations. Scene resources contain authored navigation, lighting, and action anchors.

The campaign build path validates resources and active settings before export. A documented checkpoint preserved the save format while revising materials, furniture, character shading, and lighting across locations.

Browser regression runs use ordinary player inputs directed by read-only observations. Separate recordings without those observations check representative interactions. This separates progression verification from a claim about unaided player usability.

Building and checking it.

The pipeline imports and checks screenplay data, generates or imports assets, validates scene resources, builds WebGL output, and retains checkpoint hashes for rollback.

The checkpoint notes distinguish targeted runs on changed systems from an older full-campaign run. Keeping that distinction prevents a narrow regression pass from being described as a fresh end-to-end playthrough.