Dev log – Day 18 – Release
Summary
Day 18 was focused entirely on finalizing Shutdown Protocol for submission and release. The work centered on producing and validating both a Development test build and the final Shipping distribution build, resolving last-minute performance and presentation issues discovered during verification, and completing all required documentation deliverables. The day concluded with a full parity check to ensure the shipped build and written materials accurately reflect the same finalized project state.
What I Worked on Today
[Global / Release] – Final Build, Testing & Documentation Delivery
Intent
Produce final test and distribution builds of the game and complete all required project documentation deliverables (GDD, LDD, Technical Documentation, and User Manual) in a submission-ready format. Ensure the shipped build and written materials match the finalized project state.
What Actually Happened
A Windows Development test build was packaged first to validate the complete gameplay flow and surface any remaining issues. During this pass, several late-stage problems were identified, including texture streaming budget pressure, minor alignment issues, and small gameplay presentation bugs. These were addressed before transitioning the project to a Shipping configuration. Debug options were disabled, distribution settings were enabled, and a final Shipping build was packaged and launched to confirm clean startup and full end-to-end playability. Documentation was then finalized and reviewed against the shipped build to ensure full alignment across design, level flow, technical structure, and player-facing instructions, followed by a final verification pass.
Accomplished
- [STEP] Set build configuration to Development for test build packaging.
- [STEP] Verified Windows platform packaging settings prior to test build.
- [STEP] Set staging directory and confirmed Development configuration for test build packaging.
- [STEP] Packaged a Development test build of the game using the Windows platform.
- [STEP] Packaged a Development test build of the game using the Windows platform.
- [NOTE] Test build shows Texture Streaming Pool Over Budget warning indicating optimization and/or texture memory adjustments are required.
- [FIX] Identified start menu background image alignment issue where the image is not centered on screen.
- [FIX] Identified keycard spawn offset issue where the keycard spawns too far from its intended location.
- [FIX] Reduced texture resolutions and replaced selected static meshes with lower-fidelity variants to address texture streaming pool over budget.
- [FIX] Applied last-minute fixes by gating feedback sound playback to prevent sounds from triggering when no longer required.
- [STEP] Set build configuration to Shipping in preparation for final distribution build.
- [STEP] Disabled debug options and enabled For Distribution setting for Shipping build.
- [STEP] Packaged final Shipping build for distribution.
- [TEST] Launched final Shipping build and verified correct startup and gameplay flow with no debug output.
- [STEP] Finalized the Game Design Document (GDD) to accurately reflect shipped gameplay, mechanics, UI flow, and level structure.
- [STEP] Updated and aligned the Level Design Document (LDD) with the finalized GDD, reflecting Room 1, Room 2, and the Exit Corridor as implemented.
- [STEP] Produced complete Technical Documentation detailing Blueprint architecture, core systems, major classes, asset roles, and system integration.
- [STEP] Authored a full User Manual explaining game objectives, controls, interaction rules, puzzle progression, and completion flow.
- [STEP] Generated final documentation deliverables in structured format suitable for academic submission and portfolio use.
- [STEP] Built and validated final distribution build after documentation completion to ensure parity between shipped game and written deliverables.
- [TEST] Performed final verification pass confirming documentation matches shipped gameplay, controls, UI behavior, and end sequence.
- [NOTE] Project deliverables finalized: playable build, GDD, LDD, Technical Documentation, and User Manual.
Why This Matters
- Locks the project into a verified Shipping build state with distribution settings enabled and all debug output removed.
- Ensures all documentation accurately reflects the shipped version of the game, reducing risk of mismatch during review or submission.
- Addresses late-stage stability and performance risks before final delivery, resulting in a cleaner and more reliable final build.
Technical Notes
- Development builds were used strategically to surface performance warnings (texture streaming pool) before committing to Shipping.
- Final Shipping configuration required disabling debug options and explicitly enabling “For Distribution” settings.
- Reducing texture resolutions and swapping select meshes proved sufficient to resolve streaming budget warnings without visible quality loss.
Challenges & Lessons Learned
- Late-stage verification often reveals small but important issues that are easy to miss earlier (alignment, offsets, audio gating).
- Documentation should be finalized after gameplay and build stabilization to ensure exact parity with the shipped experience.
- Running a clean Shipping build test after documentation completion is critical to confirm nothing drifted during final polish.
Next Steps
- Submit the final Shipping build and documentation bundle for evaluation.
- Archive the final project state, builds, and documentation sources for portfolio and long-term reference.
- Optionally perform a final fresh-machine launch test to confirm distribution robustness.