godot-port
Skill23 starsChanged 5 days agoMITView on GitHub
Port a Godot 4 project (GDScript) to Unity, Unreal Engine, three.js/web or Godot C# with ReversePort — signals, node paths, autoloads, scenes, physics bodies, input actions and coordinates done right. Use whenever the source of a port is a Godot project, including "make a web/browser version of my Godot game".
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- rea-analysis-optimizationSkill
- rea-changelog-updateSkill
- rea-ci-tests-auditSkill
- rea-tool-designSkill
- reverse-engineer-anythingSkill
- build-inspectorSkill
- port-projectSkill
- port-verifySkill
- proof-caseSkill
- rebuildSkill
- reverse-engineerSkill
- troubleshootSkill
- unity-to-godotSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 8
Use the port-project skill for the loop.
≈ “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
Porting from Godot
Use the port-project skill for the loop; this skill holds the Godot-specific judgement.
Before planning
- Godot 3 source (
config_version=4in project.godot)? Upgrade first:port_upgrade {path, action:"apply"}writes a Godot 4 copy and lists what needs a human; fix those,re_apicheckthe copy, then port from the copy. re_scene {file:"project.godot"}→ main scene, autoloads (singletons), input actions, physics tick rate. Autoloads become singletons (Unity: DontDestroyOnLoad MonoBehaviour; Unreal: GameInstanceSubsystem; web: module singleton). Input actions must be recreated by name in the target.- Binary
.scn/.rescannot be read as text: open them in Godot and save as.tscn/.tresfirst. port_map {from:"godot", to}— read the conventions once; they decide naming and coordinates.
Things that silently break
| Godot | Watch out |
-transform.basis.z is forward | Unity forward is +Z, Unreal +X. Never copy direction math unconverted. |
rotation is radians, Euler order YXZ | Unity eulerAngles are degrees; three.js default order is XYZ (set rotation.order = 'YXZ'). |
| meters | Unreal is centimeters: speeds, forces, ranges, gravity ×100. |
_physics_process at 60 Hz | Unity FixedUpdate is 50 Hz by default; Unreal ticks per frame. Retune or set the rate. |
move_and_slide() uses velocity and delta internally | Unity CharacterController.Move wants a displacement (× deltaTime) and no built-in gravity. |
| signals connected in the editor | They live in .tscn [connection] sections: re_scene lists them; recreate each one. |
$Path / get_node | Target: serialized references (Unity), component pointers (Unreal), direct references (web). |
await on signals/timers | Unity: coroutines (or Awaitable); Unreal: timers/delegates; web: promises with a game-time timer. |
| groups | Unity tags, Unreal actor tags; port_scene carries the first group as the tag. |
Camera3D fov is vertical | Unreal FieldOfView is horizontal: port_convert {fov, aspect}. |
Targets
- godot-csharp: the smallest port. Scenes, resources and project.godot are copied with script paths swapped by
port_scene; only scripts are rewritten (public partial class X : Base, PascalCase API,double delta,[Export],[Signal] delegate void XEventHandler(), struct properties copied out and back). - unity: scenes become
*.scene.jsonspecs + the editor builder; build them in Unity after the scripts compile so components attach by class name. - threejs: scenes become TypeScript builder modules (
buildMain()); physics with Rapier; UI in HTML/CSS. Godot can export meshes as glTF for GLTFLoader. - unreal: scripts become
.h/.cpppairs with UCLASS/UPROPERTY/UFUNCTION; scenes become specs in cm, Z-up.
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.

