Toolkit for AI-assisted browser ports of classic games

What to build

A packaged AI-assisted game-porting toolkit — decompiler/recompiler scripts, asset converters, and input-mapping templates that turn native console/PC game binaries into WebAssembly + WebGL browser builds — sold as a starter kit or paid template to romhackers, emulation hobbyists, and small studios porting games they have rights to (open-source engines, abandonware, or their own titles).

AI-assisted decompilation plus WASM/WebGL recompilation has lowered the skill floor for turning legacy game binaries into browser-playable ports, creating demand for a reusable, templatized pipeline rather than one-off hacks.

Demand

Retro gaming fans, romhacking/decomp communities, and solo 'vibe coders' who saw the Halo/Simpsons/GTA browser ports circulate want the same workflow for other titles, but lack a packaged toolchain and are currently re-deriving the pipeline from scratch.

• Hacker NewsNews

  Vibe coded browser ports of Halo, The Simpsons: Hit And Run, GTA work well — 90 points, 75 comments on HN; high engagement at the source.

• Decompilation/recompilation hobbyist projects (e.g. N64Recomp-based PC ports, EmulatorJS)Other

  Existing open-source decompilation and recompilation toolchains for other legacy titles have built active contributor and user communities, indicating an established hobbyist appetite for tooling that converts native game code into portable/web-runnable form.

Stack

• Emscripten (C/C++ to WASM)
• Ghidra (reverse engineering/decompilation)
• WebGL / WebGPU
• Claude or GPT API for AI-assisted code translation and asset format inference
• Three.js or Babylon.js for in-browser rendering
• Cloudflare Pages or Vercel for static hosting of ports

Solo + AI difficulty

The AI-assisted decompilation step is the hard part — physics, shader, and asset-format quirks differ per game engine, so a truly generic toolkit is harder than the viral demos suggest; the easy part is packaging known-working scripts (asset converters, input mappers) for a handful of similar-engine titles. Realistic MVP for 2-3 supported games/engines: 4-8 weeks solo with AI assistance, longer if aiming for a broad multi-engine toolkit.

Entry threshold

Requires moderate technical depth in reverse engineering, WebAssembly, and graphics APIs, achievable solo with AI assistance over several weeks; legal risk around copyrighted assets and engines limits how openly this can be monetized.

Window

3-6 months

Where to find first users

• r/emulation and r/ROMHacking
• Hacker News (already one viral thread to follow up on)
• itch.io for selling ports or toolkit templates
• Discord servers for decomp/recomp communities (e.g. Zelda64, N64Recomp-adjacent servers)

Competitors

• EmulatorJS
• Ship of Harkinian
• N64Recomp

Counter-signals & risks

• Unauthorized browser ports of Halo, GTA, and The Simpsons: Hit and Run carry unresolved copyright/IP exposure since Microsoft/343, Rockstar/Take-Two, and the Simpsons rights holders have not authorized them.

• A 'works well' demo for a few titles may not generalize into a reliable templated pipeline — physics, shaders, and asset formats often need game-specific manual fixes, which undermines a one-size-fits-all toolkit business model.

• Rights holders could issue DMCA takedowns or cease-and-desist actions against both the ports and any commercial toolkit that facilitates unauthorized derivative works, creating legal risk for sellers and buyers alike.