Godot Engine vs PlayCanvas

Agent access

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas✓fullprobed9/10

   A working llms.txt confirmed via HTTP 200 probe plus an unusually large llms-full.txt (2MB) of complete docs is directly served at developer.playcanvas.com, satisfying the exact story of pointing an agent at llms.txt/agent-oriented docs. This is corroborated by both docs claims and independent runtime probes, not just vendor assertion. Missing for 10: no independent third-party (non-probe) report of an agent actually consuming the file successfully in a real workflow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.playcanvas.com/llms.txt # PlayCanvas Developer Documentation > PlayCanvas is an open-source W…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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

   PlayCanvas—none0/10

   Evidence shows the engine is npm-installable and there's an Editor MCP server, but the MCP server explicitly requires 'an open PlayCanvas Editor session' (interactive), and no evidence describes headless rendering, CI pipelines, or server-side/automated execution of the engine or editor without a live browser/editor session.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [github] “npm install playcanvas”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Godot Engine—none0/10

   There is no evidence Godot itself can consume MCP servers as a client to use their tools; the probe shows no official MCP integration exists (0 results searching GitHub org, no llms.txt), only unofficial third-party community projects like godot-mcp and godot-ai, which expose Godot's editor as an MCP *server* for external agents to control, not Godot acting as an MCP client consuming external tools.

   • [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

   PlayCanvas—none0/10

   Evidence only shows PlayCanvas exposing its own Editor as an MCP *server* that AI assistants connect to (playcanvas-docs-6, playcanvas-probe-rt-1) — the opposite direction of this story, which asks whether PlayCanvas itself can plug in external MCP servers to consume their tools. No evidence shows PlayCanvas acting as an MCP client or integrating third-party MCP tool servers into its engine, editor, or workflow.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”

   proof ↗⚑ flag

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

   weight 3 · round to PlayCanvas
   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

   PlayCanvas✓fullprobed9/10

   PlayCanvas documents and ships an official, first-party MCP server (`@playcanvas/editor-mcp-server`, npm-published, official org repo) that connects AI assistants to a live Editor session to modify project data and verify results via the viewport, confirmed both in docs and runtime probes. Missing for 10: independent third-party hands-on validation of the MCP server beyond vendor docs/probe.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   proof ↗⚑ flag

5. 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

   PlayCanvas~partialclaimed4/10

   PlayCanvas ships an official `create-playcanvas` CLI for scaffolding Vite/TypeScript projects, which an AI agent could invoke, but the docs describe it purely as a project scaffolder with no explicit AI-native/agentic features (non-interactive flags, scripting API, automation hooks) and no independent confirmation of agent usage. Missing for 10: documentation of CLI flags/JSON output for automation, evidence of AI-agent usage, and any tie-in with the MCP server workflow.

   • [claimed-docs] “Use `create-playcanvas` to scaffold a Vite and TypeScript project for the Engine, React, or Web Components from one of 12 runnable starters.”

   proof ↗⚑ flag

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

   weight 3 · round to PlayCanvas
   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

   PlayCanvas✓fullprobed7/10

   PlayCanvas exposes a documented scriptable Editor API for automating/customizing the Editor environment (api.playcanvas.com/editor/) plus an official, npm-published Editor MCP Server explicitly built for AI assistants to modify project data and verify results, alongside a standalone Engine API and llms.txt docs for AI consumption. This gives AI-native users multiple documented, programmatic ways to drive the product. Missing for 10: a formal OpenAPI/REST spec (probe found only 404s for openapi/swagger endpoints) and independent third-party confirmation of API-driven automation success.

   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.playcanvas.com/openapi.json, https://developer.playcanvas.com/swagger.json, https:…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to PlayCanvas
   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

   PlayCanvas✓fullprobed8/10

   PlayCanvas publishes multiple official SDKs — the core Engine (npm `playcanvas`), React and Web Components bindings, a `create-playcanvas` scaffolding CLI, a scriptable Editor API, and an official npm-published Editor MCP server for AI automation — all documented and runtime-verified. Community discussion confirms it integrates with standard JS/React workflows, though it also notes some dev-experience friction unrelated to SDK availability. Missing for 10: independent hands-on developer reports specifically validating SDK usage/quality, and a public OpenAPI/versioned reference (probe found only 404s for openapi.json).

   • [claimed-docs] “Use `create-playcanvas` to scaffold a Vite and TypeScript project for the Engine, React, or Web Components from one of 12 runnable starters.”
   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [claimed-docs] “Already use React, want declarative 3D scenes, or need to integrate 3D into React apps”
   • [github] “npm install playcanvas”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”
   • [community] “You can use it in conjunction with pretty much any other JS framework available.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas~partialprobed4/10

   PlayCanvas ships an official Editor MCP server that lets connected AI assistants read and modify project data and verify results in the viewport, which could be used to generate suggestions/insights from a user's scene data, but there is no evidence of a native, built-in AI insights/recommendations feature (e.g., analytics, optimization suggestions) inside the product itself. Missing for 10: dedicated AI-insights UI or documented use-case of the MCP server producing analytical suggestions, independent corroboration of this workflow in practice.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   proof ↗⚑ flag

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas~partialprobed4/10

   PlayCanvas ships an official Editor MCP server that lets AI assistants programmatically modify project data, but it explicitly requires 'an open PlayCanvas Editor session' rather than running as an independent, scheduled, or background process — this is closer to AI-assisted live editing than autonomous background automation. Missing for 10: evidence of scheduled/triggered jobs, headless/background execution without a live editor session, or any autonomous agent loop running unattended.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   proof ↗⚑ flag

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

   weight 3 · round to PlayCanvas
   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

   PlayCanvas~partialprobed5/10

   PlayCanvas does not ship a built-in AI assistant embedded in its UI; instead it exposes an official Editor MCP server that lets external AI assistants (e.g. Claude) connect to an open Editor session and modify/inspect project data via the viewport, effectively allowing task delegation to AI, but the assistant itself lives outside the product rather than inside it. Missing for 10: a first-party, in-product AI assistant UI/chat surface, and any hands-on/community verification that delegation via MCP works well in practice.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   proof ↗⚑ flag

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas~partialprobed6/10

   PlayCanvas ships an official, npm-published Editor MCP Server that lets AI assistants modify project data and verify results via the viewport, which is a genuine natural-language/agentic control surface for the Editor. However, this only covers Editor operations, not the runtime Engine or broader workflows, and there's no independent/hands-on evidence of it being used successfully in practice. missing for 10: community/hands-on validation of the MCP server in real workflows, evidence of natural-language control over the Engine/runtime (not just Editor), and broader agentic tool coverage beyond the single MCP server.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   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

   PlayCanvas—none0/10

   Evidence shows PlayCanvas has API docs (api.playcanvas.com/editor), llms.txt full docs, and starter templates, but no evidence of an interactive API reference page with embedded runnable code examples akin to a live sandbox integrated into the reference itself.

   ⚑ flag

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

   weight 2 · round drawn
   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

   PlayCanvas—none0/10

   Explicit probe evidence shows no OpenAPI/Swagger spec exists at any expected path (all candidates 404); while llms.txt and an Editor API doc site exist, there is no machine-readable API spec download offered.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.playcanvas.com/openapi.json, https://developer.playcanvas.com/swagger.json, https:…”

   proof ↗⚑ flag

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

   weight 1 · round to PlayCanvas
   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

   PlayCanvas~partialclaimed3/10

   PlayCanvas documents Checkpoints for snapshotting/rolling back a project and an MCP server that acts on 'an open PlayCanvas Editor session,' which offers some safety net against irreversible changes, but there is no explicit sandbox/staging environment distinct from production data that an AI agent could test against. missing for 10: dedicated sandbox/staging project mode, explicit production-vs-test data separation, and evidence that MCP or automation actions can't touch the live production project.

   • [claimed-docs] “Checkpoints — Snapshot your project at any point and roll back if needed”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [claimed-docs] “With live editing, you can tweak materials, adjust positions, and even modify scripts while your application runs.”

   proof ↗⚑ 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

   PlayCanvas—none0/10

   No evidence pack item mentions API versioning semantics or a documented deprecation policy; the OpenAPI probe returned 404s and docs only describe scripting formats, editor features, and an MCP server, not stability guarantees for the API surface.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.playcanvas.com/openapi.json, https://developer.playcanvas.com/swagger.json, https:…”

   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 PlayCanvas
   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

   PlayCanvas✓fullprobed8/10

   PlayCanvas ships an official, npm-published Editor MCP server that lets AI agents connect to an open Editor session, modify project data, and verify results, plus a separate documented scriptable Editor API (api.playcanvas.com/editor) for programmatic scene/node/property manipulation and automation. This directly satisfies the story of an agent driving the editor programmatically through a documented interface. Missing for 10: no independent/hands-on community report of an agent actually using the MCP server end-to-end, and no explicit documentation of triggering builds via this interface.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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 PlayCanvas
   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

   PlayCanvas~partialprobed6/10

   PlayCanvas offers strong LLM-friendly infrastructure — a dedicated llms.txt/llms-full.txt (over 2MB of docs), a stable, long-standing npm-published engine (2.22.2, 48k weekly downloads) with abundant public code examples and community history, plus scripting API docs — all of which support an LLM having 'seen' the API. However, community threads note real dev-experience quirks and unusual design choices that could trip up naive LLM-generated code, and there's no direct hands-on evidence of first-try LLM code generation success rates. Missing for 10: independent benchmark or testimonial confirming LLM-generated PlayCanvas code works correctly on first try, and no discussion of API stability/breaking-change history that would affect training-data staleness.

   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.playcanvas.com/llms.txt # PlayCanvas Developer Documentation > PlayCanvas is an open-source W…”
   • [github] “npm install playcanvas”
   • [community] “That issue was opened in 2022. Honestly if you really get into the nitty gritty of PC it becomes quickly apparent there's some very strange …”
   • [community] “I think Playcanvas would do well to focus on the basics, like being able to export/import variables in the standard js way, being able to de…”

   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 PlayCanvas
   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

   PlayCanvas~partialprobed6/10

   PlayCanvas ships an official, npm-published Editor MCP Server that lets external AI assistants connect to a live Editor session to modify project data, script entities, and verify changes via the viewport—directly enabling AI-assisted script generation and scene/asset scaffolding (playcanvas-docs-6, playcanvas-probe-rt-1). However, this is an MCP bridge for third-party assistants rather than a built-in chat/assistant panel inside the engine UI, and there's no dedicated in-engine API Q&A assistant beyond the llms.txt docs feed. Missing for 10: a native in-editor chat/assistant UI, and explicit evidence of it answering free-form API questions rather than just executing structured edits.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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

   PlayCanvas—none0/10

   The evidence pack contains no mention of glTF, FBX, or USD import support, nor any asset-pipeline/import documentation; it covers editor, scripting, MCP server, and community sentiment unrelated to file format import.

   ⚑ 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

   PlayCanvas~partialcommunity3/10

   The Editor API is explicitly billed for scripting custom tools and integrating external systems (playcanvas-docs-9), and the community references playcanvas-sync for mapping project assets to a local filesystem (playcanvas-comm-10) and the MCP server for programmatic project data changes (playcanvas-docs-6), all of which imply some automation capability. However, there is no documented import-hook system, asset presets, or a dedicated pipeline-scripting API specifically for processing incoming assets automatically. Missing for 10: explicit asset import hooks, configurable import presets, documented pipeline scripts triggered on asset ingestion, and independent confirmation these tools eliminate manual per-asset clicking.

   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”

   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

   PlayCanvas—none0/10

   The evidence pack shows PlayCanvas has an editor, engine, scripting system, MCP server, and npm-published engine, but nowhere mentions an asset store, marketplace, or plugin/package ecosystem for ready-made models or tools. No community or docs citation references anything resembling a store of third-party assets or plugins.

   ⚑ flag

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

   weight 2 · round drawn
   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

   PlayCanvas~partialprobed4/10

   PlayCanvas exposes a scriptable Editor API (api.playcanvas.com/editor) explicitly for building custom editing tools and integrating external data, and an official MCP server that lets AI assistants modify project data programmatically — both imply automation potential across many assets, but neither doc explicitly describes bulk/batch operations (e.g., multi-entity edits, batch asset import) or gives a hands-on example of many-item automation. Missing for 10: explicit bulk-edit/batch API examples, documented multi-item scripting workflows, and independent confirmation of large-scale automation via the MCP server or Editor API.

   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”

   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

   PlayCanvas—none0/10

   The evidence pack covers scripting syntax, editor collaboration, physics components, and the MCP server for AI-assisted project editing, but contains no documentation of an explicit event/rule system where users can define triggers that automatically fire actions (e.g., event listeners, condition-action bindings) for automation purposes. Missing for 10: documentation of an event-trigger/rule engine, examples of defining conditional automation, and evidence tying this to AI-native workflows.

   ⚑ flag

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

   weight 1 · round to PlayCanvas
   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

   PlayCanvas~partialcommunity5/10

   PlayCanvas Editor has a Checkpoints feature to snapshot a project and roll back, which covers basic versioning/rollback of editor state (including changes made via the MCP-driven AI automation), but there's no documented diff/review workflow for automations and community feedback explicitly flags the lack of standard source-control integration as a pain point. missing for 10: dedicated review/diff tooling for automation changes, git-style commit history, and any evidence that checkpoints integrate specifically with AI-driven MCP edits.

   • [claimed-docs] “Checkpoints — Snapshot your project at any point and roll back if needed”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [community] “I think Playcanvas would do well to focus on the basics, like being able to export/import variables in the standard js way, being able to de…”

   proof ↗⚑ flag

2d

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

   weight 2 · round to Godot Engine
   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

   PlayCanvas—none0/10

   Evidence pack covers 3D features (rigidbody/collision physics, Gaussian Splatting, Engine, Editor) but contains no mention of sprites, tilemaps, or a 2D physics system — PlayCanvas is documented here purely as a 3D-first engine. This is a fair question for a game engine, but no evidence supports a first-class 2D workflow, so it's 'none' rather than 'na'.

   • [claimed-docs] “The rigidbody component decides how an entity moves, the collision component gives it a physical shape, and the alpha joint component constr…”
   • [github] “Gaussian Splatting - First-class support for loading and rendering 3D Gaussian Splats”

   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

   PlayCanvas—none0/10

   The evidence pack contains no mention of a profiler, ECS architecture, job/worker system, or GPU instancing for scaling heavy scenes — only physics components, Gaussian splatting, and editor/collab features are documented. This is a fair axis for any game engine, but PlayCanvas's pack simply doesn't address it.

   ⚑ flag

Physics

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas~partialcommunity6/10

   Docs confirm built-in rigidbody, collision, and joint components enabling physics simulation out of the box (playcanvas-docs-8), and community sources corroborate PlayCanvas as a capable, well-designed engine used in shipped games. However, raycasts are not explicitly mentioned, and there's no hands-on evidence or tutorial demonstrating physics working smoothly without setup friction (e.g., Ammo.js/physics engine integration steps). Missing for 10: explicit raycast documentation, independent hands-on confirmation of zero-config physics setup, and detail on which physics backend is bundled vs. requires separate install.

   • [claimed-docs] “The rigidbody component decides how an entity moves, the collision component gives it a physical shape, and the alpha joint component constr…”
   • [community] “THREE.js is very low-level framework, while PlayCanvas additionally to low-level engine access has game framework, which will allow you to c…”
   • [community] “I haven't used it, but I remember looking at the minified code a while back when it was first released. It looks very well done, by someone …”

   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

   PlayCanvas—none0/10

   The evidence pack documents scripting, editor collaboration, physics, MCP integration, and Gaussian splatting support, but contains no first-party or community evidence about PBR materials, global illumination/baked lighting, shadow systems, or a post-processing pipeline. Per the rules, absence of evidence for this applicable rendering-feature axis must be scored as 'none' rather than inferred from outside knowledge.

   ⚑ 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 to PlayCanvas
   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

   PlayCanvas!disputedcontradicted4/10

   PlayCanvas markets real-time multi-user editing as solving merge conflicts entirely (docs-4, docs-13) rather than a diffable/VCS-friendly text format, but hands-on community reports concretely contradict the 'plays well with version control' framing: developers note the project lives on PlayCanvas's servers with 'no easy local dev environment' and that basics like 'using your own source control' are missing, with unofficial third-party tools (playcanvas-sync) needed just to sync assets locally, and uploading being a 'deal breaker' for offline/local workflows. Checkpoints (docs-5) offer some rollback safety but are not the same as git-based diff/merge tooling. missing for 10: official git-friendly/text-diffable scene format, first-party local-file sync equivalent to real VCS integration, and evidence the community-reported local-dev gap has been resolved.

   • [claimed-docs] “Multiple developers, artists, and designers can build the same scene simultaneously—no merge conflicts, no stepping on each other's toes.”
   • [claimed-docs] “With live editing, you can tweak materials, adjust positions, and even modify scripts while your application runs.”
   • [claimed-docs] “Checkpoints — Snapshot your project at any point and roll back if needed”
   • [community] “I think Playcanvas would do well to focus on the basics, like being able to export/import variables in the standard js way, being able to de…”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [community] “I'd love to be able to use their scene editor offline, uploading assets is a deal breaker.”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”

   proof ↗⚑ 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

   PlayCanvas~partialcommunity6/10

   Docs confirm a full drag-and-drop visual Editor with real-time collaborative scene building, live editing of materials/positions, and checkpoint/versioning (playcanvas-docs-3, docs-4, docs-5, docs-13), which matches the viewport+scene-composition part of the story. However, no evidence explicitly documents an 'inspector' panel or a 'prefab' system by name, and community reports flag real dev-experience friction (no easy local dev, assets must be uploaded, offline editing not supported) that complicate treating the editor as the primary, frictionless build workflow. missing for 10: explicit inspector/prefab terminology and documentation, independent hands-on confirmation of prefab workflow, resolution of community-reported offline/local-dev friction.

   • [claimed-docs] “Want drag-and-drop scene building, real-time collaboration, or prefer visual tools over code”
   • [claimed-docs] “Multiple developers, artists, and designers can build the same scene simultaneously—no merge conflicts, no stepping on each other's toes.”
   • [claimed-docs] “Checkpoints — Snapshot your project at any point and roll back if needed”
   • [claimed-docs] “With live editing, you can tweak materials, adjust positions, and even modify scripts while your application runs.”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “I'd love to be able to use their scene editor offline, uploading assets is a deal breaker.”

   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

   PlayCanvas✓fullprobed7/10

   PlayCanvas explicitly documents a scriptable Editor API module (api.playcanvas.com/editor) built 'for developers looking to... create custom editing tools, or integrate external data and systems into the PlayCanvas Editor environment,' plus an official MCP server for AI-driven automation of live Editor sessions, and community-built sync tools for local file mapping — together showing programmatic extension of the editor itself. Missing for 10: concrete example plugins/marketplace or hands-on demonstration of a third-party editor tool built with this API, and no independent review confirming ease of use for this specific API (only general dev-experience complaints exist).

   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”

   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

   PlayCanvas~partialcommunity4/10

   The standalone Engine is a plain npm package usable with Vite/TypeScript scaffolding, so Engine-only projects can plausibly be built and bundled headlessly via a standard `vite build` in CI (playcanvas-gh-2, playcanvas-docs-1, playcanvas-docs-7). However, PlayCanvas's primary workflow is the cloud Editor, and community reports confirm no easy local dev environment or native CLI export — code/assets live on PlayCanvas's servers, requiring third-party 'playcanvas-sync' tooling and manual tinkering to approximate a local/CI workflow (playcanvas-comm-8, playcanvas-comm-9, playcanvas-comm-10). No first-party CLI/CI build-and-export tool for Editor projects is documented anywhere in the evidence. Missing for 10: an official CLI/CI export command for Editor-based projects, documentation of headless Editor project builds, and independent confirmation that Editor-based CI pipelines work reliably.

   • [github] “npm install playcanvas”
   • [claimed-docs] “Use `create-playcanvas` to scaffold a Vite and TypeScript project for the Engine, React, or Web Components from one of 12 runnable starters.”
   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “It's certainly not super obvious to setup but there are ways to use PlayCanvas with local setup... with some tinkering you can have hot modu…”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”

   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

   PlayCanvas—none0/10

   The evidence pack shows PlayCanvas as a browser-focused WebGL/WebGPU engine with npm packages, Editor, and MCP server tooling, but nothing about a dedicated headless/server-runtime build without rendering for running game logic on servers. Missing for 10: any docs or GitHub evidence of a headless Node.js server build, server-side simulation mode, or rendering-free runtime.

   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [github] “npm install playcanvas”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   proof ↗⚑ 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

   PlayCanvas—none0/10

   No evidence of a testing framework, headless mode, or CI integration for running unit/integration tests against the PlayCanvas engine; docs cover scripting, editor, MCP server, and standalone engine usage but never mention headless test execution or CI workflows.

   ⚑ 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

   PlayCanvas—none0/10

   No evidence of a governing foundation, published financials, or a public roadmap; PlayCanvas is run as a commercial product (subscription plans mentioned) with no transparency artifacts cited. Community comments discuss engine features and dev-experience, not governance or funding.

   ⚑ 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

   PlayCanvas✓fullprobed7/10

   The core PlayCanvas Engine is confirmed MIT-licensed and open source ('MIT engine runtime' in playcanvas-probe-rt-2; community confirms 'the engine is open source' in playcanvas-comm-11 and playcanvas-comm-16), meaning a studio can ship and monetize games without royalties or per-install fees on the runtime itself. However, evidence also shows the hosted Editor/collaboration tooling is a paid subscription (e.g., $15/month for private projects, playcanvas-comm-4), which is a studio-tooling cost rather than a revenue royalty, so it doesn't contradict the engine's permissive licensing but adds nuance. Missing for 10: explicit vendor documentation stating 'no royalties/no revenue share' policy and independent legal/community confirmation of unrestricted commercial use terms.

   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [community] “It's an open source javascript game engine that is kinda like halfway between something like three.js and e.g. Unity—pretty lightweight, but…”
   • [community] “Every time I've taken a look at this engine it has always felt very limited. And with a $15/month subscription just to be able to create pri…”

   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

   PlayCanvas✓fullprobed8/10

   The PlayCanvas Engine is confirmed open source (MIT) and published on GitHub/npm, allowing developers to read and modify the core engine code directly, corroborated by community comment that 'the engine is open source' and runtime probes confirming the MIT license and public repo. Missing for 10: explicit contribution/build docs or a first-party statement of the license terms, and no independent hands-on account of someone actually patching engine internals.

   • [github] “Gaussian Splatting - First-class support for loading and rendering 3D Gaussian Splats”
   • [github] “npm install playcanvas”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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

   PlayCanvas—none0/10

   No evidence in the pack addresses pricing/licensing history, terms stability, or retroactive repricing of shipped games; only a $15/month subscription mention and a link to the plans page appear, with no discussion of contract stability or track record.

   ⚑ flag

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

   weight 2 · round drawn
   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

   PlayCanvas~partialprobed6/10

   PlayCanvas exposes a scriptable Editor API (api.playcanvas.com/editor) for custom editing tools and integrations, plus an official MCP server that lets AI assistants modify project data and verify results via the viewport — going beyond a typical 'no API' game engine. However there is no discoverable REST/OpenAPI spec (404s across probed endpoints), and no documentation explicitly claims full UI-API parity; some Editor-only features (drag-and-drop scene building, real-time collaboration) are framed as UI-first conveniences without confirmed programmatic equivalents. missing for 10: an explicit parity statement/spec covering all UI actions, a formal REST/OpenAPI contract, and independent confirmation that collaborative/visual editor features are fully scriptable.

   • [claimed-docs] “The PlayCanvas Editor MCP Server connects AI assistants to an open PlayCanvas Editor session. It can modify project data and verify the resu…”
   • [claimed-docs] “This module is essential for developers looking to streamline their workflow, create custom editing tools, or integrate external data and sy…”
   • [probe] “official MCP server documented at https://developer.playcanvas.com/user-manual/editor/mcp-server/”
   • [probe] “PROBE runtime (recorded 2026-09-15): PlayCanvas ships the only OFFICIAL, open, npm-published editor MCP server of the eight engines — `npm v…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.playcanvas.com/openapi.json, https://developer.playcanvas.com/swagger.json, https:…”
   • [claimed-docs] “Want drag-and-drop scene building, real-time collaboration, or prefer visual tools over code”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   PlayCanvas~partialcommunity5/10

   The engine itself is open-source (MIT, npm-published) and PlayCanvas offers 'Download Apps for Self-hosting', plus community tooling (playcanvas-sync) to map project assets to a local filesystem, giving users a path to exit the platform with their code/engine. However, there is no first-party documentation of a comprehensive 'export all project data in open formats' feature, and community reports explicitly flag that code/collaboration data lives on PlayCanvas's servers with no easy local dev environment, undercutting a full data-portability story. Missing for 10: an official bulk data-export tool/format for scenes, assets and editor project state, and independent confirmation that exported data is fully open and complete.

   • [claimed-docs] “Download Apps for Self-hosting”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “It's certainly not super obvious to setup but there are ways to use PlayCanvas with local setup... with some tinkering you can have hot modu…”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [github] “npm install playcanvas”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   PlayCanvas✓fullprobed9/10

   PlayCanvas Engine is confirmed open source (GitHub repo, MIT license, npm-published), and community commentary independently corroborates 'the engine is open source' (playcanvas-comm-11, comm-16). The full engine source is browsable on GitHub and versioned, satisfying an AI-native user's ability to read source under an open license; missing for 10: explicit license file text/OSI confirmation cited directly in evidence.

   • [github] “Gaussian Splatting - First-class support for loading and rendering 3D Gaussian Splats”
   • [github] “npm install playcanvas”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [community] “It's an open source javascript game engine that is kinda like halfway between something like three.js and e.g. Unity—pretty lightweight, but…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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

   PlayCanvas!disputedcontradicted5/10

   The core Engine is open-source (MIT, npm-published) and documented for standalone/self-hosted use (playcanvas-docs-7, playcanvas-gh-2), but the actual PlayCanvas product most users mean—the Editor/collaboration platform—is proprietary SaaS with no self-hosting option; community reports confirm project code must live on PlayCanvas's servers with no easy local dev environment (playcanvas-comm-8, playcanvas-comm-11, playcanvas-comm-12). The 'Download Apps for Self-hosting' doc refers to exporting built apps, not self-hosting the Editor itself. Missing for 10: an official self-hostable Editor/backend, first-party self-host deployment docs for the full platform, and resolution of the community-confirmed server-lock-in for authoring.

   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [github] “npm install playcanvas”
   • [claimed-docs] “Download Apps for Self-hosting”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “I think the engine is open source; but the real appeal is using the real time collab online tool, which is proprietary and had the drawbacks…”
   • [community] “I'd love to be able to use their scene editor offline, uploading assets is a deal breaker.”

   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

   PlayCanvas—none0/10

   Evidence shows PlayCanvas engine and Editor covering web, desktop-via-browser, and self-hosted app export, but there is no mention anywhere in the pack of console export (PlayStation/Xbox/Switch) or partner porting programs. Community commentary consistently frames PlayCanvas as a web-first/WebGL engine with no console story. missing for 10: any documentation of console export or third-party console porting partnership, evidence of desktop/mobile packaging beyond generic 'download apps', console SDK support.

   • [claimed-docs] “Download Apps for Self-hosting”
   • [community] “It is a very nice engine, specially for those focused on Web only as target.”
   • [community] “It's an open source javascript game engine that is kinda like halfway between something like three.js and e.g. Unity—pretty lightweight, but…”

   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 PlayCanvas
   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

   PlayCanvas✓fullprobed8/10

   PlayCanvas is explicitly documented as a WebGL/WebGPU engine (probe-1) with a lightweight open-source runtime (npm playcanvas package, MIT license) and community corroboration that it's well-suited to lean web deployment (comm-1, comm-6, comm-13, comm-16) versus bloated alternatives. Missing for 10: no explicit payload-size benchmarks or bundle-size comparisons, and no independent hands-on confirmation of WebGPU parity/performance versus WebGL in production games.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.playcanvas.com/llms.txt # PlayCanvas Developer Documentation > PlayCanvas is an open-source W…”
   • [github] “npm install playcanvas”
   • [community] “Unreal is a bloated way to develop WebGPU projects for the web. PlayCanvas is a sensible solution if your target is web.”
   • [community] “It is a very nice engine, specially for those focused on Web only as target.”
   • [community] “THREE.js is very low-level framework, while PlayCanvas additionally to low-level engine access has game framework, which will allow you to c…”
   • [community] “It's an open source javascript game engine that is kinda like halfway between something like three.js and e.g. Unity—pretty lightweight, but…”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”

   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 PlayCanvas
   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

   PlayCanvas✓fullprobed8/10

   PlayCanvas engine is published to npm (`npm install playcanvas`, version 2.22.2, ~48k weekly downloads) as a standard ES module library, with docs on using the Engine standalone and scaffolding via create-playcanvas/Vite for standard bundler-based toolchains. Community confirms it integrates with other JS frameworks and modern web-dev workflows (HMR, bundlers), supporting tree-shakable ESM usage. Missing for 10: no explicit documentation or independent confirmation of tree-shaking behavior/bundle-size optimization guidance, and some community reports note setup isn't always straightforward.

   • [github] “npm install playcanvas”
   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [claimed-docs] “Use `create-playcanvas` to scaffold a Vite and TypeScript project for the Engine, React, or Web Components from one of 12 runnable starters.”
   • [probe] “PROBE runtime (recorded 2026-09-15): developer.playcanvas.com serves llms.txt plus the largest llms-full.txt of the arena (2,053,637 bytes o…”
   • [community] “You can use it in conjunction with pretty much any other JS framework available.”
   • [community] “It's certainly not super obvious to setup but there are ways to use PlayCanvas with local setup... with some tinkering you can have hot modu…”

   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

   PlayCanvas—none0/10

   No evidence pack item addresses telemetry, analytics, or opt-out settings for PlayCanvas engine, editor, or CLI tools; the axis applies (any dev tool/platform could ship telemetry controls) but there is simply no documentation or mention of such a setting.

   ⚑ flag

Iteration

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

   weight 2 · round to PlayCanvas
   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

   PlayCanvas~partialcommunity6/10

   Docs claim live editing lets you tweak materials, positions, and even modify scripts while the application is running, and community reports confirm hot-module-replacement style workflows are achievable with the local sync tooling — but multiple community sources note this setup is 'certainly not super obvious' and historically required 'tinkering,' with one report citing no easy local dev environment as a dealbreaker at the time. missing for 10: first-party benchmark or docs describing built-in near-instant reload latency, and confirmation the friction reported in community threads has been resolved.

   • [claimed-docs] “With live editing, you can tweak materials, adjust positions, and even modify scripts while your application runs.”
   • [community] “It's certainly not super obvious to setup but there are ways to use PlayCanvas with local setup... with some tinkering you can have hot modu…”
   • [community] “When I was working at a mobile game studio, we looked at this as an engine for a project. At the time we decided not to go with it since all…”
   • [community] “I recommend checking out the newly released playcanvas-sync tools which let you map your PlayCanvas project's assets to your local machine's…”

   proof ↗⚑ 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

   PlayCanvas~partialcommunity6/10

   PlayCanvas scripting uses standard JavaScript/TypeScript (ESM `.mjs` scripts with class syntax) and the full engine can be scripted via `npm install playcanvas`, giving broad API access and a productive, familiar language; community comments (e.g. comm-13) also praise its game-framework layer atop low-level access. However, the evidence pack never explicitly documents a debugger (e.g. browser devtools breakpoints, source maps, or an IDE debug workflow) tied to scripting, and some community feedback flags dev-experience friction (playcanvas-comm-2, playcanvas-comm-3, playcanvas-comm-9) around local/offline workflows that could affect debugging setup. Missing for 10: explicit documentation of a debugger/breakpoint workflow for scripts, and confirmation that the full engine API (not just scripting hooks) is exposed without gaps.

   • [claimed-docs] “ESM Scripts (`.mjs` files) — Modern ES Module-based scripts using class syntax. Recommended for new projects.”
   • [claimed-docs] “ESM Scripts (`.mjs` files) — Modern ES Module-based scripts using class syntax. **Recommended for new projects.**”
   • [claimed-docs] “Build applications against the Engine directly. Learn how to use the Engine standalone.”
   • [github] “npm install playcanvas”
   • [community] “THREE.js is very low-level framework, while PlayCanvas additionally to low-level engine access has game framework, which will allow you to c…”
   • [community] “It's certainly not super obvious to setup but there are ways to use PlayCanvas with local setup... with some tinkering you can have hot modu…”

   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

   PlayCanvas—none0/10

   Evidence shows PlayCanvas scripting is code-based (ESM/.mjs JavaScript classes) and the Editor supports drag-and-drop scene building and collaboration, but there is no mention of a node-based or visual scripting system for gameplay logic comparable to Blueprints/Bolt that would let a technical artist avoid writing code.

   • [claimed-docs] “ESM Scripts (`.mjs` files) — Modern ES Module-based scripts using class syntax. Recommended for new projects.”
   • [claimed-docs] “Want drag-and-drop scene building, real-time collaboration, or prefer visual tools over code”
   • [claimed-docs] “ESM Scripts (`.mjs` files) — Modern ES Module-based scripts using class syntax. **Recommended for new projects.**”

   proof ↗⚑ flag