Author Boundary Check in WolvenKit

Build Boundary Check in WolvenKit using the start checkpoint. You will add the quest graph to the supplied streaming, journal, and localization resources.

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. Other versions may expose different editor wrappers or runtime behavior.

1. Open and isolate the checkpoint

1. Download and extract the start ZIP.
2. Open CQA_Lab03_BoundaryCheck_Start.cpmodproj with File > Open Project.
3. Make an untouched backup of the extracted directory.
4. Confirm that source\archive and source\raw each contain the same six depot resources listed in the lab overview.
5. Confirm CQA_Lab03_BoundaryCheck_Start.archive.xl is under source\resources.
6. Do not install the start and completed checkpoints together.

The phase should contain only [0] Input connected to [1] Output. Confirm Input socketName: In1, Output socketName: Out1, and Output type: Terminating.

2. Audit registration before graph work

Open the ArchiveXL file and retain all four sections:

quest:
  phases:
  - path: mod\cqa\cqa003\phases\cqa003.questphase
    parent: base\quest\cyberpunk2077.quest

journal:
- mod\cqa\cqa003\journal\cqa003.journal

localization:
  onscreens:
    en-us:
    - mod\cqa\cqa003\localization\en-us\onscreens\cqa003.json

streaming:
  blocks:
  - mod\cqa\cqa003\world\cqa003_boundary.streamingblock

The block owns the two sector dependencies. Do not add the sectors to a guessed top-level registration list. base\quest\cyberpunk2077.quest is a vanilla reference; do not include an extracted copy.

3. Audit the journal, strings, and map pin

Open cqa003.journal and confirm this typed tree:

gameJournalRootFolderEntry
└── quests                         gameJournalPrimaryFolderEntry
    └── minor_quest                gameJournalFolderEntry
        └── cqa003                 gameJournalQuest
            └── cqa003_01          gameJournalQuestPhase
                ├── cqa003_01_obj_reach
                │   └── cqa003_01_qmp_checkpoint
                └── cqa003_01_obj_leave

The map-pin entry is gameJournalQuestMapPin. Confirm:

Open the onscreen localization resource and confirm four entries with primary key 0, empty male variants, and these exact joins:

Save, close, and reopen both resources. Do not edit the raw JSON review copies.

4. Audit the root prefab declaration

Open cqa003.questphase in the resource editor. Its root questQuestPhaseResource has:

phasePrefabs[0].prefabNodeRef = #cqa003_pr_boundary
inplacePhases = []

Keep exactly one declaration. phasePrefabs is a root-resource collection; phaseInstancePrefabs belongs to a Phase node. This lab has no child phase node and needs no duplicate declaration.

The full world root is $/mod/cqa/cqa003/#cqa003_pr_boundary. Local graph conditions refer to child refs under that declared root.

5. Audit the streaming block

Open cqa003_boundary.streamingblock. It has two worldStreamingSectorDescriptor records:

The Quest descriptor’s finite box is:

Min (-1300.02, 1197.2208, -291.7)
Max ( -700.02, 1797.2208,  308.3)

The AlwaysLoaded descriptor uses the supplied broad -99999..99999 box. Descriptor and sector levels are separate properties: the Quest descriptor is level 0, while the Quest sector root below is level 255. Do not normalize them to the same number.

The chosen bounds are Experimental. Keep them unchanged for canonical comparison; tune bounds only as a separately hashed candidate.

6. Audit the Quest sector and placements

Open cqa003_boundary.streamingsector. Confirm root category Quest, level 255, two nodes, two nodeData.Data records, and two full nodeRefs.

Both placements use yaw 88.6°, unit scale, zero/unset cooked prefab data, and these distance-shaped fields:

Treat UkFloat1 as opaque. Similar numerical ordering does not establish its meaning.

For these compact supplied sectors, NodeIndex selects a local node. Do not turn that into a universal rule: some vanilla sectors register refs or use indices outside a local nodes array.

7. Audit each trigger and its authoritative outline

Each node is a worldTriggerAreaNode with one questTriggerNotifier_Quest, includeChannels: TC_Default, and isEnabled: 1.

Open the AreaShapeOutline and inspect the serialized resource, not only the canvas preview. Its binary buffer begins with a little-endian point count, then stores each point as four floats (x, y, z, 1.0), then the height float. The supplied resources were verified by decoding those bytes.

Do not manually edit only points or height. If you intentionally change an outline, use a WolvenKit operation that rebuilds the buffer, save and reopen, then serialize the cooked result for an independent buffer check. The canonical walkthrough keeps the supplied geometry unchanged.

8. Audit the marker sector

Open cqa003_always_loaded.streamingsector. Confirm category AlwaysLoaded, level 1, and one worldStaticMarkerNode selected by NodeIndex: 0.

The marker is an anchor. It is not the journal map pin, and it does not change journal state. Keep the three-owner chain intact: sector marker, journal map pin, graph Mappin Manager.

9. Add and number graph nodes

In the questphase graph, add these nodes in order. Input 0 and Output 1 already exist.

WolvenKit normally assigns lower automatic IDs. Renumber safely in two passes: move the new nodes to temporary IDs 100–113, then to target IDs 10–23. Never overwrite an ID still owned by another node. Save, close, reopen, and confirm the exact inventory before wiring.

10. Configure the completion guard and fact writer

At ID 10, add a questFactsDBCondition, then questVarComparison_ConditionType:

At ID 22, choose questSetVar_NodeType and set:

Exact assignment makes the one-shot result independent of an old numeric value. Do not use a console write in the canonical runtime run.

11. Configure journal operations

For Journal IDs, add questJournalQuestEntry_NodeType and a typed gameJournalPath. Keep these common values:

Incoming sockets choose state. IDs 11, 12, 13, and 18 receive Active; IDs 17, 20, 21, and 23 receive Succeeded.

12. Configure map-pin operations

Both Mappin Manager nodes use this typed path:

Set both ID 14 and ID 16 to disablePreviousMappins: 0. ID 14 receives the Active socket and ID 16 receives the Inactive socket; both paths point to the same journal entry. This isolated lab has no deliberate prior route to replace. Use 1 only for a separately tested transition that intentionally clears previous routing.

13. Configure trigger Pause Conditions

At each Pause Condition, add a questTriggerCondition at condition:

Set isPlayerActivator: 1. Leave activatorRef as the ordinary empty gameEntityReference; do not substitute a guessed entity path. These are state-shaped waiting nodes. Do not change them to Entered/Exited while comparing with the canonical checkpoint.

14. Wire the exact graph

Use Show Unused Sockets, then create these 16 ordinary edges:

Leave every CutDestination unwired. Save, close, reopen, then compare IDs, types, payloads, sockets, and edges with the exact generated graph. Canvas position and handle IDs are not behavior.

15. Validate, build, and install

With every tab saved:

1. run Project > Scan for broken file references;
2. run Project > Scan for broken files;
3. run Project > Run File Validation on the entire project;
4. resolve all project-owned errors;
5. close Cyberpunk 2077;
6. choose Build > Install and wait for packing and installation;
7. inspect WolvenKit’s Log panel and both installed files.

Use the normal ArchiveXL project install, not Install as REDmod. A packed archive without its loose .archive.xl cannot attach the phase, merge the journal/localization, or register the block.

The authored start project installs _Start-named files. To test the supplied completed project, open CQA_Lab03_BoundaryCheck.cpmodproj and remove the start project’s installed files before installing it.

Common authoring failures

Lab sequence: All labs · Previous: Lab 3: Boundary Check · Next: Test Boundary Check.