Pathway: Integrator / Porter

Level: Advanced · For: porting/ingesting existing games and using the toolchain.

The route

1. The adapter seam — the adapter architecture (GameAdapter, AuthoringAdapter, system adapters).

2. Ingest unmodified games — the render-accessor trap + overlays.

3. Study real ingests — the marquee unmodified ingests: pmndrs/racing-game, simcity, and the multiplayer colyseus/realtime-tanks-demo — each a real third-party Three.js game run byte-for-byte unmodified through the ingest adapter.

4. Adapt without vendoring — custom adapters: your game keeps its own architecture and ships a small { module } adapter the editor mounts. For a full port to the native format instead, the vgai checkout carries the cheatsheets: docs/PORTING-PHYSICS.md (cannon-es/ammo.js → Rapier — required for a native port) and docs/PORTING-NETWORKING.md (hand-rolled ws/socket.io → Colyseus — vgai’s conventional stack, not an engine requirement). The decision guide between the routes is docs/BRINGING-AN-EXISTING-GAME.md.

5. Tooling & publishing — the CLI/SDK & scaffolding and hot reload, storage & web builds.

6. Lab — ingest a small Three.js demo of your own (see the “Ingest your own folder” section of the ingest tutorial), edit it, and persist the edits as an overlay.

Outcome

You can ingest an unmodified Three.js game, edit and persist it via overlays, drive the editor from the CLI/SDK, and produce a web build.