Shipping example verification

The actual Win64 Shipping example has an explicitly opt-in review route. Normal play does not spawn the review actor. The review operates the same saved Blueprint screens and public provider actions used by players; it does not substitute a test-only menu or HUD.

Shipping logging keeps its normal engine configuration. The fixture writes a UTF-8 sidecar under Unreal's example user save directory. It records the compiled configuration, engine version, executable path, PID, destination map, actual viewport, individual checks and terminal result. The external verifier requires the actual Shipping executable and checks the declared genre against the loaded map. A process exit or static frame alone is insufficient.

What the current records cover

The SI6F revision has four primary flows and four clean-process reloads on UE5.6.1 CL44394996: RTS/RPG at 1280×720 and 800×600 with enlarged UI/text. Checks cover saved settings Cancel/Apply, isolated SaveGame persistence, independent UI/game volume values, controller glyphs and cursor/input presentation, actual Patrol/Ward responses, center-tint material, backend pause/resume, custom Blueprint cards, dialogs/focus and return to main.

The actual slider graph is invoked through its value-change event. This verifies the saved Blueprint binding and resulting setting, not physical slider manipulation. Audio-value checks do not replace the separate mixer PCM tests. Remapping, physical controllers/touch, OS input, other platforms and broader Shipping feature coverage retain their own verification gates.

SI6G adds a settled-frame primary-label geometry check and player-menu travel in both directions. Its eightactualUE5.6 Shipping primary/reload cases nowpass, with12menu-travel trails andpositive settledlabelgeometry. Reviewednormaland enlargedframesare readable; earlierclipping-lookingcaptureis retainedwithoutclaimingitscause. SI7G/SI8G now have the same eight scoped actual Shipping primary/reload passes on UE5.7.4 CL51494982 and UE5.8.3 CL58210709. Shipping-G-Matrix pins24cases/36menu-travel trails across the three frozen177-source/55-package revisions. Each engine compiles32Blueprints cleanly. This evidence predates the new-label localization refresh.

Review data and reproducibility

The review uses uniquely named IFShipQA- profiles. A primary run refuses to overwrite an existing profile; its separate reload requires that profile to exist. Existing terminal records are preserved and can only be resumed after strict verification. Shipping uses the engine user save directory, which differs from the Development archive's Saved directory. The launcher copies owned records, frames and profile snapshots into internal Evidence for review.

Run Tools/package_shipping_review.ps1 with a fresh prepared host tag and its engine version. It serializes build/cook/archive, immediately captures UAT receipts, compiles all saved Blueprints, verifies distribution boundaries and runs primary/reload cases through Tools/run_shipping_reviews.ps1. Tools/verify_shipping_review.py verifies sidecars against the exact executable. These tools belong to the development workspace, not the normal buyer authoring workflow.

The real main-menu Visit Emberwatch / Visit Ashen Reach actions select the worlds. The tested Shipping executable ignored a command-line map override; the rejected record identified its actual RTS map instead of claiming an RPG success. See world navigation for the public Blueprint/provider route and root cleanup around Open Level.

Current records are development evidence, not a declaration of full product completion or platform certification. Failed source/launcher/map cases and prior artifacts are retained separately. Final delivery excludes internal Evidence, user save data, reference captures and private SDK validation archives.