Godot Engine vs Phaser

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Phaser
   Godot Engine—none0/10

   Explicit probes show no llms.txt (404 at docs.godotengine.org/llms.txt), no .md doc mirrors, and no agent-oriented docs endpoint; the only doc format is standard human-facing HTML documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser~partialprobed6/10

   A live llms.txt was found at phaser.io/llms.txt (an examples-API index) and Phaser Studio publishes agent-oriented docs/MCP server pages (phaser.io/agent/mcp) explicitly for connecting coding agents, but the more commonly probed docs.phaser.io/llms.txt returns 404 and the site root 403s non-browser clients, requiring a browser UA and precise deep links to succeed. Missing for 10: a consistently discoverable llms.txt across the main docs domain, no 403/404 friction for automated agent fetches, and independent confirmation that agents can reliably ingest these docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.phaser.io/llms.txt”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Godot Engine
   Godot Engine✓fullprobed8/10

   Godot documents an official CLI for command-line work and headless operation is explicitly confirmed via runtime probe (`godot --headless` for CI builds, exports, and scripted editor automation), plus EditorScript for scripted automation and one-click exports supporting CI pipelines. Missing for 10: no first-party CI/CD documentation or GitHub Actions template explicitly walking through a CI setup, and no independent hands-on report confirming headless CI use in the wild.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [github] “Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platfor…”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser—none0/10

   The evidence pack covers installation, scenes, physics, animations, editor and MCP agent features, but nothing addresses headless execution or CI-based automation for Phaser games/tests. Since browser-based game engines can in principle support headless rendering or CI test harnesses, this is a fair but unaddressed axis rather than a category error.

   ⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Phaser
   Godot Engine—none0/10

   Evidence explicitly shows no official Godot MCP server exists (GitHub org search for 'mcp' returns 0 results, no llms.txt, no official endpoint); only third-party community MCP projects exist. The axis applies since Godot could plausibly ship an official MCP integration for editor automation, but no such first-party offering is documented.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser✓fullprobed7/10

   Phaser Studio ships an official 'Phaser Game Agent' MCP server (phaser.io/agent/mcp) documented with 40+ specialized tools and explicit integration with Claude Desktop, Cursor, and GitHub Copilot, letting external agents connect and build games via plain-language commands. Missing for 10: independent/hands-on community validation that the MCP server works as advertised, and clarity on self-hosted/npm distribution (probe found no @phaserjs MCP package on npm, only a hosted endpoint).

   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [claimed-docs] “Give the player a double-jump and a coin counter.The jump feels floaty, make gravity stronger.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Godot Engine
   Godot Engine✓fullprobed7/10

   Godot ships an official command-line interface (godot binary with --headless, export, script-run flags) documented extensively and confirmed via runtime probe, enabling scripted/agentic automation such as CI builds and exports. Missing for 10: no AI-specific CLI features (e.g., structured/agent-friendly output modes), no independent hands-on validation of CLI scripting workflows beyond docs, and no llms.txt or machine-readable docs mirror.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser~partialclaimed5/10

   Phaser docs confirm an official CLI tool for scaffolding projects (interactive selection of templates/demo games), which counts as an official CLI, but it is described as interactive Q&A rather than a scriptable/agent-friendly interface, and there's no documentation of flags or non-interactive mode suited for AI-native automated use. missing for 10: evidence of non-interactive/programmatic CLI flags, AI-agent-oriented CLI documentation, and independent confirmation of CLI usability by agents.

   • [claimed-docs] “This CLI tool presents an interactive selection of official project templates and demo games.”
   • [claimed-docs] “This CLI tool presents an interactive selection of official project templates and demo games. Issue the command, answer some questions and t…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Phaser
   Godot Engine~partialprobed6/10

   Godot exposes a documented, scriptable surface (command-line/headless mode, EditorScript for in-editor automation, full GDScript/C# class API, and a keyless JSON Asset Library API) that an agent could drive programmatically, per godot-docs-3/5/12/14 and godot-probe-rt-1/2. However this is a traditional engine API/CLI, not an AI-native interface: probes confirm no llms.txt, no OpenAPI spec, and no official MCP server (godot-probe-1/2/3, godot-probe-rt-3), leaving only third-party community MCP wrappers of uneven maintenance. Missing for 10: an official machine-readable API spec (OpenAPI/llms.txt) and a first-party MCP or agent-oriented interface layer.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the Godot Asset Library exposes a keyless JSON API — GET godotengine.org/asset-library/api/asset?godot_…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.godotengine.org/openapi.json, https://docs.godotengine.org/swagger.json, https://docs.g…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser✓fullprobed8/10

   Phaser ships an extensive, versioned public JS/TS API (Scenes, physics, input, loader, animations) documented at docs.phaser.io with full TypeScript definitions, which is exactly the kind of documented public API an AI agent needs to generate/drive game code programmatically; the runtime probe also shows phaser.io/llms.txt now serving a live, programmatic examples-API index tailored for AI consumption. Missing for 10: a formal machine-readable spec (OpenAPI) for the core API surface — probes show OpenAPI/swagger endpoints all 404 — so discovery still relies on human-oriented docs rather than a fully machine-consumable contract.

   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”
   • [claimed-docs] “This will allow you to control the Sprite using the built-in physics functions, such as velocity, acceleration, gravity, etc.”
   • [claimed-docs] “Phaser maintains a unified input system that works across all browsers and devices.”
   • [claimed-docs] “Common asset types include images, texture atlases, sprite sheets, fonts, audio files and JSON data, but there are many more that Phaser can…”
   • [claimed-docs] “Animations are created via the Animation Manager.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.phaser.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.phaser.io/openapi.json, https://docs.phaser.io/swagger.json, https://docs.phaser.io/api…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Phaser
   Godot Engine~partialprobed6/10

   Godot ships official, well-documented SDKs/language bindings — GDScript, C# via .NET, and GDExtension/C++ — plus a command-line interface and a queryable Asset Library JSON API, all of which an AI-native developer could build against (godot-docs-1, godot-docs-2, godot-docs-8, godot-docs-3, godot-probe-rt-2). However, there is no AI/agent-specific SDK, no official MCP server, and no machine-readable docs (llms.txt/.md mirrors return 404), with only unofficial community MCP projects filling that gap. Missing for 10: an official AI-agent SDK or MCP server, machine-readable/llms.txt documentation, and first-party AI integration tooling.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [claimed-docs] “Keep your code modular with an object-oriented API using Godot's own GDScript, C#, C++, or bring your own using GDExtension.”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the Godot Asset Library exposes a keyless JSON API — GET godotengine.org/asset-library/api/asset?godot_…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”

   proof ↗⚑ flag

   Phaser✓fullcommunity8/10

   Phaser itself is the official SDK: it's distributed via npm, an official CLI, a CDN, and ships full TypeScript definitions, all documented in first-party docs and corroborated by community usage (games built in JS/TS, TypeScript experience feedback). Missing for 10: independent/third-party audit of the SDK's completeness and explicit multi-platform SDK packaging (e.g., official native wrappers) beyond docs claims.

   • [claimed-docs] “npm install phaser”
   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”
   • [claimed-docs] “Install via [npm](https://www.npmjs.com/package/phaser): npm install phaser”
   • [claimed-docs] “This CLI tool presents an interactive selection of official project templates and demo games. Issue the command, answer some questions and t…”
   • [claimed-docs] “Phaser is on jsDelivr which is a "super-fast CDN for developers". Include _either_ of the following in your html”
   • [github] “You can use JavaScript or TypeScript for development.”
   • [community] “I've spent the past 6 months building a game using Phaser and TypeScript. On the whole, it's been a great experience... one of the worst par…”
   • [community] “Phaser 4 was announced ~four years ago and was an attempt to get the project written natively in TypeScript. It looks pretty dead in the wat…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Godot Engine—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Godot Engine
   Godot Engine~partialprobed3/10

   Godot's headless CLI mode and EditorScript/plugin system let scripts run without the GUI (e.g., for CI builds/exports), which can be wired into external schedulers or automation pipelines, but there is no built-in agent/automation-scheduling framework or AI-native background-task system documented. missing for 10: native scheduling/trigger system, evidence of persistent background agents, AI-specific automation hooks, independent confirmation of autonomous unattended runs beyond CI export scripts.

   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”

   proof ↗⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Godot Engine—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Phaser—none0/10

   Phaser's AI-related evidence (phaser-docs-13/14/15) describes an MCP server that lets *external* coding agents (Claude Desktop, Cursor, Copilot) call Phaser Editor tools — the opposite relationship of a built-in assistant living inside the product that a user delegates tasks to. No evidence shows a native, in-product chat/assistant feature.

   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Phaser
   Godot Engine—none0/10

   Evidence shows only conventional scripting (GDScript, C#), CLI tooling, and editor plugin APIs — none of which constitute natural-language command operation. No official MCP server or NL interface exists (GitHub search for org:godotengine mcp returns 0 results), and only unofficial third-party community MCP projects (godot-mcp, godot-ai) exist, which are not part of the product itself.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser✓fullprobed7/10

   Phaser ships an official hosted 'Game Agent' MCP server that lets users describe changes in plain language (e.g., 'Give the player a double-jump...') and have the agent call over 40 specialised tools inside the Scene Editor, integrating with Claude Desktop, Cursor, and Copilot — directly matching natural-language operation. This is corroborated by a runtime probe confirming the live MCP endpoint at phaser.io/agent/mcp. Missing for 10: independent/community hands-on validation of the MCP agent's reliability and no npm-distributed MCP package (only hosted), so evidence is vendor-only.

   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [claimed-docs] “Give the player a double-jump and a coin counter.The jump feels floaty, make gravity stronger.”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Phaser
   Godot Engine—none0/10

   Godot ships extensive static class/API reference docs (godot-docs-1–17) but none of the evidence shows an interactive reference with runnable/executable code examples (no REPL, playground, or in-browser code execution is mentioned), and probes confirm no llms.txt, no OpenAPI spec, and no .md-mirrored interactive docs.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.godotengine.org/openapi.json, https://docs.godotengine.org/swagger.json, https://docs.g…”

   proof ↗⚑ flag

   Phaser~partialprobed5/10

   Community evidence confirms Phaser has an extensive examples library ('many examples and docs to work from' — phaser-comm-7), and a runtime probe shows docs.phaser.io/llms.txt now serves as a programmatic examples-API index with endpoints to fetch full source code per example (phaser-probe-rt-1), which is useful for AI-native exploration. However, there is no first-party evidence of an interactive, runnable-in-browser API reference (no OpenAPI/API-reference page found, docs-md and llms.txt initially 404'd per probes), so the story is only partially substantiated. Missing for 10: dedicated interactive API reference UI with live code execution, confirmation the examples API is documented/stable, independent hands-on account of using it.

   • [community] “I've made a couple toy projects with Phaser, after comparing other Javascript based 2d engines. Phaser is the most fully featured amongst th…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.phaser.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.phaser.io/phaser/getting-started/what-is-phaser.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Phaser
   Godot Engine—none0/10

   Godot is a game engine, not a web/service API, but the story is about whether a machine-readable API spec (OpenAPI or equivalent) can be downloaded — probes explicitly show no OpenAPI/swagger endpoints exist (all 404s) and no llms.txt equivalent either, so the applicable axis yields no evidence of delivery.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.godotengine.org/openapi.json, https://docs.godotengine.org/swagger.json, https://docs.g…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser~partialprobed4/10

   Phaser ships full TypeScript type definitions (phaser-docs-4) which function as a machine-readable description of its API surface and can be consumed by tooling/agents, but there is no formal OpenAPI/Swagger spec or comprehensive llms.txt for the full API — probes confirm openapi.json/swagger.json 404 and the only live llms.txt is a narrow examples-index API, not a full API spec (phaser-probe-1, phaser-probe-3, phaser-probe-rt-1). missing for 10: a dedicated OpenAPI/JSON-schema style spec covering the full public API, and an official downloadable machine-readable spec beyond TS typings/examples index.

   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.phaser.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.phaser.io/openapi.json, https://docs.phaser.io/swagger.json, https://docs.phaser.io/api…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Godot Engine—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Godot Engine—none0/10

   The evidence pack contains no documentation of a versioned API policy or deprecation schedule for Godot's scripting/engine APIs (GDScript, C#, GDExtension); community notes only mention version differences (3.5.2 LTS vs 4.0) informally, not a documented deprecation policy. Since engine APIs could plausibly have such policies, absence of evidence yields 'none' rather than 'na'.

   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”

   proof ↗⚑ flag

   Phaser—none0/10

   No evidence of a documented deprecation policy, semver commitments, or API-stability guarantees; the only version-related evidence notes Phaser 2→3 broke compatibility ("States"... won't work in Phaser 3) with no stated migration/deprecation process, and probes found no OpenAPI/versioned docs artifacts.

   • [claimed-docs] “If you find any reference to States in code or a tutorial you've found online, it's for Phaser 2 and likely won't work in Phaser 3.”
   • [community] “Phaser 4 was announced ~four years ago and was an attempt to get the project written natively in TypeScript. It looks pretty dead in the wat…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.phaser.io/openapi.json, https://docs.phaser.io/swagger.json, https://docs.phaser.io/api…”

   proof ↗⚑ flag

Agent editor

1. ai-native userAn agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface

   weight 3 · round to Phaser
   Godot Engine~partialprobed6/10

   Godot documents multiple genuine programmatic surfaces — GDScript/C# scripting, EditorScript for in-editor automation, EditorPlugin for extending the editor, and a full command-line interface supporting headless mode and export/build triggering — which together let a script or external process create scenes/nodes, edit properties, and build. However these are general-purpose developer APIs, not an agent-oriented interface, and there is no official MCP server or agent-facing wrapper (GitHub search found zero official MCP results, llms.txt 404s, only community MCP projects of varying activity). Missing for 10: an official/first-party agent-facing API or MCP server, and independent hands-on evidence of an agent actually driving the editor end-to-end via these interfaces.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “It can be made entirely with GDScript and standard scenes, without even reloading the editor.”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser✓fullprobed8/10

   Phaser Studio ships an official 'Phaser Game Agent' MCP server with 40+ specialized tools that integrates with Claude Desktop, Cursor, GitHub Copilot and other MCP clients, letting an agent create particle emitters, reorganize scenes into layers, rename objects, tweak physics/animations, and add filters via natural-language commands routed through documented tool calls — directly matching the 'agent drives the editor programmatically' story. Runtime probe confirms the hosted MCP endpoint is live and documented at phaser.io/agent/mcp. missing for 10: independent/hands-on third-party verification that the MCP tools reliably perform builds/edits, and a published open API/tool reference (npm package) beyond the marketing page.

   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [claimed-docs] “Give the player a double-jump and a coin counter.The jump feels floaty, make gravity stronger.”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

Codegen

1. ai-native userLLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen

   weight 2 · round to Phaser
   Godot Engine~partialcommunity4/10

   Godot's GDScript/C# APIs are extensively documented (godot-docs-1/2) and the engine has a large public codebase/asset library that could supply LLM training examples, but there is no direct evidence about LLM-generated code success rates, and community reports note documentation gaps in the past and major GDScript/API syntax breaks between Godot 3 and 4 (godot-comm-11, godot-comm-14, godot-comm-15) that would fragment what models have seen. missing for 10: direct evidence of LLM code-generation success, confirmation that version-specific API drift (3.x vs 4.x GDScript) doesn't cause mismatched generations, independent benchmarks of first-try correctness.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”
   • [community] “gdscript is pretty awful. It's only python-like for someone who's never used python. No list comprehensions, no tuples... It's like Python 1…”
   • [community] “I have tried to use it something like 2 years ago and just gave up in front of the poorly documented custom scripting language they used.”

   proof ↗⚑ flag

   Phaser~partialcommunity6/10

   Phaser has extensive first-party docs, TypeScript definitions, and a long history (widely used since ~2013) that HN commenters confirm produced 'many examples and docs to work from' and 'great documentation,' supporting LLM familiarity. However, other independent reports directly contradict doc quality ('worst documentation... very bad design') and TypeScript support is described as a 'best-effort' bolt-on rather than native, plus the docs explicitly warn that pre-Phaser-3 tutorials/code (States) will not work — all of which undercut first-try reliability for LLM-generated code. Missing for 10: no direct evidence of LLM-generated Phaser code being tested/benchmarked, no resolution of the conflicting doc-quality reports, and no confirmation that the API has stabilized enough to avoid version-mismatch pitfalls.

   • [community] “I've made a couple toy projects with Phaser, after comparing other Javascript based 2d engines. Phaser is the most fully featured amongst th…”
   • [community] “After trying out several HTML5/JS game libraries, I'm pretty sure that Phaser is the best one for 2D games. It has frequent updates, great d…”
   • [community] “I've spent the past 6 months building a game using Phaser and TypeScript. On the whole, it's been a great experience... one of the worst par…”
   • [community] “The documentation of Phaser is the worst i've seen to a popular framework. The website is very bad in the design, styling as well as content…”
   • [community] “It's still rough around the edges, but I have no doubt Phaser 3 will get to feature complete. What's holding me back is lack of TypeScript d…”
   • [community] “Phaser 4 was announced ~four years ago and was an attempt to get the project written natively in TypeScript. It looks pretty dead in the wat…”
   • [claimed-docs] “If you find any reference to States in code or a tutorial you've found online, it's for Phaser 2 and likely won't work in Phaser 3.”
   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”

   proof ↗⚑ flag

Copilot

1. ai-native userAn official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets

   weight 2 · round to Phaser
   Godot Engine—none0/10

   No evidence of any official AI assistant built into the Godot editor for generating scripts, answering API questions, or scaffolding scenes; the evidence pack only shows scripting languages, plugins, CLI tools, and asset import pipelines — plus explicit probes confirming no official MCP/AI integration exists and only unofficial community projects (e.g., godot-mcp, godot-ai) fill the gap.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   Phaser~partialprobed6/10

   Phaser Studio ships an official 'Phaser Game Agent' MCP server with 40+ specialized tools that integrates with Claude Desktop, Cursor, and Copilot, letting users describe changes in plain language (e.g. 'give the player a double-jump', 'create a particle emitter, reorganise a scene into layers') and have the agent execute them in the editor — directly matching the scaffolding/scripting parts of the story. However this is a separate hosted MCP server/agent rather than an assistant embedded 'inside the engine' itself, and there's no evidence it specifically answers API/documentation questions, nor any independent hands-on corroboration of its effectiveness. Missing for 10: evidence of API Q&A capability, first-party/independent hands-on validation of code-generation quality, and confirmation it's embedded in-engine rather than an external connected tool.

   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [claimed-docs] “Give the player a double-jump and a coin counter.The jump feels floaty, make gravity stronger.”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”

   proof ↗⚑ flag

Formats

1. technical artistStandard interchange formats — glTF, FBX, USD — import cleanly

   weight 2 · round drawn
   Godot Engine—none0/10

   The evidence pack only describes Godot's generic asset-import pipeline (auto-import to res://.godot/imported/, bulk import parameter changes) but never mentions glTF, FBX, or USD specifically, nor any hands-on report of clean or problematic imports for these formats — missing for 10: explicit glTF/FBX/USD import documentation, fidelity/compatibility notes, and any community corroboration of import quality for technical artists.

   • [claimed-docs] “Godot will automatically import these files internally and keep the imported resources hidden in a res://.godot/imported/ folder.”
   • [claimed-docs] “Changing the import parameters of several assets at the same time is also possible.”
   • [claimed-docs] “To import assets in Godot, place your assets (image files, scenes, audio files, fonts, etc) directly in the project folder.”

   proof ↗⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Import

1. technical artistAsset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one

   weight 2 · round to Godot Engine
   Godot Engine~partialprobed6/10

   Docs confirm Godot auto-imports assets on drop-in and supports batch-editing import parameters across multiple assets at once, plus a general editor-plugin/EditorScript system and headless CLI usable for scripted automation (godot-docs-9, godot-docs-15, godot-docs-17, godot-docs-4/13, godot-docs-5/14, godot-probe-4, godot-probe-rt-1). However, the evidence never names Godot's specific import-hook API (e.g., EditorImportPlugin/postimport scripts) or shows a documented pipeline-scripting workflow purpose-built for technical artists. Missing for 10: explicit documentation of custom import plugin/hook APIs, real-world pipeline-script examples, and independent corroboration that artists use this for hands-off batch processing.

   • [claimed-docs] “Godot will automatically import these files internally and keep the imported resources hidden in a res://.godot/imported/ folder.”
   • [claimed-docs] “Changing the import parameters of several assets at the same time is also possible.”
   • [claimed-docs] “To import assets in Godot, place your assets (image files, scenes, audio files, fonts, etc) directly in the project folder.”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “It can be made entirely with GDScript and standard scenes, without even reloading the editor.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser—none0/10

   Phaser's docs cover its runtime Loader for fetching common asset types (images, atlases, audio) and an editor/MCP agent for interactive scene building, but there is no evidence of asset-import automation tooling (import hooks, preset-based pipelines, or scripts that batch-process incoming source assets before they reach the game) as a build-time pipeline feature. Missing for 10: any documented import-hook API, preset/config-driven asset processing, or pipeline scripting for automating asset ingestion.

   • [claimed-docs] “Common asset types include images, texture atlases, sprite sheets, fonts, audio files and JSON data, but there are many more that Phaser can…”
   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “Add and configure filters visually — Glow, Shadow, Blur, Pixelate, Bokeh, ColorMatrix, Displacement and more — directly in the Scene Editor'…”

   proof ↗⚑ flag

Marketplace

1. game developerA large asset store or package ecosystem gives me ready-made models, tools, and plugins

   weight 2 · round to Godot Engine
   Godot Engine✓fullprobed7/10

   Godot ships an official Asset Library with categorized listings (2D/3D Tools, Shaders, Materials, Scripts, Templates, Projects, Demos) and a public JSON API for querying it, directly matching the asset-store/package-ecosystem story. Missing for 10: independent evidence of the store's actual scale/quality (e.g. asset counts, community praise of the marketplace itself) and any third-party commentary comparing it to competitor stores.

   • [claimed-docs] “Godot Asset Library ... Category Any 2D Tools 3D Tools Shaders Materials Tools Scripts Misc Templates Projects Demos”
   • [probe] “PROBE runtime (recorded 2026-09-15): the Godot Asset Library exposes a keyless JSON API — GET godotengine.org/asset-library/api/asset?godot_…”

   proof ↗⚑ flag

   Phaser—none0/10

   Evidence covers Phaser's editor, MCP agent tooling, npm install, CDN and framework integrations, but there is no mention of a dedicated asset store, marketplace, or curated plugin ecosystem (à la Unity Asset Store) offering ready-made models/tools/plugins. Missing for 10: evidence of an official or third-party asset marketplace, a plugin registry, or curated ready-made asset packages.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Godot Engine
   Godot Engine~partialclaimed4/10

   Godot supports batch editing of import parameters across multiple assets (godot-docs-15), EditorScript for custom in-editor automation (godot-docs-5/14), and CLI/headless scripting for automated workflows (godot-docs-3/12), which together enable some bulk operations. However there's no dedicated bulk-editing API, no evidence of scripted bulk scene/node manipulation at scale, and no AI-native tooling or examples of large-scale automated bulk operations. Missing for 10: dedicated bulk-edit API/tooling, documented examples of scripted bulk operations across many scenes/nodes, AI-agent-oriented automation examples, independent corroboration of bulk-operation workflows.

   • [claimed-docs] “Changing the import parameters of several assets at the same time is also possible.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”

   proof ↗⚑ flag

   Phaser~partialclaimed3/10

   The Editor/MCP agent evidence mentions handling tasks like renaming multiple objects and reorganizing scenes without switching tools, implying some bulk-editing capability, but there's no detailed documentation of a systematic bulk-operations API or workflow for AI agents. Missing for 10: explicit bulk-edit tooling/API docs, examples of batch operations across many assets/scenes, and independent confirmation of this capability working at scale.

   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Godot Engine—none0/10

   The evidence pack covers GDScript, C#, plugins, EditorScript, and CLI tooling, but never mentions Godot's signal/event system or any explicit mechanism for defining rules that auto-trigger actions on events; without a citable capability, this is unsupported. missing for 10: any documentation of signals/event-connection APIs, examples of automated rule-triggering, or AI-oriented automation hooks.

   ⚑ flag

   Phaser—none0/10

   Phaser's docs mention a unified input system and scene lifecycle events, but no evidence describes a rule-engine or declarative trigger system where events automatically fire configured actions (e.g., an event-emitter/automation API is never documented in the pack). Missing for 10: documentation of an event-emitter/listener API, examples of rule-based automation, and any AI-native tooling for defining trigger→action rules.

   • [claimed-docs] “Phaser maintains a unified input system that works across all browsers and devices.”
   • [claimed-docs] “Typical uses for a Scene would be a Loading Screen, a Main Menu, a Game Level, a Boss Fight, an in-game Item Shop, a High Score Table, etc.”
   • [claimed-docs] “you can pause, resume and sleep a Scene at will, and that you can easily run multiple Scenes at the same time.”

   proof ↗⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Godot Engine—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2d

1. game developer2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought

   weight 2 · round to Phaser
   Godot Engine✓fullcommunity7/10

   First-party docs explicitly market Godot's 'dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes,' distinguishing 2D as first-class rather than a 3D afterthought, and the asset library segments 2D vs 3D tools, reinforcing separate 2D-focused workflows. Community threads corroborate Godot's strength and ease relative to competitors for indie/2D-style projects, though none specifically praise tilemaps or 2D physics. Missing for 10: explicit documentation/evidence on TileMap editor and 2D physics engine (Box2D-like) specifics, and independent hands-on confirmation of 2D-specific workflow quality.

   • [claimed-docs] “Make crisp and performant 2D games with Godot's dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes.”
   • [claimed-docs] “Godot Asset Library ... Category Any 2D Tools 3D Tools Shaders Materials Tools Scripts Misc Templates Projects Demos”
   • [claimed-docs] “Godot's Node and Scene system gives you both power and flexibility to create anything.”
   • [community] “I'm using it every day at work... Godot was just what I needed since I wanted a visual editor but still be able to code. The scripting langu…”

   proof ↗⚑ flag

   Phaser✓fullcommunity9/10

   Phaser's docs and community feedback confirm sprites, scenes, arcade physics, animations, tilemaps/atlases, and input are core, well-documented primitives rather than bolted-on features, and community comments reinforce it as a dedicated 2D engine (comparisons to Pixi/Love2D, 'fits 2D, sprites, tilemaps, physics'). missing for 10: independent hands-on benchmarking of tilemap-specific workflows and no explicit dedicated tilemap doc excerpt in the pack (only physics/scenes/animations/input are directly quoted).

   • [claimed-docs] “Typical uses for a Scene would be a Loading Screen, a Main Menu, a Game Level, a Boss Fight, an in-game Item Shop, a High Score Table, etc.”
   • [claimed-docs] “it's a common practise to have a Scene dedicated entirely to handling the UI for your game, that is rendered above all other Scenes”
   • [claimed-docs] “This will allow you to control the Sprite using the built-in physics functions, such as velocity, acceleration, gravity, etc.”
   • [claimed-docs] “Phaser maintains a unified input system that works across all browsers and devices.”
   • [claimed-docs] “Common asset types include images, texture atlases, sprite sheets, fonts, audio files and JSON data, but there are many more that Phaser can…”
   • [claimed-docs] “Animations are created via the Animation Manager.”
   • [community] “It's a great tool if you go for a game that fits this framework - 2D, sprites, tilemaps, physics... After experimenting a little with phaser…”
   • [community] “Phaser is the perfect framework to get started making HTML5 2D games.”

   proof ↗⚑ flag

Performance

1. game developerProfile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy

   weight 2 · round drawn
   Godot Engine—none0/10

   The evidence pack contains no mention of Godot's built-in profiler, ECS, job/threading system, or MultiMesh/instancing APIs for scaling heavy scenes; only a community note that hitting high framerates may require dropping to C++/GDExtension, which doesn't confirm profiling or data-oriented tooling. missing for 10: evidence of a real profiler UI, ECS support, job/threading system, and instancing APIs for scaling.

   • [community] “The other con will likely be around performance, it's passable at 90hz, but if you want to start hitting framerates like 144hz, the critical…”

   proof ↗⚑ flag

   Phaser—none0/10

   The evidence pack shows no mention of a built-in profiler, ECS architecture, job system, or instancing support for scaling heavy scenes; Phaser's docs and community discussion focus on Scenes, Arcade physics, animations, and rendering (Canvas/WebGL) with only a passing complaint about relative rendering FPS. Nothing indicates data-oriented performance tooling exists.

   • [claimed-docs] “Typical uses for a Scene would be a Loading Screen, a Main Menu, a Game Level, a Boss Fight, an in-game Item Shop, a High Score Table, etc.”
   • [claimed-docs] “This will allow you to control the Sprite using the built-in physics functions, such as velocity, acceleration, gravity, etc.”
   • [community] “The framework is good, however I got faster (fps wise) results using my own rendering functions on Canvas than I was getting using their ren…”

   proof ↗⚑ flag

Physics

1. game developerBuilt-in physics — rigid bodies, collisions, raycasts — works out of the box

   weight 2 · round to Phaser
   Godot Engine—none0/10

   The evidence pack contains no mention of Godot's physics system, rigid bodies, collision detection, or raycasting APIs — only general engine features like 2D rendering, node/scene system, scripting, and export tooling are cited. Absence of evidence for this applicable core-engine capability means it cannot be credited as full/partial.

   ⚑ flag

   Phaser~partialcommunity6/10

   Docs confirm a built-in Arcade Physics system providing velocity, acceleration, gravity, and collision handling out of the box, and community testimony (phaser-comm-13) lists physics as a core built-in feature, but the pack explicitly notes Arcade physics 'does have its limitations' (phaser-docs-24) and never mentions raycasting or full rigid-body dynamics (e.g., Matter.js integration) with concrete examples. Missing for 10: explicit raycast API evidence, rigid-body/Matter physics documentation, and independent confirmation of collision accuracy beyond Arcade's simplified AABB model.

   • [claimed-docs] “This will allow you to control the Sprite using the built-in physics functions, such as velocity, acceleration, gravity, etc.”
   • [claimed-docs] “It's very fast and easy to use, with lots of helper functions, but due to its nature it does have its limitations.”
   • [community] “It's a great tool if you go for a game that fits this framework - 2D, sprites, tilemaps, physics... After experimenting a little with phaser…”

   proof ↗⚑ flag

Rendering

1. game developerThe engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing

   weight 3 · round drawn
   Godot Engine—none0/10

   The evidence pack documents Godot's 2D rendering engine explicitly (godot-docs-7) but contains no mention of a 3D renderer, PBR materials, global illumination/baked lighting, shadows, or post-processing pipeline anywhere in the docs, GitHub, or community citations.

   • [claimed-docs] “Make crisp and performant 2D games with Godot's dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes.”
   • [claimed-docs] “Godot's Node and Scene system gives you both power and flexibility to create anything.”

   proof ↗⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Collaboration

1. studio leadThe project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaboration

   weight 2 · round drawn
   Godot Engine—none0/10

   The evidence pack contains no mention of Godot's text-based .tscn/.tres scene format, scene diffability, merge-friendly project files, or built-in team-collaboration tooling — only general references to the node/scene system, asset import pipeline, and PR review practices for the engine's own codebase, none of which address version-control friendliness of authored projects.

   ⚑ flag

   Phaser—none0/10

   The evidence pack covers installation, scenes, physics, animation, and a visual Scene Editor, but nothing addresses version-control friendliness, mergeable/diffable scene file formats, or built-in multi-person collaboration tooling. While Phaser's code-first nature implies plain-text source files, there is no explicit documentation of scene file format diffability, conflict resolution, or team collaboration features for the visual editor.

   ⚑ flag

Editor

1. technical artistA full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels

   weight 3 · round to Godot Engine
   Godot Engine✓fullcommunity8/10

   Godot's core identity is a visual editor built around a Node/Scene composition system (scenes act as prefabs), inspector for property editing, and viewport for level/scene building, well documented across docs (scene system, import pipeline, plugins extending editor tools) and corroborated by community users praising it as 'a visual editor but still be able to code' compared favorably to more code-heavy alternatives. missing for 10: no dedicated hands-on walkthrough of viewport/inspector UI specifics or prefab-equivalent scene-instancing workflow details, and some community comments note friction for beginners with non-visual-scripting workflows.

   • [claimed-docs] “Godot's Node and Scene system gives you both power and flexibility to create anything.”
   • [claimed-docs] “Godot will automatically import these files internally and keep the imported resources hidden in a res://.godot/imported/ folder.”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [community] “I'm using it every day at work... Godot was just what I needed since I wanted a visual editor but still be able to code. The scripting langu…”
   • [community] “For beginners Godot is not as intuitive as other engines (e.g. Unreal with it's visual blueprints). For people with programming experience I…”

   proof ↗⚑ flag

   Phaser~partialclaimed5/10

   Phaser Studio ships an official visual Scene Editor with drag-and-drop placement, a real-time Inspector for effects/physics/animations, and scene reorganization into layers (phaser-docs-12, phaser-docs-27, phaser-docs-29), which covers viewport/inspector/scene-composition claims. However, core Phaser itself remains a code-first framework, prefab workflows are never explicitly named, and all evidence is first-party marketing with zero independent/hands-on corroboration of the editor's actual level-building workflow. Missing for 10: explicit prefab/reusable-component system documentation, independent reviews or hands-on reports of the editor, and clarity on how central this paid add-on editor is versus code-based scene building.

   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “Add and configure filters visually — Glow, Shadow, Blur, Pixelate, Bokeh, ColorMatrix, Displacement and more — directly in the Scene Editor'…”
   • [claimed-docs] “Pixel art, tilemap & atlas editors * SFX & music generation”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”

   proof ↗⚑ flag

Extensibility

1. game developerExtend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically

   weight 3 · round to Godot Engine
   Godot Engine✓fullprobed9/10

   Godot has first-party, well-documented mechanisms for editor extension: EditorPlugin/plugin system for custom scenes/asset manipulation without reloading the editor, EditorScript for scripted one-off editor automation runnable via Ctrl+Shift+X, and a CLI/headless mode enabling scripted automation of the editor itself. The Asset Library also hosts many community editor tool plugins, corroborating a real ecosystem. missing for 10: no independent hands-on report specifically validating plugin/EditorScript workflows (community evidence is about the engine generally, not editor scripting extensibility).

   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “It can be made entirely with GDScript and standard scenes, without even reloading the editor.”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot Asset Library ... Category Any 2D Tools 3D Tools Shaders Materials Tools Scripts Misc Templates Projects Demos”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser~partialprobed5/10

   Phaser's separate Editor product supports visual scene/asset manipulation (drag-and-drop, filters, inspector) and an MCP server exposes 40+ tools letting AI agents call editor-like functions to manipulate scenes/assets programmatically, which partially satisfies 'automate the editor.' However there is no evidence of a scripting/plugin API for the Editor itself (e.g., custom editor panels, extension SDK, editor-scripting language) — the MCP tools are agent-facing, not a documented developer plugin architecture. missing for 10: documented editor plugin/extension SDK, editor scripting API for custom tools, evidence of third-party editor plugins, independent hands-on confirmation of MCP tool automation reliability.

   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “Add and configure filters visually — Glow, Shadow, Blur, Pixelate, Bokeh, ColorMatrix, Displacement and more — directly in the Scene Editor'…”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [probe] “official MCP server documented at https://phaser.io/agent/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

Ci

1. game developerBuild and export the project from the command line, headless, in CI — no human clicking an editor

   weight 3 · round to Godot Engine
   Godot Engine✓fullprobed9/10

   Godot documents a full command-line workflow for editing, building, and exporting projects without opening the GUI editor, and the runtime probe confirms `godot --headless` is usable for CI builds/exports/scripted automation. This is well-documented first-party capability and corroborated by an independent runtime check. Missing for 10: no independent third-party CI pipeline case study or hands-on report confirming headless export works flawlessly in a real CI environment.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser—none0/10

   The evidence only shows an interactive CLI installer for scaffolding new projects (phaser-docs-2/21) and a separate paid Scene Editor with an MCP 'agent' for human-in-the-loop coding assistance (phaser-docs-12/13/14/27/29) — neither documents a headless build/export command or CI pipeline usage. There is no mention of a 'phaser build' CLI, bundler config, or automated export pipeline suitable for CI. Missing for 10: documented headless build/export CLI command, CI integration example, evidence that game export doesn't require the GUI editor.

   • [claimed-docs] “This CLI tool presents an interactive selection of official project templates and demo games.”
   • [claimed-docs] “This CLI tool presents an interactive selection of official project templates and demo games. Issue the command, answer some questions and t…”
   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”

   proof ↗⚑ flag

Server

1. game developerGame logic runs headless on servers — a dedicated-server or server-runtime build without rendering

   weight 2 · round to Godot Engine
   Godot Engine~partialprobed6/10

   Runtime evidence confirms Godot ships a `--headless` flag used for CI builds, exports, and scripted automation, and official docs describe extensive command-line/editor-less workflows (godot-probe-rt-1, godot-docs-3/12). However, the evidence pack lacks first-party documentation specifically covering dedicated-server export templates or headless runtime performance/behavior details beyond the CLI tutorial. Missing for 10: dedicated first-party docs on server export templates, detailed headless runtime behavior, and independent hands-on confirmation of headless server deployment at scale.

   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”

   proof ↗⚑ flag

   Phaser—none0/10

   No evidence anywhere in the pack of a headless/server-runtime build of Phaser that runs game logic without a canvas/WebGL renderer; all documentation focuses on browser/CDN/npm installs, Scenes, physics, and rendering-oriented editor tooling. Headless server support is a fair question for a game framework (many engines offer it), but nothing here confirms Phaser ships one.

   ⚑ flag

Testing

1. game developerTests run headlessly — unit and integration tests of game code execute in CI against the real engine

   weight 2 · round to Godot Engine
   Godot Engine~partialprobed4/10

   Godot explicitly supports headless CLI operation (`godot --headless`) for automation and scripted editor tasks, and documents command-line workflows and EditorScript execution, which are prerequisites for CI test runs against the real engine. However, there is no evidence of an official unit/integration testing framework (e.g., GUT) or documented CI test-runner examples/integration in the evidence pack. Missing for 10: official testing framework docs, CI pipeline examples, evidence of test-result reporting from headless runs.

   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”

   proof ↗⚑ flag

   Phaser—none0/10

   No evidence in the pack mentions headless testing, CI integration, test runners, or running Phaser against a headless browser/Node environment for automated test execution — all evidence covers installation, scenes, physics, editor, and MCP tooling.

   ⚑ flag

Governance

1. studio leadThe project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan against

   weight 1 · round drawn
   Godot Engine—none0/10

   The evidence pack contains license info (MIT) and community remarks about core-team PR management, but no evidence of a governing foundation, published financial reports, or a public roadmap that a studio lead could plan against. missing for 10: foundation/legal-entity documentation, published financial statements or funding sources, public roadmap or release-planning documentation.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [community] “Akien does a great job managing the PRs. They have a decent system to enable them to review quickly and the core team does a ton of code rev…”
   • [community] “There were several significant land-mines that blew up in my face and it has made me lose some confidence in the core Godot team... I think …”

   proof ↗⚑ flag

   Phaser—none0/10

   No evidence pack items address governance structure, foundation status, published finances, or a public roadmap for Phaser; the evidence covers technical docs, editor/MCP features, pricing/licensing transfer, and community sentiment only. Missing for 10: any mention of a governing foundation, financial transparency/reports, or a published roadmap that a studio lead could plan against.

   ⚑ flag

License

1. studio leadThe license is permissive with no royalties or per-install fees — I keep what my game earns

   weight 3 · round to Godot Engine
   Godot Engine✓fullcommunity9/10

   Godot is MIT-licensed, explicitly described as 'completely free and open source... no royalties, nothing' and 'free to use for any purpose,' with community corroboration noting no forced splash screen requirement unlike Unity. Missing for 10: no explicit discussion of edge cases like trademark/logo usage restrictions or third-party asset licensing nuances.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [community] “One thing many of the big players do that Godot doesn't is require telling the user they used that engine. If you use Unity, you need to sho…”

   proof ↗⚑ flag

   Phaser✓fullprobed7/10

   Runtime probe confirms the core Phaser engine is published under the MIT license (npm registry metadata), which is inherently permissive and imposes no royalties or per-install fees, letting studios keep 100% of game revenue. The evidence pack does not include an explicit vendor statement like 'no royalties' or 'keep what you earn,' so this is inferred from the MIT designation rather than a direct claim; separately, the paid Editor/pricing page (phaser-docs-30) mentions 'full commercial rights' and license transfer for a different, optional commercial tool, not the core engine's licensing terms. Missing for 10: an explicit first-party statement on royalty-free/no-fee terms and independent legal/community confirmation of the license text.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”
   • [claimed-docs] “Full commercial rights * Transfer your licence to any user”

   proof ↗⚑ flag

Source

1. game developerRead and modify the full engine source when I hit a wall

   weight 2 · round to Godot Engine
   Godot Engine✓fullcommunity9/10

   Godot is MIT-licensed open source, with full source available on GitHub, permissive rights to use/modify/redistribute per the license page, and an active core team accepting PRs/code reviews from contributors — directly enabling developers to read and modify engine internals when needed. missing for 10: no explicit evidence pack citation of the exact source-code repo browsing/build docs beyond compilation instructions link.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [github] “See the official docs for compilation instructions for every supported platform.”
   • [community] “Akien does a great job managing the PRs. They have a decent system to enable them to review quickly and the core team does a ton of code rev…”

   proof ↗⚑ flag

   Phaser✓fullprobed7/10

   Phaser's source is hosted on GitHub (phaser-gh-1, phaser-gh-2) and the runtime probe confirms it is MIT-licensed (phaser-probe-rt-1), meaning developers can freely read, fork, and modify the entire engine source when they hit a limitation. Community comments (e.g. phaser-comm-11, phaser-comm-12) even show developers digging into internals/rendering behavior, consistent with open-source access. Missing for 10: explicit documentation/tutorial on how to build from source or contribute patches, and no first-party statement framing this as a workaround path for hitting engine walls.

   • [github] “You can use JavaScript or TypeScript for development.”
   • [github] “Games can be built for the web, or as YouTube Playables, Discord Activities, Reddit games, Twitch Overlays or compiled to iOS, Android, Stea…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”
   • [community] “The framework is good, however I got faster (fps wise) results using my own rendering functions on Canvas than I was getting using their ren…”
   • [community] “I just started playing with it and circular dependencies make me cringe... It's really tough to compose things with it.”

   proof ↗⚑ flag

Trust

1. studio leadThe pricing and license terms have a track record of stability — no retroactive changes that reprice games already shipped

   weight 2 · round to Godot Engine
   Godot Engine✓fullcommunity8/10

   Godot ships under the permissive MIT license with no royalties and no required attribution splash, and since it's a community-governed open-source project (not a single commercial vendor), there's no entity that could retroactively reprice shipped games — MIT terms apply perpetually to released versions. Community commentary explicitly contrasts this with Unity's runtime-fee model requiring payment/splash screens. missing for 10: no explicit independent commentary tracing Godot's licensing history over multiple years to confirm zero retroactive changes, and no first-party statement addressing this stability guarantee directly.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [community] “One thing many of the big players do that Godot doesn't is require telling the user they used that engine. If you use Unity, you need to sho…”

   proof ↗⚑ flag

   Phaser—none0/10

   Evidence shows current pricing/licence terms (full commercial rights, licence transfer) and confirms the core engine is MIT-licensed, but there is no evidence of a documented track record over time — no mention of past pricing changes, grandfathering policies, or community confirmation that shipped games were never repriced retroactively. Missing for 10: historical pricing-change log, explicit no-retroactive-repricing policy statement, and independent/community corroboration of licence stability over multiple releases.

   • [claimed-docs] “You can transfer any active licence or subscription to another registered Phaser user from your account page.”
   • [claimed-docs] “Full commercial rights * Transfer your licence to any user”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Godot Engine
   Godot Engine~partialprobed6/10

   Godot documents extensive CLI/headless operation, EditorScript for scripting editor actions, and GDScript-based plugins that extend the editor 'without even reloading' it — strong evidence of doing much editor work via API/script rather than UI. However, there is no explicit documentation or claim of full UI/API parity, and no independent confirmation that every UI-only feature has a scripting equivalent. Missing for 10: an explicit full API-UI parity guarantee, independent verification that all editor features are scriptable, and evidence of official OpenAPI/MCP-style programmatic surface (probes show none exists).

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser~partialprobed5/10

   Phaser is a code-first JS/TS game framework whose entire API is already scriptable (Scenes, physics, input, animations, loader), so most 'UI' interactions like the Scene Editor are optional visual layers over the same API. The official MCP server (phaser.io/agent/mcp) lets an AI agent describe intent in plain language and have it call editor-equivalent tools, supporting API-level parity with editor actions like adding filters, particle emitters, and reorganizing scenes. However, evidence doesn't confirm 100% coverage of every visual editor feature (e.g., visual filter/particle configuration, pixel art/tilemap/SFX generation tools) via the plain code API, and the MCP server itself is a separate hosted tool, not something distributed as an installable npm package with public OpenAPI/spec. missing for 10: explicit confirmation that every Scene Editor visual feature (filters, particle emitters, layers, pixel/tilemap/SFX tools) has a documented equivalent API call, independent hands-on evidence the MCP/API can fully replicate editor UI actions, and a public API spec (OpenAPI 404s) proving completeness.

   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “Build games from inside the editor you already use with the Phaser Game Agent MCP server.”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [claimed-docs] “Give the player a double-jump and a coin counter.The jump feels floaty, make gravity stronger.”
   • [claimed-docs] “Add and configure filters visually — Glow, Shadow, Blur, Pixelate, Bokeh, ColorMatrix, Displacement and more — directly in the Scene Editor'…”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [claimed-docs] “Pixel art, tilemap & atlas editors * SFX & music generation”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.phaser.io/openapi.json, https://docs.phaser.io/swagger.json, https://docs.phaser.io/api…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Godot Engine
   Godot Engine~partialclaimed5/10

   Godot's MIT license and 'free for any purpose' policy (godot-gh-2, godot-docs-16) mean there's no vendor lock-in, and the asset pipeline docs show raw source assets live in the project folder while only imported caches sit in a hidden .godot folder (godot-docs-9, godot-docs-17), implying user data stays in accessible files. However, there's no explicit documentation of a dedicated 'export all your data' or project-portability feature, nor confirmation that all internal formats (e.g. binary .tscn/.res variants) are fully open/documented. Missing for 10: explicit docs on project file format openness/portability guarantees, a documented data-export or migration tool, and independent corroboration that users can fully extract and reuse their data outside Godot.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [claimed-docs] “Godot will automatically import these files internally and keep the imported resources hidden in a res://.godot/imported/ folder.”
   • [claimed-docs] “To import assets in Godot, place your assets (image files, scenes, audio files, fonts, etc) directly in the project folder.”

   proof ↗⚑ flag

   Phaser—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Godot Engine
   Godot Engine✓fullcommunity9/10

   Godot is MIT-licensed and open source, with the full source hosted publicly on GitHub and license terms explicitly documented ('completely free and open source under the very permissive MIT license', 'You are free to use Godot Engine, for any purpose'); community evidence corroborates active open contribution/review processes. missing for 10: no independent audit or license-scan citation beyond vendor/GitHub statements.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [community] “Akien does a great job managing the PRs. They have a decent system to enable them to review quickly and the core team does a ton of code rev…”

   proof ↗⚑ flag

   Phaser✓fullprobed8/10

   Phaser's source is hosted publicly on GitHub (github.com/phaserjs/phaser, cited in phaser-gh-1/2) and the npm package is confirmed MIT-licensed via runtime probe, satisfying the 'read source under open license' story directly. Missing for 10: an explicit first-party LICENSE file citation and independent community commentary specifically about license terms/openness.

   • [github] “You can use JavaScript or TypeScript for development.”
   • [github] “Games can be built for the web, or as YouTube Playables, Discord Activities, Reddit games, Twitch Overlays or compiled to iOS, Android, Stea…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Godot Engine
   Godot Engine✓fullprobed9/10

   Godot is MIT-licensed, fully open source, and can be self-hosted/self-compiled on any infrastructure the user controls, with headless CLI operation documented for CI/scripted use and confirmed by runtime probes (keyless Homebrew install, --headless mode). missing for 10: no first-party managed self-hosted server/cloud offering docs beyond generic compile-and-run instructions.

   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [github] “See the official docs for compilation instructions for every supported platform.”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”

   proof ↗⚑ flag

   Phaser✓fullprobed8/10

   Phaser is an MIT-licensed, open-source JavaScript library installable via npm or CDN and usable entirely within a self-managed environment (GitHub source, npm package, jsDelivr CDN) — there is no vendor-hosted runtime dependency for the core engine, so self-hosting is inherent to the product. missing for 10: explicit deployment/self-hosting guide (e.g., Docker, server config) and independent confirmation of running fully offline in production.

   • [claimed-docs] “npm install phaser”
   • [claimed-docs] “Phaser is on jsDelivr which is a "super-fast CDN for developers".”
   • [github] “You can use JavaScript or TypeScript for development.”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”

   proof ↗⚑ flag

Targets

1. studio leadOne project exports to desktop, mobile, and (directly or via partners) consoles

   weight 3 · round to Godot Engine
   Godot Engine✓fullclaimed7/10

   Godot's official GitHub description explicitly states one-click export to desktop (Linux/macOS/Windows), mobile (Android/iOS), web, and consoles from a single project, matching the studio-lead's cross-platform export need, and the license docs/MIT confirm no barriers to shipping across platforms. No community evidence contradicts console or desktop/mobile export capability. Missing for 10: independent/hands-on confirmation of console export specifically (which in practice goes through third-party console partners), and more detail on the partner/porting process for consoles beyond the single GitHub line.

   • [github] “Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platfor…”
   • [claimed-docs] “You are free to use Godot Engine, for any purpose”
   • [github] “Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing.”

   proof ↗⚑ flag

   Phaser~partialcommunity5/10

   Phaser docs and GitHub state games can be "compiled to iOS, Android, Steam and native apps using 3rd party tools," covering mobile and desktop export paths, and a community report confirms a real Android .apk export at 60fps. However, there is no evidence—vendor or community—of console export capability (directly or via a documented console partner program), which is a core part of this story. Missing for 10: documented console export path or partner program, first-party tooling/guide for desktop/mobile builds beyond "3rd party tools", independent confirmation of Steam/iOS builds.

   • [claimed-docs] “compiled to iOS, Android, Steam and native apps using 3rd party tools”
   • [claimed-docs] “Games can be built for the web, or as YouTube Playables, Discord Activies, Twitch Overlays or compiled to iOS, Android, Steam and native app…”
   • [github] “Games can be built for the web, or as YouTube Playables, Discord Activities, Reddit games, Twitch Overlays or compiled to iOS, Android, Stea…”
   • [community] “This is the best JavaScript game framework. Been using it for a few years and it never let me down... created a small game and exported it t…”

   proof ↗⚑ flag

Web

1. web developerMy game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU story

   weight 2 · round to Godot Engine
   Godot Engine~partialcommunity5/10

   Evidence confirms Godot supports one-click export to Web platforms (godot-gh-1) and community reports web export working well for GDScript-based projects in the 3.x LTS line (godot-comm-11), but a community report specifically flags that C#/.NET export to web does not work (godot-comm-5), and there is no evidence at all in the pack addressing WebGPU support, payload size optimization, or a build pipeline story for it. Missing for 10: WebGPU backend documentation/evidence, payload-size guidance, and clarity on C# web-export limitations vs GDScript.

   • [github] “Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platfor…”
   • [community] “It works relatively well, and actually better than in Unity (which uses an older C# version), but unfortunately it does not work everywhere.…”
   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”

   proof ↗⚑ flag

   Phaser~partialcommunity4/10

   Evidence confirms browser-based rendering with WebGL (community mention of 'rendering on both Canvas and WebGL') and easy npm/CDN distribution suggesting reasonable payload, but there is no mention anywhere in the pack of WebGPU support, a WebGPU renderer, or a roadmap toward it. missing for 10: explicit WebGPU renderer/roadmap documentation, payload-size benchmarks, and independent corroboration of WebGL performance beyond one anecdotal comment.

   • [community] “The framework is good, however I got faster (fps wise) results using my own rendering functions on Canvas than I was getting using their ren…”
   • [claimed-docs] “npm install phaser”
   • [claimed-docs] “Phaser is on jsDelivr which is a "super-fast CDN for developers".”

   proof ↗⚑ flag

2. web developerThe engine installs from a package registry into my existing toolchain — a library I import, bundle, and tree-shake like any dependency

   weight 2 · round to Phaser
   Godot Engine—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Phaser✓fullprobed9/10

   Phaser is published as a standard npm package (`npm install phaser`), confirmed both in docs and via live registry probe (v4.2.1, MIT license, 263k weekly downloads), and includes TypeScript definitions in the package, making it importable/bundleable like any standard JS dependency. Community evidence corroborates typical toolchain use (bundling into games/apps) though tree-shaking specifically isn't explicitly discussed. Missing for 10: explicit documentation or confirmation of tree-shaking/ESM module support behavior.

   • [claimed-docs] “npm install phaser”
   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”
   • [claimed-docs] “Install via [npm](https://www.npmjs.com/package/phaser): npm install phaser”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view phaser version` → 4.2.1 (MIT, 263,018 weekly downloads), and phaser.io/llms.txt is live as a …”
   • [github] “You can use JavaScript or TypeScript for development.”

   proof ↗⚑ flag

1. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Godot Engine—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or any opt-out mechanism for Godot; the pack covers scripting languages, plugins, licensing, and community sentiment but never discusses data collection or privacy settings.

   ⚑ flag

   Phaser—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Phaser's library, CLI, editor, or MCP server offerings, despite these being product surfaces where such a policy could exist.

   ⚑ flag

Iteration

1. game developerThe edit-run loop is fast — hot reload or near-instant preview after a script change

   weight 2 · round to Godot Engine
   Godot Engine~partialclaimed4/10

   Evidence shows editor plugins can be built in GDScript without reloading the editor (godot-docs-4/13) and Godot's scene/node system supports live editing, implying reasonably fast iteration, but there is no direct documentation or community confirmation of hot-reloading running gameplay scripts or near-instant preview after a script change during play mode. missing for 10: explicit docs on script hot-reload during play, independent hands-on confirmation of edit-run loop speed for gameplay code, comparison benchmarks.

   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “It can be made entirely with GDScript and standard scenes, without even reloading the editor.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”

   proof ↗⚑ flag

   Phaser—none0/10

   No evidence in the pack describes hot reload, live-reload dev server, or near-instant preview after script changes; only editor visual tweaks (glow/filters, drag-drop) are documented, which is not the same as a fast JS edit-run loop. The templates/CLI installation docs mention project setup but not dev-server hot reload behavior.

   ⚑ flag

Language

1. game developerThe primary scripting language is productive and fully exposes the engine API, with a debugger behind it

   weight 3 · round drawn
   Godot Engine~partialcommunity6/10

   GDScript is documented as Godot's native, high-level, object-oriented, gradually-typed language that fully exposes the engine API (nodes/scenes, editor plugins, EditorScript), and community reports back this up as reasonably fast to learn and productive for people with programming experience. However, the evidence pack contains no explicit documentation of a GDScript-specific debugger (only C#'s Visual Studio debugging is called out), and some community feedback calls GDScript's ergonomics and documentation poor (comm-14, comm-15), creating real caveats rather than a clean full delivery. Missing for 10: explicit docs on the built-in GDScript debugger/breakpoints workflow, and stronger independent confirmation that GDScript is unambiguously productive for professional use.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “Keep your code modular with an object-oriented API using Godot's own GDScript, C#, C++, or bring your own using GDExtension.”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [community] “I'm using it every day at work... Godot was just what I needed since I wanted a visual editor but still be able to code. The scripting langu…”
   • [community] “gdscript is pretty awful. It's only python-like for someone who's never used python. No list comprehensions, no tuples... It's like Python 1…”
   • [community] “I have tried to use it something like 2 years ago and just gave up in front of the poorly documented custom scripting language they used.”
   • [community] “Godot 4 is using actual .NET instead of Mono, so you get all the tooling support that implies, including seamless debugging with Visual Stud…”

   proof ↗⚑ flag

   Phaser~partialcommunity6/10

   Phaser's primary language is JavaScript/TypeScript with full TypeScript definitions shipped (phaser-docs-4) and GitHub confirming both JS/TS support (phaser-gh-1), and community members report it as easy to learn and productive (phaser-comm-3, phaser-comm-7, phaser-comm-10). However TypeScript support is described as 'best-effort... layered onto Phaser 3 via DefinitelyTyped' rather than native (phaser-comm-8), and docs quality — key to fully exposing the API productively — is criticized as 'the worst I've seen' by one community member (phaser-comm-16) even as others praise it (phaser-comm-10). No dedicated debugger tooling (breakpoints, inspector) is documented anywhere in the evidence pack beyond standard browser JS debugging implied by using JS/TS. Missing for 10: explicit debugger/dev-tools integration documentation, native (non-DefinitelyTyped) TypeScript support, and independent confirmation that the API surface is fully exposed without workarounds.

   • [github] “You can use JavaScript or TypeScript for development.”
   • [claimed-docs] “Full TypeScript definitions can be found inside the types folder”
   • [community] “A year or so ago I did a lot with Phaser... man is Phaser easy to learn and easy to get more advanced in... I am a big fan of their work.”
   • [community] “I've made a couple toy projects with Phaser, after comparing other Javascript based 2d engines. Phaser is the most fully featured amongst th…”
   • [community] “Phaser 4 was announced ~four years ago and was an attempt to get the project written natively in TypeScript. It looks pretty dead in the wat…”
   • [community] “The documentation of Phaser is the worst i've seen to a popular framework. The website is very bad in the design, styling as well as content…”
   • [community] “I've spent the past 6 months building a game using Phaser and TypeScript. On the whole, it's been a great experience... one of the worst par…”

   proof ↗⚑ flag

Visual

1. technical artistBuild gameplay logic with visual scripting without writing code

   weight 2 · round drawn
   Godot Engine—none0/10

   The evidence pack documents only code-based scripting options (GDScript, C#, GDExtension/C++) and editor plugins/scripts, with no mention of a node-graph or visual scripting system for building gameplay logic without writing code; Godot's own VisualScript feature is not referenced anywhere in the pack.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [claimed-docs] “Keep your code modular with an object-oriented API using Godot's own GDScript, C#, C++, or bring your own using GDExtension.”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”

   proof ↗⚑ flag

   Phaser—none0/10

   Evidence shows Phaser's editor (phaser.io/editor) provides visual scene/asset editing—drag-and-drop placement, animation tweaking, physics-body adjustment, filter effects—and an MCP agent that translates natural-language requests into code changes, but nothing describes a node-based or visual gameplay-logic scripting system that lets a technical artist build game logic without writing JavaScript/TypeScript code. Phaser remains fundamentally a code-first framework (phaser-gh-1, phaser-docs-4), so the 'no-code logic' capability is unevidenced.

   • [claimed-docs] “Drag and drop objects into place, tweak their animations, adjust their physics bodies, enable special effects and more as you go.”
   • [claimed-docs] “Add and configure filters visually — Glow, Shadow, Blur, Pixelate, Bokeh, ColorMatrix, Displacement and more — directly in the Scene Editor'…”
   • [claimed-docs] “Create a particle emitter, reorganise a scene into layers, rename a bunch of objects — it handles it without switching tools.”
   • [claimed-docs] “For power users, the MCP Server goes deeper. It implements over 40 specialised tools and integrates directly with Claude Desktop, Cursor, Gi…”
   • [claimed-docs] “You describe what you want in plain language and your agent calls the tools for you.”
   • [github] “You can use JavaScript or TypeScript for development.”

   proof ↗⚑ flag