Posts about features and tips that improve developer workflows with Godot
View All Tags
Godot Launcher 1.10.0 is for projects that do not always fit the default path: local engine builds, patched Godot editors, older projects that ask for a missing editor, and VS Code config files that need a careful recovery path.
You can now register your own Godot builds next to official releases, pick them per project, and keep importing projects even when the exact editor is not installed yet.
Godot Launcher 1.9.0 brings two practical quality-of-life improvements. You can now create a new project in the parent folder you actually want with Overwrite Project Path, and app updates now follow a clearer two-step flow: download when you are ready, then restart once the update is prepared.
The Godot Launcher just got a public roadmap. Here's why it matters and how you can follow along.
With the release of Godot 4.4, the editor now remembers the last window size and position. This small but useful improvement opens the door for a more flexible way to launch Godot projects, and the Godot Launcher 1.2.0 update supports it.
This release introduces a small but helpful quality-of-life feature for developers using Visual Studio Code. When creating a new Godot project with the Setup Visual Studio Code as Text Editor setting enabled, the launcher now automatically configures VSCode to hide Godot's autogenerated .gd.uid files by