lennartandClaude Opus 5
bb0f2b760c
No project code is in Assembly-CSharp any more. Five assemblies: Core (no dependencies), Locomotion.Math, Skills, Game (everything else under Scripts), and StarterAssets. Game is one assembly rather than one per area, which is what the plan assumed. Measuring the dependency graph first found three cycles, all through UI — CharacterPanelView reaches into Dialogue, PlayerControlLock into Player, and UILayerBootstrap into Cinematics — plus two edges a using-scan cannot see, because NPCStandIn is in the global namespace. Assemblies cannot be circular, so splitting further means relocating those three files. That is a code-movement task, not an asmdef task, and nothing needs it yet. StarterAssets had to get an assembly of its own. It had none, so it lived in Assembly-CSharp, and an asmdef assembly cannot reference the predefined assemblies — four runtime files use it, and all four would have stopped compiling. The payoff is immediate: BootstrapTests no longer needs reflection to reach NPCStandIn and CinemachineFollowsPlayer, which is exactly why Phase 3 wanted this. Assets/Editor/PlayerBuild.cs is the headless build entry point. It reads the enabled scenes, asserts Bootstrap is scene 0 because the player opens scene 0 on launch, honours the -buildOutput the CLI forwards from -o, and calls EditorApplication.Exit(1) on anything short of Succeeded — without which Unity exits 0 on a build that produced nothing and CI goes green on it. Verified end to end: a 172MB .app in about two minutes. Two renames, both different from what the plan described. DialougueSkillComparison.cs contains a class called SkillFunctions — the filename never matched the type, so it is now SkillFunctions.cs. The two .yarn files with spaces in their names lost the spaces rather than becoming kebab-case, which would have made them inconsistent with Bartender.yarn and SC101.yarn; spaces were the actual problem. Both renames preserved their .meta GUIDs, and the yarnproject graph keys and the two character sheets were updated. EditMode 42/42, PlayMode 5/5, YarnCheck 9 files / 35 nodes, make build green. Co-Authored-By: Claude Opus 5 <[email protected]>
Writing — start here
This directory is the writing surface for Nightclub Arcadia. Everything a session needs
to write or revise dialogue lives here or in Assets/Dialogue/. You should not need to open
Unity, edit C#, or touch a .asset file to write a scene, a character, or a branch. If a
writing task seems to require any of those, that is a pipeline bug — say so rather than
working around it.
Read in this order
| # | File | What it gives you |
|---|---|---|
| 1 | STYLE.md |
The register, the five tone moves, the ban list, the rules that govern branching. Re-read before every session. |
| 2 | YARN-PRIMER.md |
The one page of Yarn syntax you actually need. |
| 3 | voices/ |
The eleven skill voices, one sheet each. Who they are and how they talk. |
| 4 | characters/ |
The named NPCs. |
| 5 | scenes/ |
Per-scene briefs — intent, beats, constraints. Not the dialogue. |
| 6 | GLOSSARY.md |
In-world terms, and where the deep lore lives. |
Where the words actually go
Playable dialogue lives in NightclubArcadia/Assets/Dialogue/, not here:
Assets/Dialogue/
├── Common.yarn every <<declare>>, project-wide. Never played. Add new flags here.
├── Commentary.yarn passive skill barks, one node per (context, voice)
├── Scenes/ SC101, SC102, Debug
├── Characters/ Bartender, Bradford Kane, Chevalier Cassian Thal
└── Objects/ Chair
A new .yarn file anywhere under Assets/Dialogue/ is picked up automatically — the Yarn
project globs **/*.yarn. Adding a scene or a character needs no registration step.
This directory holds the context; Assets/Dialogue/ holds the content. Keep it that way:
never paste dialogue into a sheet here, and never paste a character bio into a .yarn file.
Check your work before handing it back
From the repo root:
cd tools/YarnCheck && dotnet run -- ../../NightclubArcadia/Assets/Dialogue
That compiles every Yarn file and reports errors with line numbers. It needs only the .NET 9 SDK — no Unity, no licence, no Editor. Run it after any dialogue change.
You can also play a node from the terminal, choosing options by number:
dotnet run -- ../../NightclubArcadia/Assets/Dialogue Bartender_Talk 2 2 0 0
Leftover picks restart the node, which models the player walking away and coming back.
One thing that will confuse you. YarnCheck stubs the engine's commands, so
<<check>>never runs and$check_resultis alwaysfalse. Every check-gated branch will show you its failure side. That is the harness, not a bug in your writing. To read the success prose, read the file.
If you edited a voice sheet in voices/, also run:
python3 tools/writing/sync_voices.py --check
What is yours, and what is not
Yours — edit freely: everything in writing/, every .yarn file, the <<declare>> lines
in Common.yarn, and the prose fields of Assets/Candidates/candidates.json.
Not yours — ask an engineer: any .cs file, anything under Assets/Editor/, any
.asset / .prefab / .unity / .meta file, and ProjectSettings/. The implementations
of Yarn commands are code; using them is writing.
The deeper design material
The full design documents live in Obsidian, not in this repo, and remain the authoring home for design work:
~/Obsidian-Vaults/obsidian-vault/Projects/Active/NightclubArcadia/
[[Mystery Writing Handbook]]— the full reference.STYLE.mdis a dialogue-facing digest of it.[[Skill System Draft]]— the Skill Bible.voices/is generated from the shipped subset.[[Candidate System — Design Explanation]]— the three identity readings.[[Lorebook]],[[Timeline notes]],[[Divergence Point Analysis]]— world and history.[[Character Sheet Handbook]]— the full character schema.characters/_TEMPLATE.mdis its dialogue-facing subset.
[[Ground Truth]]is the solution document. Do not copy it, quote it, or summarise it into this repo — not into a sheet, not into a comment, not into a commit message. The game's central premise is that the protagonist's identity never resolves; a copy of the answer sitting in a git history is how that leaks. If you need to know whether something contradicts the solution, ask, and keep the answer out of the files.