Keep making the game. Keep builds repeatable.
One local workspace for the project, the tools it needs, the run history and the Windows files it produces.
Start from the project’s requirements.
Choose the game, engine version and Windows target. Environment checks establish whether the editor, export support and required toolchain are ready. The project’s original source is not the build workspace.
A passing preflight is permission to start. It does not guarantee a successful export or a correct game.
Follow the run without losing the details.
Queue and configuration
One local run at a time. Keep its target, configuration, revision and status together.
Diagnostics and original log
Read the human-readable explanation, then inspect the raw engine output when something fails.
Cancel, resolve, retry
Canceled and interrupted runs retain their history. A successful retry produces a new result; it does not rewrite the old failure.
Run a real Windows build
Start a Godot Windows release in the current interface and follow its completed artifact.
Current interface · A new Godot Windows release recorded 9 October 2026 · Gameplay not tested
Read the walkthrough
- Open the existing Godot project after its required setup checks pass.
- Choose New build, keep the Windows release target, and start the actual run.
- Follow the real build while the production build service exports and archives the game.
- Inspect the new completed artifact. Gameplay is not tested in this recording.
Inspect a real Windows artifact
Read an existing build, inspect its files and expand a checksum.
Current interface · Recorded 9 October 2026 · Existing October 7 build records
Read the walkthrough
- Open the Godot example and its build history.
- Return to Overview to inspect the earlier completed Windows ZIP.
- Expand SHA-256 to see a file checksum and open the build details.
- This is inspection of the October 7 run. A build is not rerun in this clip.
The green status is the beginning of inspection.
Compare the extracted files with the manifest, launch the game and exercise the behavior that matters. Only then prepare a release destination or share the build with testers.
