Reference
Use this section when you know the question but do not need another tutorial. It maps player-facing concepts to native resources, keeps identifier domains separate, and points each structural or runtime claim back to its evidence boundary.
Orientation
| Need | Reference |
|---|---|
| Choose the next practical project or download a checkpoint | Labs at a glance |
| Decode a RED or book-specific term | Glossary |
| Find which resource owns a responsibility | Resource map |
| Distinguish handles, NodeRefs, facts, paths, keys, and numeric IDs | Identifier-domain quick reference |
Graph and condition lookup
| Need | Reference |
|---|---|
| Find a quest/scene node, its sockets, and the lab that demonstrates it | Node and socket index |
| Choose a condition family without confusing a predicate with a waiting node | Condition index |
| Read node IDs, sockets, edges, and colors in the diagrams | Reading graph diagrams |
Registration and data lookup
| Need | Reference |
|---|---|
Build or diagnose a typed journal path and fileEntryIndex | Journal-path reference |
| Trace UI, subtitle, VO, or embedded scene-choice localization | Localization reference |
| Decide what ArchiveXL registers and what the archive reaches indirectly | ArchiveXL registration reference |
| Connect a status to a custom visual on V or an NPC | Entity spawners and status effects |
| Reuse the tutorial naming convention without colliding with it | Tutorial namespace |
Additional references
| Need | Reference |
|---|---|
| Check which labs have been tested in game | Lab status |
| Check the exact pinned practical versions | Tested versions |
| Locate a named vanilla resource to extract and inspect yourself | Vanilla depot paths |
The vanilla index contains depot paths and focused properties. Extract the resources from your own installation when inspecting them.
For failures rather than lookup, start with Troubleshooting.