Agent skill · software engineering · sickn33
godot-4-migration
Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.
Why this skill is useful
Provides detailed migration patterns and syntax changes specific to Godot 4 that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Godot 4 Migration Guide Overview A critical guide for developers transitioning from Godot 3.x to Godot 4. This skill focuses on the major syntax changes in GDScript 2.0, the new Tween system, and export annotation updates. When to Use This Skill Use when porting a Godot 3 project to Godot 4. Use when encountering syntax errors after upgrading. Use when replacing deprecated nodes (like Tween node vs createtween). Use when updating export variables to @export annotations. Migration procedure Work in a backed-up branch or copy. Choose an exact Godot 4 version, validate conversion before changing files, and inspect converter gaps, renamed nodes, shaders, physics, plugins and export targets. Test scenes and saved games before replacing the working Godot 3 build. Examples below are fragments in an appropriate Node script; Enemy must be a declared project type. Official guide: Upgrading to Godot 4. Key Changes 1. Annotations (@) Godot 4 uses @ for keywords that modify behavior. export var x -> @export var x onready var y -> @onready var y tool -> @tool (at top of file) 2. Setters and Getters Properties now define setters/getters inline. Godot 3: Godot 4: 3. Tween System The Godot 3 Tween node was removed in Godot 4. Use createtween() in code. Godot 3: Godot 4: 4. Signal Connections String-based connections are discouraged. Use callables. Godot 3: Godot 4: Examples Example 1: Typed Arrays GDScript 2.0 supports typed arrays for type checking; measure performance rather than assuming a speedup. Example 2: Awaiting Signals (Coroutines) yield is replaced by await. Godot 3: Godot 4: Best Practices ✅ Do: Use @exportrange, @exportfile, etc., for better inspector UI. ✅ Do: Type all variables (var x: int) for performance gains in GDScript 2.0. ✅ Do: Use super() to call parent methods instead of .functionname(). ❌ Don't: Use string names for signals (emitsignal("name")) if you can use the signal object (name.emit()). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/godot-4-migration--142df9