Reverse engineer anything. Port it anywhere.

A Godot pack, read field by field

The first bytes of a real Godot 4.3 .pck, and what re_archive makes of them. Point at a field to find its bytes. The same reader finds packs hidden inside an exported .exe.

reverseport archive MiniHeli.pck
{ "format": "godot-pck",
  "packVersion": 2, "godotVersion": "4.3.0",
  "encryptedDirectory": false, "totalEntries": 13,
  "entries": [ { "path": "res://actors/bullet.gd",
                 "offset": 900, "size": 208 }, … ] }

Port routes

Scenes, transforms and assets convert automatically. Code is ported by your agent with an API map for each pair, one unit at a time.

The problems that make ports go wrong

Each of these came from a real port that broke. ReversePort has a tool for it, so the agent does not have to guess.

• re_apicheck

  Is this GDScript valid for Godot 4.3? Finds Godot 3 names with their replacements, members that do not exist and classes that are too new.

• port_upgrade

  Godot 3 to 4 as a converted copy: renames, annotations, await, signals, scenes and project.godot, plus what still needs a human.

• port_convert {physics}

  Gravity, fixed step, damping, friction and layers mapped, and jump velocity recomputed, so the port falls and jumps the same.

• port_trace

  Logs both versions tick by tick and points to the first tick where they differ.

• port_shader

  Unity shaders and Shadertoys to Godot: uniforms, intrinsics and built-ins mapped, with markers for the rest.

• re_save

  Save files: layers, fields with their role, checksums that are verified, and a diff of two saves.

• re_il2cpp

  A Unity IL2CPP game without source: classes, methods and strings from global-metadata.dat, plus a C# skeleton.

• port_rpgmaker

  RPG Maker MV/MZ to Godot: maps drawn from the tilesets, events running and a list of what is left.

• re_archive

  GameMaker, Ren'Py, Unreal, Flash, FMOD, Wwise and Unity WebGL containers: names, assets and facts.

• re_refs

  Pink materials and "missing" scripts after a Unity move: dangling and duplicate GUIDs, with remap suggestions.

• re_strings

  Every player-facing string as .pot or .csv, and a translated copy written back.

• port_verify

  Leftovers, missing functions and stub bodies, so a port that compiles but does nothing is not called done.

Skills that know the next step

Setup installs skills next to the server, so the agent follows the right workflow without being told.

• reverse-engineer

  How does this work? Engine, stack, architecture, dependency graph, classes, scenes and unknown files.

• build-inspector

  Exported builds: engine and version, what is inside the pack, and what changed between two builds.

• rebuild

  No files: learn how a game, app or site is built, then write a measured clean-room rebuild spec.

• port-project

  Any port, unit by unit in dependency order, with API maps, converted scenes and a verified result.

• godot-port

  Godot 4 to Unity, Unreal, three.js or Godot C#: signals, node paths, autoloads, physics, input and axes.

• unity-to-godot

  Unity to Godot 4: MonoBehaviours, prefabs and scenes to .tscn, colliders and rigidbodies.

• port-verify

  The finish line: fix what is left, then hand over with an honest list of what still needs a human.

• proof-case

  Evidence, claims that cite it, decisions with what was rejected, real tests and open unknowns.

• troubleshoot

  Unreadable scenes, packs that will not list, refused paths and MCP connection problems.

The Claude Code plugin adds the port-architect agent, which runs a whole port from recon to hand-over, and guard hooks. A copied skill can be older than the tool: reverseport skills get <name> prints the one that matches your version.

What it does and does not do

So you know what to expect before you install.