godot-47-migration
Skill8 starsChanged 5 months agoMITView on GitHub
Godot 4.7 migration guide: new features (HDR, Steam Frame, AreaLight3D, VirtualJoystick, tween_await, Perfetto tracing), breaking changes, and step-by-step migration patterns for existing Godot 4.x projects. Use when upgrading a Godot project to version 4.7.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- godot-animationSkill
- godot-architectureSkill
- godot-audioSkill
- godot-brainstormingSkill
- godot-code-reviewSkill
- godot-csharp-patternsSkill
- godot-debuggingSkill
- godot-dialog-systemsSkill
- godot-gdscript-patternsSkill
- godot-headless-workflowSkill
- godot-i18nSkill
- godot-inputSkill
- godot-inventory-economySkill
- godot-networkingSkill
- godot-performanceSkill
- godot-physicsSkill
- godot-project-setupSkill
- godot-save-systemsSkill
- godot-shaders-vfxSkill
- godot-state-managementSkill
- godot-uiSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 77
Check all AreaLight3D nodes for new property options
- Distinctive: line 78
Update intensity profiles if using custom values
- Distinctive: line 81
If using third-party virtual joystick implementations:
- Distinctive: line 82
Remove custom VirtualJoystick scripts
- Distinctive: line 83
Add the built-in VirtualJoystick node to your scene
- Distinctive: line 84
Update input handling code (axis names may differ)
- Distinctive: line 133
When the MCP bridge is running (Phase 2), these tools support migration:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Godot 4.7 Migration Guide
Complete guide for migrating Godot 4.x projects to version 4.7.
What's New in Godot 4.7
Rendering & Visual
- HDR output settings — Configure HDR display support in project settings
- New AreaLight3D — Enhanced area lighting with new modes and intensity profiles
- Nearest-neighbor viewport scaling — Pixel-perfect rendering for retro-style games
UI & Controls
- VirtualJoystick — Built-in virtual joystick node replaces third-party solutions
- PopupMenu search — Native search in popup menus
- Control offset transforms — New transform system for UI animation
Animation
- Collapsible animation tracks — Better organization in AnimationTrackEdit
- tween_await() — Await tween completion for sequential chains
Mobile & Android
- Perfetto tracing — Built-in Android performance profiling
- Android XR settings — New project settings for extended reality
Steam Integration
- Steam Frame configuration — Enhanced Steam overlay and frame support
Step-by-Step Migration
Step 1: Backup Your Project
cp -r MyGame MyGame_backup_4.6Step 2: Open in Godot 4.7 Editor
- Launch Godot 4.7
- Open your existing project
- Editor will auto-migrate project.godot settings
- Review migration warnings in the output panel
Step 3: Update project.godot Settings
# Add HDR support if needed
[rendering]
environment/default_environment="default_world.tres"
# Add Steam Frame config if using Steam
[steam]
app_id="YOUR_APP_ID"Step 4: Review AreaLight3D Changes
- Check all AreaLight3D nodes for new property options
- Update intensity profiles if using custom values
Step 5: Replace Custom VirtualJoysticks
If using third-party virtual joystick implementations:
- Remove custom VirtualJoystick scripts
- Add the built-in VirtualJoystick node to your scene
- Update input handling code (axis names may differ)
Step 6: Update Tween Patterns
Replace nested callbacks with tween_await():
# Before (4.6)
func play_sequence():
var tween = create_tween()
tween.tween_property($Sprite, "position:x", 100, 1.0)
tween.finished.connect(func():
var tween2 = create_tween()
tween2.tween_property($Sprite, "position:y", 50, 0.5)
)
# After (4.7)
func play_sequence():
await create_tween().tween_property($Sprite, "position:x", 100, 1.0).finished
await create_tween().tween_property($Sprite, "position:y", 50, 0.5).finishedStep 7: Test All Platforms
- Windows desktop build
- Linux/X11 build
- Android build (verify Perfetto tracing works)
- HTML5 build
- Steam build (if applicable)
Breaking Changes Checklist
- Review VirtualJoystick API changes if using custom implementations
- Update tween callback patterns to use await syntax
- Test HDR rendering pipeline impact on visual quality
- Verify Android XR settings if targeting XR devices
- Check Steam Frame configuration compatibility
Godot 4.7 Feature Quick Reference
| Feature | Category | Skill Coverage |
| HDR output | Rendering | godot-project-setup |
| AreaLight3D | Rendering | godot-code-review |
| VirtualJoystick | Mobile | godot-brainstorming |
| tween_await() | Animation | godot-gdscript-patterns |
| Perfetto tracing | Profiling | godot-debugging |
| Steam Frame | Networking | godot-project-setup |
MCP Bridge Tools (Optional — Live Editor Integration)
When the MCP bridge is running (Phase 2), these tools support migration:
script_validate— Run withsuggestTweenAwait: trueto detect nested tween callbacks and suggestawaitmigrationproject_settings_read— Check current HDR/Steam settings before migrationproject_settings_set— Apply 4.7 settings (e.g.,rendering/hdr,steam/frame/*) directlyfile_search— Search for deprecated API patterns across the projectclass_db_info— Verify new 4.7 classes like AreaLight3D and VirtualJoystick are available
Note: MCP tools require the Godot editor to be running with the MCP plugin enabled. Skills work independently without the bridge.
References
- Full Migration Guide
- Godot 4.7 Changelog
- Godot 4 Migration Guide
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

