LOPTR LAB · INTERACTIVE NARRATIVE

The Interactive Track

A practical path from written branching narrative to a playable browser experience — with Ink, state, consequences, playtesting, accessibility, QA, and provenance built into the process.

Play The Yellow Door → Open 50 Ways Writer Path → Support Loptr Lab →

What this is: an independent learning and prototype track. It does not grant repository permissions, contributor status, Discord access, event access, or rights to third-party material.

What you can learn here

Playable case study

The Yellow Door

Study a real Ink narrative with branching choices, state, consequences, convergence, multiple endings, and a browser runtime.

Training

50 Ways Interactive Writer Path

Move from Ink fundamentals through narrative design, production handoff, QA, accessibility, rights, and an original-story exercise.

Cross-reference

Training Integration

See how the Yellow Door case study connects to the broader independent 50 Ways learning pathway.

Source-only study

Ink + Music Pilot

Examine the fictional source-only music/interactive proposal without mistaking it for a released track, player, clearance, or production integration.

The production handoff

Ink source → compiled story data → JavaScript runtime → browser UI

Ink is the writer-facing narrative language; Inky is the authoring/preview environment; inkjs can run compiled Ink story data in a web context. The separation lets writers work on narrative while the browser layer handles presentation. Ink's official web tutorial describes the same general source-to-web workflow, and inkjs documents the browser runtime pattern.

Use cases

Writing

Interactive writer

Choices, knots, stitches, variables, conditional text, convergence, endings.

Design

Narrative designer

Branch shape, pacing, consequence visibility, midpoint reframing, replay paths.

Production

Producer

Source, compile, runtime, versions, handoff records, ownership, delivery.

QA / access

Tester & reviewer

Branch coverage, restart behavior, accessibility, readable choices, regression checks.

One important boundary

The source-only Ink/music pilot is deliberately kept separate from the playable Yellow Door implementation. A story source is not a compiled release; a track brief is not an implemented narrator/audio track; and a streaming link is not rights clearance.

Start small

Map one branching story before changing it.
Make one controlled narrative revision.
Play the affected path and a neighboring path.
Build a small original Ink story with state, consequence, convergence, and two endings.
Record accessibility, QA, and provenance observations.

Enter The Yellow Door → Back to Break the Grid