From prompt to playable checkpoint: building a first-person game with Director 1
A first-person build log should show the prompt, the starter or blank start, the real Godot/Flockbay Engine project files Director 1 changed, and the browser preview checkpoint used to decide the next iteration.
Start with the playable action
The prompt should name what the player does moment to moment: move through a room, aim at targets, collect an item, avoid danger, or reach an exit. Director 1 gets a clearer first checkpoint when the request describes a player action instead of only naming a genre.
Keep the Godot project path visible
The proof should lead with the real PC game path, then show that the game is built from real Godot/Flockbay Engine project files. Scenes, scripts, assets, controls, camera behavior, and project metadata matter because they are what Director 1 can keep changing after the first preview.
Use browser preview as the checkpoint
The browser preview is the first place to play the current version. It should prove movement, camera, interaction, and a simple goal well enough for the creator to decide what Director 1 should change next.
Record what is still unfinished
The build log should not imply that one prompt produced a finished commercial game. It should name the known limits, the next likely change, and any desktop-build proof still needed before stronger claims are made.