Moving a Godot 2D Game to 3D? Let an Agent Handle It

Where this fits

Your 2D platformer is feature-complete, and then the product team asks: "Can we make the same game in 3D?" The task is not just changing z-indexes. Every node type, physics layer, camera, input mapping, and art asset follows different rules. The godot-adapt-2d-to-3d skill gives an agent those rules, so instead of asking "what goes where" it can perform a structured migration of an existing Godot project.

Why agents benefit

• It can rewrite scene trees with correct node type mappings: CharacterBody2D → CharacterBody3D, Area2D → Area3D, CollisionShape2D → CollisionShape3D, and so on.
• It picks a camera system based on gameplay: third-person spring arm, first-person mouse look, or orbit camera, instead of copying Camera2D follow logic.
• It migrates collision_layer and collision_mask with 3D layer conventions, preventing characters from clipping through floors or hitting invisible walls.
• It converts sprite placeholders into mesh instances and reminds the developer to add lights and materials, avoiding the classic "black screen" first run.
• It adapts control schemes: movement becomes camera-relative, and jump/gravity values are tuned for Z-depth and 3D physics.

Practical scenarios

2D platformer becomes a 3D exploration game

The agent replaces tilemap collisions and player body nodes, then sets up a third-person spring arm camera and converts the input map so jumping feels correct with depth perception.

Top-down 2D shooter becomes a third-person controller

Here the agent needs more than node swaps: it changes aiming from screen-space to world-space raycasts, adds an orbit camera, and reworks enemy AI sightlines to rely on 3D physics queries.

Adding a 3D minigame inside a 2D title

A visual novel or 2D RPG adds a 3D hub room. The skill handles the isolated 3D subtree, migration of physics layers, and switching between Camera2D and Camera3D without touching the rest of the 2D game.

Add it to your agent workflow

Install it for a project with:

npx skills add thedivergentai/GD-Agentic-Skills --skill godot-adapt-2d-to-3d

Then give your agent a migration task such as: "Port player.tscn to 3D using an orbit camera, migrate all collision layers, and replace sprite textures with placeholder MeshInstance3D nodes." The agent will use the skill's constraints, including the "NEVER do" rules, to avoid flat 3D, missing lights, and stale 2D physics.

Compare before adopting

Before adding it to every project, compare quality signals: Does the README include concrete constraints and examples? Is it maintained for your Godot version? Also check alternatives — generic "Godot coding" skills might not contain the migration-specific camera and collision patterns. Finally, consider workflow fit: the skill is most useful when your agent already has access to the project structure and can inspect scene files before editing.

Why it is worth tracking

With 657 stars on GitHub and a focused scope, this skill has enough community momentum to be worth evaluating before your next 2D-to-3D port. The maintainer is actively publishing agent skills for Godot, and you can follow the skill's evolution and community feedback on its OpenAgentSkill page: https://www.openagentskill.com/skills/thedivergentai-godot-adapt-2d-to-3d. If your backlog contains any "make it 3D" feature, track this skill now so you know whether its patterns match your engine version and art pipeline when the migration starts.