Godot on Mac: Your First Walker Project with Claude Code

Downloading Godot gives you an engine, not a game. In Walker's first setup tutorial, Liam, in for Bear, shows how to choose the regular macOS download, identify the installed executable, create an empty walker-jumpman project, and check exactly what that setup proves.

Walker explores making Godot games by prompting. The larger workflow is Game brief → Build → Playtest → Inspect → Revise → Export. This episode establishes a checkable starting point; it does not build Jumpman gameplay or claim a tested Web export.

WHAT YOU'LL LEARN

• Regular Godot vs. .NET, and why this project uses GDScript.
• The difference between a ZIP archive, Godot.app, and project.godot.
• How to check the engine version from Terminal.
• How to give Claude Code a precise, no-overwrite project request.
• Why the planned browser target calls for Compatibility.
• How to inspect the configuration and keep untested claims separate from evidence.

CHAPTERS 0:00 An engine is not a game 0:27 Choose the Godot macOS download 0:47 Download evidence and installation 1:04 Find the executable and check its version 1:31 Ask Claude Code for an empty project 1:50 Project name, path, and Git metadata 2:19 Switch to Compatibility for the Web target 2:48 Recheck the project and prevent overwrites 3:07 What remains unbuilt 3:26 Your turn: a checkable Walker project

YOUR TURN Create an empty walker-prefixed Godot project using GDScript and Compatibility. Preserve existing files. Ask Claude Code to show the configuration, the file list, what it verified, and what remains untested.

OFFICIAL REFERENCES Godot for macOS: https://godotengine.org/download/macos/ Godot command line: https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html Web export: https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_web.html C# and .NET: https://docs.godotengine.org/en/stable/tutorials/scripting/c_sharp/c_sharp_basics.html

PRODUCTION & DISCLOSURE Created with Brutalist: https://github.com/nikbearbrown/brutalist.art Liam is an AI narrator using local Kokoro speech synthesis, not a recording or voice clone of Bear. The download page and Godot dialogs are labeled UI reconstructions. Terminal replays use saved command output, with the supplied download log identified separately. Godot 4.7.2 was used for the recorded setup checks; versions and interfaces may change. Independent tutorial, not endorsed by Godot or Anthropic. Native 3840 × 2160 master; optional English closed captions.

WALKER PLAYLIST https://www.youtube.com/playlist?list=PLbeL9xXuLsLs

What this video covers

• 0:00 — An engine is not a game
• 0:27 — Choose the Godot macOS download
• 0:47 — Download evidence and installation
• 1:04 — Find the executable and check its version
• 1:31 — Ask Claude Code for an empty project
• 1:50 — Project name, path, and Git metadata
• 2:19 — Switch to Compatibility for the Web target
• 2:48 — Recheck the project and prevent overwrites
• 3:07 — What remains unbuilt
• 3:26 — Your turn: a checkable Walker project

Transcript

A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.

An engine is not a game

[0:00] Hi, this is Liam in for Bear. We're downloading Godot, inspecting what landed, and creating an empty walker jumpman project you can actually identify. Downloading Godot gives you the engine, not a game. Naming a project gives that engine a place to work. The player and level still have to be built. The download is a zip archive. Inside is the application. Your project is a different folder containing settings and later scenes and scripts.

Choose the Godot macOS download

[0:27] On Godot's Mac OS page, choose the regular engine for this walker project. Universal means this package supports both Apple silicon and Intel Macs. The other download adds C# support and needs the .NET SDK. Our plan uses GDScript. Choosing the regular engine is a workflow decision, not a quality downgrade. Bear's download log says the

Download evidence and installation

[0:48] Archive finished saving. That is download evidence. It doesn't prove the application launches or that project exists. Extract the archive to get godot.app. Keep the application in applications. That is the engine's home. It isn't where your game source belongs.

Find the executable and check its version

[1:04] The app is a bundle. Its executable lives inside contents mac OS godot. Calling that executable with version asks the installed engine to identify itself. On this Mac, that check returns 4.7.2 stable. Keep the full version string in your notes. A tutorial's version can age. The godot command here is a link to that same executable. If your terminal cannot find it, the full application path still avoids guessing.

Ask Claude Code for an empty project

[1:31] Ask Claude Code for an empty project, not jumpman gameplay. Specify the name and destination. Tell it to stop if the destination already contains work. This configuration names the project and records its engine features. There is no player script hidden in these lines. The file is the setup, not the game.

Project name, path, and Git metadata

[1:50] In create new project, the name labels the project. The path chooses where its files go. Keep the engine project beside walker's design documents in its own subfolder. Check the final path before creating. Create folder can add a subfolder. Get metadata prepares ignore files. It does not publish a repository to GitHub. The first result is an empty project the editor can load. No main scene is assigned. That is our stopping point for creation, not a failed game launch.

Switch to Compatibility for the Web target

[2:19] Bare screenshot selected forward plus that can serve a desktop project. Our plan browser version changes the requirement. Godot's web export uses the compatibility renderer. Now give Claude the constraint that matters. Keep this empty project, select compatibility for the web target, and show the exact configuration changes. The revision changes the renderer settings and the feature label. It does not add mechanics. Read the diff. A setup change should not quietly become game generation.

Recheck the project and prevent overwrites

[2:48] Load the revised project again. Check its name, renderer settings, and absence of scenes and scripts. These checks establish an empty starting point, not a tested browser build. Try creating into that occupied destination again. The safe response is to stop, not replace it. Preserving existing work is part of a correct setup. An empty editor is

What remains unbuilt

[3:08] Expected. No main scene means there is nothing to run yet. Next comes a scene, then a player, then a level. Walker starts with a game brief. Building, play testing, inspection, revision, and export follow. Today we prepared an empty engine project. Movement, fun, and export remain untested. Your task is to produce a

Your turn: a checkable Walker project

[3:27] Checkable starting point. Ask for the configuration, the file list, and the limits of the check. Liam, in for bare. Create an empty Walker prefix Godot project. Use compatibility and GDScript. Preserve existing files. Show its configuration and file list. State what you verified and what remains untested. >> Nick Bear Brown teaching Claude.