Resource map

Use this page to answer two questions before editing a graph:

1. Which resource owns the missing definition or behavior?
2. Which registration or native reference makes that owner reachable?

The Lab 1–5 resources are Structurally validated with WolvenKit 8.19.0. Rows marked Observed in vanilla describe game resources to inspect yourself.

Project and installation layers

The same depot path can appear as a file below source\archive, a ResourcePath inside another CR2W, a registration value, and a runtime log entry. A path below source\raw normally has an extra conversion suffix and must not be registered.

Native control, journal, and scene resources

Important ownership boundaries:

• A questphase journal node changes state at a typed path; it does not define the target entry.
• A root registration does not register external children or scenes as independent quest roots.
• A .scene owns its named contact_done exit; the calling questphase owns the same-named output socket and the continuation after it.
• Termination ends a graph route. It does not automatically clean a marker, community, scene, journal entry, or fact.

See Questphase resource anatomy, Journal trees and typed paths, and Scene resource anatomy.

Localization and audio resources

Several different CR2W resource types use the depot suffix .json. Inspect the root type and registration branch instead of treating the suffix as an ownership contract.

The subtitle map and VO map are registration roots. The subtitle-entry file and WEM are referenced leaves. Registering a leaf where a map is expected does not complete the lookup.

For the complete joins and locale spelling differences, use Localization paths. Lab 5’s externally localized one-line route is explained in Author one spoken line.

World and streaming resources

The compact placed-node chain used by the labs is:

registered streaming block
  -> descriptor.data
  -> streaming sector
  -> concrete nodes[] object
  +  nodeData placement and QuestPrefabRefHash
  +  nodeRefs[] identity registration

The three sector collections are related but not universally parallel. nodeData.NodeIndex is the explicit association in the compact mod-owned shape; array position is not a schema rule. See Sector nodes and placement.

Community and character resources

Lab 5 embeds its community template data in a world registry node rather than shipping a standalone .community resource.

The exact Lab 5 join is developed in Registries and compiled areas and Entries, phases, and AI spots. The advanced chain and its legal-shell boundary are in Character records, entities, and appearances, while AI roles, behavior, and workspots separates actor, role, route, and activity ownership. Never add an extracted vanilla CR2W to a downloadable project.

Referenced world and device surfaces

These owners form the advanced device research model. Their linked procedure is complete as an Experimental authoring and acceptance boundary, not as a generic Runtime-proven custom-device recipe:

See Devices and persistence and Advanced devices and interactions before using any of these surfaces. The current Labs 1–5 do not supply a custom device.

Registration versus native reference

This is the quickest lookup for “which file do I put in ArchiveXL?”

Custom visual effects

The VFX record name, effect CName, component name, and effect depot path are different identifiers. Follow Custom effects to connect them and test the screen and NPC variants separately.

Save-state overlay

Resource ownership and saved runtime state overlap but are not the same layer:

Repacking a definition cannot be used as evidence that the corresponding saved state was reset. Route stale or contradictory retests through Facts, journals, and saves before changing more resource fields.