See the work happen in the workspace.
Actual navigation and inspection in the current interface, using a separate copy of real project and build records. No decorative cursor simulation or invented result.
Inside the build workspace
Move from a project into its completed build, history and release preparation.
Current interface · Recorded 9 October 2026 · Existing October 7 build records
Read the walkthrough
- The Projects view identifies the engine and readiness of each game.
- Open Starter Kit Match-3 to inspect the Windows artifact from an earlier real build.
- Open Builds to see completed and canceled runs with their targets and durations.
- Open Releases to see destination configuration. This clip does not upload to a store.
The four stages of project setup
Follow Project, Environment, optional Connections and Readiness in the current interface.
Current interface · Recorded 9 October 2026 · Existing October 7 build records
Read the walkthrough
- Choose an existing game project without moving its source.
- Environment checks the matching editor, Windows target and export requirements.
- Connections are optional for a local build; provider authorization and publishing configuration are separate.
- Readiness reports required checks. A passing setup check is permission to build, not proof that the game plays.
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.
Prepare a destination
See how the selected artifact relates to Steam and itch.io release profiles.
Current interface · Recorded 9 October 2026 · Existing October 7 build records
Read the walkthrough
- Open the completed Godot project, then choose Releases.
- Inspect the artifact selected for release and the available destination controls.
- A destination still needs your publisher configuration and verified access.
- The recording shows preparation only. No upload or live store release is demonstrated.
What these recordings establish.
The clips show the current application interface and real interactions. The run clip starts a new Godot build on October 9. Inspection examples use October 7 records; no clip tests the extracted game’s behavior.
Signed installation, real email/provider approval, live store upload and a complete team/runner workflow have no recorded demonstration in this delivery. Their prerequisites and current limits are explained in the setup and documentation pages.
Read the current release boundary