Lab 3: Boundary Check

Lab 3 connects a registered questphase to mod-owned world streaming. The player follows a journal map pin to a checkpoint, enters a smaller trigger, then leaves a wider trigger to complete the quest.

Implementation status: both supplied checkpoints are Structurally validated after all twelve checkpoint CR2W resources were cooked and serialized back with WolvenKit 8.19.0. Their native types, graph, NodeRef chain, sector placement records, outline buffers, journal paths, and block descriptors are exact. The test chapter checks mounting, streaming, marker/GPS presentation, trigger behavior, and save/reload behavior in game.

Follow Author Boundary Check in WolvenKit to expand the start checkpoint. Then use Test Boundary Check to bind the candidate, saves, visible observations, and logs.

What the lab demonstrates

The quest uses state-shaped trigger predicates so reloads on either side of a boundary are testable:

entry -> completed == 0?
  True  -> activate quest, phase, reach objective, and pin
        -> wait until player IsInside the 25 m reach volume
        -> retire pin, succeed reach, activate leave objective
        -> wait until player IsOutside the 110 m leave volume
        -> succeed leave and phase -> completed = 1 -> succeed quest -> end
  False -> end

IsInside and IsOutside are not synonyms for Entered and Exited. The former describe current state; the latter describe a transition event. Vanilla resources contain all three shapes, but the behavior of this new combination still needs its own runtime evidence.

Prerequisites and downloads

Complete Lab 1 and read:

• Streaming model;
• Quest prefabs and NodeRefs;
• Sector nodes and placement;
• Triggers and areas;
• Markers and navigation.

Use Cyberpunk 2077 2.31a for Windows (GOG), WolvenKit 8.19.0, ArchiveXL 1.27.0, RED4ext 1.30.0, and redscript 0.5.31.

• Download the start checkpoint. It has the entire mod-owned world scaffold and a two-node terminating phase.
• Download the completed checkpoint. It has the same scaffold and the exact 16-node quest graph.

Do not install the two checkpoints together. They register the same six depot paths. Use an untouched save created before either was first installed.

Resource ownership

ArchiveXL registers the block, not its two sectors separately. Descriptor data paths make the sectors reachable from the block.

The root questphase declares one local prefab root:

#cqa003_pr_boundary

The world records use its mod-owned full form:

$/mod/cqa/cqa003/#cqa003_pr_boundary

Nested references are:

#cqa003_tr_reach
#cqa003_tr_leave
#cqa003_mp_checkpoint

The quest graph uses the local trigger refs because its root declares the prefab. Sector nodeRefs and QuestPrefabRefHash records use the full child refs. This single-root design avoids making a claim about dependency inheritance across external child phases.

World layout

These are inherited test-site values, not a promise that the location is reachable or the volumes are appropriate on every game build. The acceptance matrix—not structural inspection—governs runtime claims about the marker, both outlines, their vertical coverage, and the finite padded Quest descriptor bounds.

The site is the outdoor recycling-station cabinet row in Watson/Kabuki. A focused vanilla sector, TweakDB, and localization chain identifies the Allen Street terminal and linked marker about 90 m southwest of the lab center; Test Boundary Check explains how to verify that ordinary route before installing the candidate. Those identities and coordinates are Observed in vanilla. The retained matrix governs runtime claims about practical access, the route, and the new 110 m boundary.

Each Quest placement’s NodeIndex selects the corresponding local entry in nodes; the marker placement selects the only marker node. This is true for the compact mod-owned sectors. It is not a universal parallel-array rule for all vanilla sectors.

Authoritative trigger geometry

Each trigger owns a questTriggerNotifier_Quest and an AreaShapeOutline. The outline’s encoded buffer contains point count, four-float points, and height. Repository validation decodes that buffer and requires it to match the intended 16/20 points and 12/16 heights.

Do not change only the visible points or height. Retained vanilla exports show that the displayed JSON points can be defaults while the buffer carries different authoritative geometry. If the outline changes, regenerate or reserialize all three representations through a tool path that updates the buffer, then inspect the cooked result.

MaxStreamingDistance is named and compared. UkFloat1 is retained as an opaque field; this book does not rename it to a streaming distance without evidence.

Journal and marker contract

quests
└── minor_quest
    └── cqa003
        └── cqa003_01
            ├── cqa003_01_obj_reach
            │   └── cqa003_01_qmp_checkpoint
            └── cqa003_01_obj_leave

The journal map pin references #cqa003_mp_checkpoint and enables GPS. The static marker places an anchor; the journal entry owns player-facing mappin data; quest Mappin Manager nodes activate and deactivate that journal state. None of those records substitutes for the other two.

Both Lab 3 Mappin Manager nodes set disablePreviousMappins: 0. This isolated lab has no deliberate previous route to replace; activation and inactivation come from the nodes’ Active and Inactive sockets.

Exact questphase

The figure is generated from the completed checkpoint. Validation resolves socket handles and requires exactly 16 nodes and 16 edges.

Every node has one explained responsibility. The graph does not contain a hidden hub, child phase, scene, community, device, or script dependency.

Exact edge contract

The only persistent fact is cqa003_completed. Quest, journal, active-node, world, and marker state can also be save-backed even though they are not FactsDB names.

Common failure modes

Lab sequence: All labs · Next: Author Boundary Check in WolvenKit.