Lab 4: Handoff Point

Lab 4 moves Boundary Check’s reach/leave activity into an external child questphase. The registered root starts the child, waits for its Out1 return, then performs a visible parent-only confirmation before completing the quest.

Structurally validated: both seven-resource checkpoints round-trip with WolvenKit 8.19.0. Follow the test guide for child entry, return, streaming, and save/reload.

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

What the lab demonstrates

registered root -> completed == 0?
  False -> terminate
  True  -> activate quest and phase
        -> enter external child through In1
             activate reach objective and pin
             wait IsInside reach volume
             retire pin; succeed reach; activate leave
             wait IsOutside leave volume
             succeed leave; terminate child through Out1
        <- parent phase node emits Out1
        -> activate confirmation objective
        -> wait 30 realtime seconds
        -> succeed confirmation and phase
        -> set completed = 1
        -> succeed quest; terminate root

The CutDestination socket exists on the external phase node and other relevant nodes, but every cut socket is deliberately unwired. Lab 4 teaches a normal terminating Out1 handoff only; cut behavior remains Experimental.

Required environment

Other versions may expose different editor wrappers or runtime behavior.

Prerequisites and downloads

Complete Lab 3, then read:

• Registering a root questphase;

• Inputs and outputs;

• Calling child phases;

• Prefab dependencies;

• Completion and interruption.

• Download the start checkpoint. It has the complete seven-resource scaffold, a three-node root, and a two-node pass-through child.

• Download the completed checkpoint. It has the same resources, the exact 12-node root, and the exact 10-node child.

Do not install the two checkpoints together. They register and pack the same depot paths. Use an untouched save created before any Lab 4 candidate was first installed. Uninstalling an earlier candidate or setting cqa004_completed = 0 does not remove save-backed journal, phase, mappin, world, or graph state.

Resource ownership

The loose ArchiveXL file is packaging metadata, not an eighth CR2W resource. ArchiveXL registers the streaming block, not its sectors separately.

Registration and child resolution

The ArchiveXL file registers only the root phase:

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

journal:
- mod\cqa\cqa004\journal\cqa004.journal

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

streaming:
  blocks:
  - mod\cqa\cqa004\world\cqa004_handoff.streamingblock

Parent phase node 13 resolves the child through:

phaseGraph: null
phaseResource:
  DepotPath: mod\cqa\cqa004\phases\cqa004_boundary.questphase
  Flags: Soft
phaseInstancePrefabs: []
saveLock: 0
unfreezingTriggerNodeRef: 0

The child is packed but not independently ArchiveXL-registered. The supplied validator rejects a child registration entry.

Prefab and NodeRef contract

The registered root declares one local prefab root:

#cqa004_pr_handoff

The external child declares:

phasePrefabs: []

The world-side full root and nested references are:

$/mod/cqa/cqa004/#cqa004_pr_handoff
  #cqa004_tr_reach
  #cqa004_tr_leave
  #cqa004_mp_handoff

The child directly uses the two local trigger refs. Its empty prefab list is intentional: Lab 4 tests root-owned scope across the child boundary. The arrangement is Structurally validated here, Observed in vanilla in the cited street-story pair, and Runtime-proven in the retained four-child GQT003 fixture. Lab 4’s own runtime result remains Experimental.

World and journal scaffold

The world resources reuse Lab 3’s checked geometry under the cqa004 namespace:

The typed journal tree is:

quests/minor_quest/cqa004
└── cqa004_01
    ├── cqa004_01_obj_reach
    │   └── cqa004_01_qmp_handoff -> #cqa004_mp_handoff
    ├── cqa004_01_obj_leave
    └── cqa004_01_obj_confirm

The child owns the first two objectives and map pin. The parent owns the confirmation objective. The only FactsDB name is cqa004_completed.

Start checkpoint contract

The start root already teaches external resolution without the completed behavior:

Its two edges are 0.Out -> 13.In1 and 13.Out1 -> 1.In.

The start child contains [0] Input and [1] Output, connected by 0.Out -> 1.In. Output 1 is Terminating. This pass-through is a checkpoint for inspecting both interface layers; it is not the completed player activity.

Exact root phase

Root edge contract

Exact boundary child phase

Child edge contract

No root edge reaches a child node directly. No child edge reaches a parent node directly. Phase node 13 and the matching interface names are the handoff.

Common failure modes

Lab sequence: All labs · Previous topic: Complex cleanup, interruption, and cancellation · Next: Author Handoff Point in WolvenKit.