Engine and framework coverage

The task skills cover assessment and version-specific porting workflows. This is documented routing coverage, not a claim that every engine or most modern games have been ported. Existing evaluated examples remain in the README's evidence table; no new engine/browser gameplay benchmark was run for this change.

Primary starting points were reviewed on 2026-10-17. Before using a route, verify the exact project/runtime version and current matching documentation. Modern proprietary, online-only or native-middleware games can remain blocked even when their engine has some browser backend.

Engine/framework family	Task/playbook	Required material or first gate
Unity	port2browser-export	Complete matching editor project; web-compatible plugins
Godot	port2browser-export	Matching editor/templates, supported renderer/language/extensions
Unreal	port2browser-export	Exact compatible HTML5 fork and editable project; UE5 not assumed
Defold	port2browser-export	Complete collection/project and HTML5-compatible extensions
Cocos Creator	port2browser-export	Matching Creator generation, project and web plugins
GameMaker	port2browser-export	Editable project, exporter access and compatible extensions
Construct	port2browser-export	Matching project generation/addons and Web exporter
GDevelop	port2browser-export	Complete events/layouts/resources and compatible extensions
RenPy	port2browser-export	Matching editable project/SDK and supported Python/codecs
LOVE	port2browser-frameworks	Version-compatible love.js backend; native modules audited
Pygame/Python	port2browser-frameworks	Matching pygame-web runtime and Wasm-built modules
OpenFL	port2browser-frameworks	Haxe project and HTML5-compatible libraries
Heaps	port2browser-frameworks	Haxe source, compatible JS backend and resources
Bevy	port2browser-frameworks	Rust source/lockfile and chosen web renderer/features
Macroquad	port2browser-frameworks	Rust source and matching Wasm/JS bundle
libGDX	port2browser-frameworks	Source and compatible GWT/HTML module/libraries
MonoGame/XNA	port2browser-frameworks	Rebuildable source and proven browser framework/content backend
FNA	port2browser-frameworks	Source and proven browser graphics/audio/native-library backend
Electron	port2browser-web	Browser gameplay source and replacements for desktop services
NW.js	port2browser-web	Browser runtime plus compatible Node/native API substitutions
RPG Maker MV/MZ	port2browser-web	Matching JavaScript runtime and browser-compatible plugins
Phaser	port2browser-web	Browser entrypoint, plugins, physics and complete resources
PixiJS	port2browser-web	Actual game logic/runtime around renderer library and complete resources
Three.js	port2browser-web	Actual game/runtime, graphics features and complete resources
SDL/C/C++	port2browser-native	Rebuildable game/dependencies and viable renderer
Custom native engines	port2browser-native	Full dependency graph, source/rights and actual web backend
Compatible open engines	port2browser-open-runtime	Exact game/data format compatibility and separate rights
Legacy emulation	port2browser-open-runtime	Exact platform/backend support, game data/firmware rights and usable performance
raylib	port2browser-native	Rebuildable game/raylib source and matching web graphics backend
Go / Ebitengine	port2browser-frameworks	Go/module source, matching wasm_exec.js and compatible packages
HaxeFlixel	port2browser-frameworks	Editable Haxe project and matching Lime/OpenFL/addons
Flash / Ruffle	port2browser-open-runtime	Exact SWF/APIs/resources and a proven compatible Ruffle revision
Java applets / CheerpJ	port2browser-open-runtime	Applet/JAR and dependencies, matching runtime and deployment terms
ScummVM	port2browser-open-runtime	Supported exact game edition/data and browser build including its engine
Adventure Game Studio	port2browser-open-runtime	Matching editable project or compatible game data, runtime/plugins
Flutter / Flame	port2browser-frameworks	Editable Dart/Flutter project with compatible web plugins and renderer

For every game, prove an actual scene before expanding scope. Record renderer, plugins, OS/services, threading, asset/decoded-memory budgets, data rights and browser evidence. Web export availability is distinct from project availability, rebuildable dependencies, feasible performance and preserved gameplay.

The machine-readable catalog supplies identifiers and prerequisites, not scores or a supported boolean. Catalog candidate IDs are navigation labels; the inspector detects only a subset, not every catalog entry. Inspector task hints remain inferred leads. Unknown engines still enter recon/route selection rather than being excluded or assigned invented compatibility.

The task-folder/playbook organization is inspired by universal-modder (revision b8675c1). Port2browser's instructions are written for browser porting; no universal-modder code, tools, hooks, MCP configuration or paid asset service is bundled. Modding or native hooks do not establish a browser runtime. Optional REA remains an investigation resource.