Unity vs Godot Engine

Agent access

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

   weight 2 · round to Unity
   Unity~partialprobed5/10

   unity.com serves a root llms.txt file (unity-docs-15, unity-docs-16, unity-probe-rt-2) that an agent could be pointed at, but the actual technical documentation site (docs.unity3d.com) returns 404 for llms.txt and has no markdown mirrors of manual pages (unity-probe-1, unity-probe-2, unity-probe-rt-2), so agent-oriented docs coverage is only marketing-site-deep. missing for 10: llms.txt or agent-readable docs covering the actual API/manual reference (docs.unity3d.com), evidence of agents successfully consuming these docs in practice.

   • [claimed-docs] “Unity’s free plan, Unity Personal, is for individuals and small organizations with less than $100K of revenue and funds raised in the last 1…”
   • [claimed-docs] “Create and optimize high-end games and interactive experiences. Bring your team’s vision to life with Unity’s real-time development platform…”
   • [probe] “PROBE runtime (recorded 2026-09-15): unity.com serves a site-root llms.txt ('# Unity — Develop, deploy, and grow with Unity...'), but docs.u…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.unity3d.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.unity3d.com/Manual/index.html.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Unity✓fullprobed8/10

   Unity's Editor and Player support extensive command-line arguments (unity-docs-6, unity-docs-7) including an explicit headless mode with no display/input (unity-docs-8), enabling automation and CI pipelines; Unity Hub is also installable headlessly via package managers (unity-probe-rt-3), supporting real-world CI build setups. One community report notes cost barriers to setting up a CI build server (unity-comm-13), but this is a licensing/cost complaint rather than a technical failure of headless capability. Missing for 10: independent hands-on verification of a full CI pipeline example and more detail on batchmode build automation scripts.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity Hub installs keylessly from Homebrew (cask unity-hub 3.21.2, 'Management tool for Unity') — the e…”
   • [community] “The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license... For the same reason, we coul…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Unity—none0/10

   Evidence shows Unity ships an official MCP *server* (com.unity.ai.assistant) so external AI agents can connect to and control Unity — the opposite direction of this story, which asks whether Unity itself can plug in external MCP servers to use their tools. No evidence indicates Unity's AI Assistant or Editor can act as an MCP client/host consuming third-party MCP servers.

   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Unity
   Unity~partialprobed6/10

   Unity ships an official MCP server (unity-mcp-get-started docs, unity.com/features/ai 'View MCP Docs') bundled in the com.unity.ai.assistant package, letting agents connect to the Editor. However it's beta, closed-source with no public repo or standalone package (no keyless handshake), and AI usage is metered via Unity Credits, while the much larger community MCP (CoplayDev/unity-mcp, 14k+ stars) suggests the official one is not the primary integration path. Missing for 10: open-source/self-hostable server, GA (non-beta) status, broader independent adoption evidence of the official server itself.

   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [claimed-docs] “Whenever you generate an image, create a 3D model, produce a sound effect, or send a message to the Assistant, you spend Unity Credits from …”

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Unity✓fullprobed7/10

   Unity ships a well-documented official CLI for the Editor and Player, supporting batch/headless mode, custom arguments, and automated build workflows (unity-docs-6/7/8/9, unity-probe-5), which is exactly the kind of scriptable interface an AI agent could drive for CI/automation. Missing for 10: no AI-specific CLI tooling and the docs aren't machine-readable (llms.txt/.md mirrors 404 per unity-probe-rt-2), limiting direct agent ingestion of the CLI reference itself.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): unity.com serves a site-root llms.txt ('# Unity — Develop, deploy, and grow with Unity...'), but docs.u…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Unity
   Unity✓fullprobed8/10

   Unity ships an extensively documented public Scripting API for editor/runtime automation, plus documented command-line/batchmode interfaces for headless CI-driven builds, and an official MCP server (com.unity.ai.assistant) explicitly for AI-driven control of the editor, corroborated by community MCP adoption. This goes beyond a typical closed product and gives AI-native users multiple documented, programmatic entry points. Missing for 10: a formal OpenAPI/REST spec (docs.unity3d.com openapi probes 404) and independent hands-on validation of the MCP server's completeness.

   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity Hub installs keylessly from Homebrew (cask unity-hub 3.21.2, 'Management tool for Unity') — the e…”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Unity
   Unity✓fullprobed7/10

   Unity documents extensive official SDK-style surfaces: the public Scripting API for direct C# integration (unity-docs-11), the Package Manager ecosystem for extending functionality (unity-docs-13), editor extensibility APIs (unity-docs-10), and CLI/automation hooks for headless and CI workflows (unity-docs-6,7,8,9, unity-probe-5). It also ships an official MCP server for AI-assistant integration (unity-probe-4, unity-probe-rt-1), directly relevant to AI-native usage, though distribution is closed (no public repo) and metered via credits rather than a keyless open SDK. Missing for 10: no dedicated multi-language SDK page, no OpenAPI/REST spec (probes show 404s), and no llms.txt/markdown mirror on the actual docs site (only on unity.com marketing pages).

   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”
   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “PROBE runtime (recorded 2026-09-15): unity.com serves a site-root llms.txt ('# Unity — Develop, deploy, and grow with Unity...'), but docs.u…”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Unity
   Unity~partialprobed5/10

   Unity ships an in-editor AI Assistant (part of com.unity.ai.assistant, metered via Unity Credits) that can chat, generate images/3D models/sound effects, suggesting some AI-driven help inside the editor, and this is corroborated by a live MCP integration for the Assistant. However, evidence never shows the Assistant producing analytical 'insights' from a user's own project data (e.g., analytics, performance suggestions) — it's framed as generative-content assistance rather than data-driven insight generation. Missing for 10: dedicated documentation of data-analysis/insight features, independent hands-on validation of insight quality, and detail beyond generic 'send a message to the Assistant.'

   • [claimed-docs] “Whenever you generate an image, create a 3D model, produce a sound effect, or send a message to the Assistant, you spend Unity Credits from …”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Unity
   Unity~partialprobed5/10

   Unity supports background/unattended automation via documented CLI and headless-mode Editor/Player flags for CI-style builds (unity-docs-6/7/8, unity-probe-5, unity-probe-rt-3), and it also ships an official (beta) MCP server for AI-assistant integration (unity-probe-rt-1) that could drive agentic workflows. However, there's no evidence of built-in scheduling, triggers, or a persistent agent-orchestration layer — automation still requires external CI tooling or scripting rather than a native 'set-and-forget' automation feature. Missing for 10: native scheduling/trigger system, documented autonomous agent workflows beyond beta MCP, independent hands-on confirmation of unattended background runs.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity Hub installs keylessly from Homebrew (cask unity-hub 3.21.2, 'Management tool for Unity') — the e…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Unity
   Unity~partialprobed6/10

   Unity docs confirm a built-in AI Assistant (com.unity.ai.assistant) that lets users generate images, 3D models, sound effects, and chat with the Assistant directly inside the Editor, metered via Unity Credits — a genuine in-product AI delegate. However, the feature is explicitly beta, evidence is thin on scope/reliability, and no independent/hands-on corroboration of its usefulness exists. Missing for 10: independent hands-on validation of the Assistant's task quality, detail on task scope/limits beyond asset generation, and confirmation it is GA rather than beta.

   • [claimed-docs] “Whenever you generate an image, create a 3D model, produce a sound effect, or send a message to the Assistant, you spend Unity Credits from …”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Unity
   Unity~partialprobed6/10

   Unity ships an official AI Assistant that accepts natural-language messages (consuming Unity Credits per message) and an official MCP server (beta) integrated into the Editor, per unity-docs-14 and unity-probe-rt-1, showing genuine natural-language operation of the tool. However this is explicitly beta, credit-metered, has no public/open repo (closed distribution), and there's no independent hands-on evidence of its reliability compared to the much larger community MCP project. Missing for 10: independent/hands-on validation of the Assistant's command execution, GA (non-beta) status, and documentation of the scope of natural-language commands it can actually perform.

   • [claimed-docs] “Whenever you generate an image, create a 3D model, produce a sound effect, or send a message to the Assistant, you spend Unity Credits from …”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Unity—none0/10

   The docs manual and scripting reference exist, but there's no evidence of an interactive API reference with runnable/executable code examples — probes explicitly show no OpenAPI spec, no llms.txt/docs-md mirrors at docs.unity3d.com, and no interactive sandbox is mentioned anywhere in the pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.unity3d.com/openapi.json, https://docs.unity3d.com/swagger.json, https://docs.unity3d.c…”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.unity3d.com/Manual/index.html.md”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.unity3d.com/llms.txt”
   • [probe] “PROBE runtime (recorded 2026-09-15): unity.com serves a site-root llms.txt ('# Unity — Develop, deploy, and grow with Unity...'), but docs.u…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Unity—none0/10

   Unity is a game engine/editor, not an API-driven service, but the story asks specifically about a machine-readable API spec (OpenAPI or equivalent); probes explicitly confirm none exists — all candidate OpenAPI/Swagger paths return 404 and there is no llms.txt or docs-md mirror on the documentation domain. Since Unity does expose scripting/editor APIs and even MCP tooling, this axis is applicable to its ecosystem but the evidence shows the specific artifact is absent.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.unity3d.com/openapi.json, https://docs.unity3d.com/swagger.json, https://docs.unity3d.c…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.unity3d.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.unity3d.com/Manual/index.html.md”
   • [probe] “PROBE runtime (recorded 2026-09-15): unity.com serves a site-root llms.txt ('# Unity — Develop, deploy, and grow with Unity...'), but docs.u…”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Unity—none0/10

   No evidence describes a sandbox/test environment for Unity's AI/MCP tooling that isolates test data from production; the pack only covers general Unity engine features, pricing controversy, and MCP server existence with no mention of sandbox vs. production data separation.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Unity—none0/10

   Evidence shows Unity exposes scripting/editor APIs and packages (unity-docs-11, unity-docs-13) but nothing documents a versioning scheme or deprecation policy for these APIs, and probes show no OpenAPI spec or machine-readable API docs (unity-probe-3, unity-probe-2). Missing for 10: any documented API versioning scheme, deprecation notices/timelines, or changelog policy for Unity's scripting/runtime APIs.

   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.unity3d.com/openapi.json, https://docs.unity3d.com/swagger.json, https://docs.unity3d.c…”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.unity3d.com/Manual/index.html.md”

   proof ↗⚑ flag

   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

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 Unity
   Unity✓fullprobed8/10

   Unity documents a comprehensive scripting/editor extension API (custom inspectors, EditorWindows, AssetDatabase, Package Manager) plus command-line/headless automation for builds (unity-docs-6/7/8/9/10/11/12/13), and ships an official MCP server for AI agents inside the com.unity.ai.assistant package with a dedicated get-started manual page (unity-probe-4, unity-probe-rt-1), reinforced by a large third-party community MCP server (14k+ stars) enabling agent-driven scene/property/build workflows. Missing for 10: no public repo/keyless access to the official MCP server (closed distribution, credit-metered) and no independent hands-on verification of an agent actually creating scenes/nodes end-to-end via the documented interface.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”

   proof ↗⚑ flag

   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

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 Godot Engine
   Unity—none0/10

   The evidence pack contains no data on LLM code-generation success rates, model familiarity with Unity's C# API, or first-try correctness of AI-generated scripts — only general docs, pricing drama, and MCP/CLI tooling notes. Without concrete evidence (docs, benchmarks, or community reports) speaking to this axis, it cannot be credited.

   ⚑ flag

   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

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 Unity
   Unity~partialprobed6/10

   Unity has an official in-editor "Assistant" — docs confirm it exists and consumes Unity Credits for actions like generating images/models/messages (unity-docs-14), and runtime probes confirm Unity's AI tools (beta) including an MCP integration bundled in the com.unity.ai.assistant package (unity-probe-rt-1, unity-probe-4). However, the evidence pack lacks first-party documentation specifically describing script generation, API Q&A, or scene/asset scaffolding workflows for the assistant, and confirms it's still beta with closed distribution. Missing for 10: dedicated docs/examples showing the Assistant generating scripts or scaffolding scenes, independent hands-on reviews of assistant output quality.

   • [claimed-docs] “Whenever you generate an image, create a 3D model, produce a sound effect, or send a message to the Assistant, you spend Unity Credits from …”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “official MCP server documented at https://docs.unity3d.com/Packages/com.unity.ai.assistant@latest/index.html?subfolder=/manual/integration/u…”

   proof ↗⚑ flag

   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

Inference

1. game developerRun ML models inside the game — an official inference runtime for on-device model execution

   weight 1 · round drawn
   Unity—none0/10

   The evidence pack covers Unity's editor AI Assistant, MCP integration, and general engine features, but contains no mention of an on-device ML inference runtime (e.g., Unity Sentis/Barracuda) for running models inside a shipped game. Absence of evidence for this applicable capability means it cannot be credited.

   ⚑ flag

   Godot Engine—none0/10

   No evidence of any official ML inference runtime (e.g., ONNX/TensorFlow Lite integration) built into Godot for on-device model execution; the evidence pack covers scripting, export, plugins, and community sentiment but nothing about ML inference. Missing for 10: official inference API/runtime docs, model-loading tutorials, any first-party ML/AI execution feature.

   ⚑ flag

Formats

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

   weight 2 · round drawn
   Unity—none0/10

   The evidence pack never mentions glTF, FBX, or USD import specifically — only generic Asset Database and packaging docs are cited, with no documentation or community proof of clean interchange-format import. Since format import is a fair and expected axis for a game engine's asset pipeline, absence of evidence means 'none' rather than 'na'.

   ⚑ flag

   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

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
   Unity~partialclaimed5/10

   Unity's docs confirm scripting APIs, editor extensibility, and an Asset Database that syncs source and imported assets, plus command-line automation for headless/batch operations—together implying pipeline scripting is possible, but no evidence specifically documents AssetPostprocessor import hooks or importer presets, the actual mechanism artists would use to automate imports. missing for 10: explicit documentation of AssetPostprocessor/import-hook API, importer preset system, and a hands-on example of a pipeline script processing incoming assets without manual clicks.

   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”
   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”

   proof ↗⚑ flag

   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

Marketplace

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

   weight 2 · round to Unity
   Unity✓fullprobed9/10

   Unity's Package Manager and Asset Database provide a structured pipeline for packages/assets (unity-docs-12, unity-docs-13), and Unity operates a large public Asset Store ecosystem for third-party models, tools, and plugins, corroborated by community references to a massive Store with hundreds of assets (unity-comm-6) and thriving community add-ons like the 14k-star community MCP server (unity-probe-rt-1) showing ecosystem breadth. Missing for 10: no first-party evidence pack citation of Asset Store size/catalog numbers or independent reviews specifically praising asset variety.

   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”
   • [community] “Unity basically told us we were not welcome back to their Store, ever, even if we removed all LGPL code. Yet there are currently hundreds of…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Unity~partialclaimed4/10

   Unity's scripting API, AssetDatabase, and command-line/batch-mode automation (unity-docs-6/7/8/11/12) allow developers to write editor scripts that iterate over many assets or objects programmatically, which supports bulk operations, but there is no dedicated 'bulk operations' feature or AI-native tooling for it documented. Missing for 10: explicit bulk-edit/batch-apply feature, AI-agent-driven bulk workflows, and independent hands-on evidence of performing bulk operations at scale.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Unity
   Unity~partialclaimed4/10

   Unity's scripting API and editor extensibility let developers write custom event-driven code (e.g. callbacks, custom inspectors, command-line automation of build/launch workflows), which can be used to trigger actions on events, but the evidence never documents an actual declarative 'rules that trigger actions on events' system or AI-native automation trigger framework. Missing for 10: a documented rules/trigger engine (e.g. webhook-style or event-condition-action config), AI-specific automation hooks, and independent confirmation that non-scripted users can define such rules.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Unity—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

   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

2d

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

   weight 2 · round to Godot Engine
   Unity~partialclaimed3/10

   Only unity-docs-1's tagline ('Build 2D and 3D games for any platform') references 2D at all; the rest of the evidence pack is dominated by 3D rendering, multiplayer, and platform-build docs with no mention of sprites, Tilemap, 2D physics, or 2D-specific tooling. Missing for 10: dedicated 2D sprite/animation docs, Tilemap system evidence, 2D physics engine documentation, and any community corroboration that 2D is treated as first-class rather than a side feature.

   • [claimed-docs] “Build 2D and 3D games for any platform”

   proof ↗⚑ flag

   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

Performance

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

   weight 2 · round drawn
   Unity—none0/10

   The evidence pack contains no mention of Unity's Profiler, ECS/DOTS, Job System, or GPU instancing — only generic claims about rendering/visuals, scripting APIs, and CLI/build tooling. Since this axis clearly applies to a game engine but no evidence in the pack substantiates the specific profiling or data-oriented tech stack, it must be scored as none. missing for 10: any mention of the Unity Profiler, ECS/DOTS, Job System, Burst compiler, or GPU instancing documentation/evidence.

   ⚑ flag

   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

Physics

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

   weight 2 · round drawn
   Unity—none0/10

   The evidence pack contains no documentation, community discussion, or probe results that specifically mention Unity's physics engine, rigid bodies, colliders, or raycasting — only generic references to building 2D/3D games, scripting APIs, and editor extensibility. Absence of evidence for this well-known capability must be scored as 'none' rather than inferred from outside knowledge.

   ⚑ flag

   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

Rendering

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

   weight 3 · round to Unity
   Unity~partialclaimed7/10

   Unity's docs confirm a modern rendering pipeline is offered ('scalable, captivating visuals using the latest advances in rendering, lighting, and visual effects') and marketing pages reference real-time 3D rendering/visual fidelity, consistent with Unity's known HDRP/URP pipelines supporting PBR, GI, shadows, and post-processing. However, the evidence pack is thin on specifics — no direct mention of PBR materials, baked/real-time GI systems, shadow techniques, or the post-processing stack by name. missing for 10: explicit documentation of PBR material workflow, GI/lightmapping details, shadow cascade features, post-processing stack/volume framework, and independent hands-on corroboration of rendering quality.

   • [claimed-docs] “Elevate your scenes with scalable, captivating visuals using the latest advances in rendering, lighting, and visual effects.”
   • [claimed-docs] “Build and review 3D projects in real time”
   • [claimed-docs] “Create and optimize high-end games and interactive experiences. Bring your team’s vision to life with Unity’s real-time development platform…”

   proof ↗⚑ flag

   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

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 Unity
   Unity~partialclaimed2/10

   Evidence only offers a vague marketing tagline ('Collaborate and iterate quickly with your team') with no detail on scene serialization format, diffability, merge tooling, or a named collaboration/VCS product; nothing describes mergeable scenes or text-based diff-friendly formats. Missing for 10: documentation of YAML/text scene serialization mode, a smart-merge tool for scenes/prefabs, and details of a built-in version-control/collaboration product (e.g. Unity VCS/Plastic) with independent corroboration.

   • [claimed-docs] “Collaborate and iterate quickly with your team”

   proof ↗⚑ flag

   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

Editor

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

   weight 3 · round to Unity
   Unity✓fullclaimed9/10

   Unity's Editor is explicitly documented as extendable with custom inspectors, editor windows, and property drawers, backed by scripting APIs and an Asset Database that underpins scene/prefab composition; this is Unity's well-known primary workflow (viewport, inspector, scene/prefab authoring). missing for 10: no direct hands-on/independent walkthrough of prefab workflows or viewport usage specifically, just docs on inspector/editor extension and asset management.

   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”

   proof ↗⚑ flag

   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

Extensibility

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

   weight 3 · round drawn
   Unity✓fullclaimed9/10

   Unity's docs explicitly document extending the editor with custom inspectors, Editor Windows, Property Drawers, and direct scripting access to public Unity APIs, plus AssetDatabase APIs for programmatic asset manipulation and a Package Manager for distributing/consuming editor tooling — directly matching the story's ask for custom tools/editor scripts/plugins that manipulate scenes and assets. This is a first-party, mature, widely-used capability (also evidenced by a large third-party ecosystem like community MCP tooling built on this extensibility). Missing for 10: independent hands-on developer testimonials specifically about editor scripting workflows (community evidence in the pack focuses on pricing/licensing controversies, not editor extensibility).

   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [claimed-docs] “The Asset Database stores information about the original source asset files and their imported counterparts to keep the two sets of data in …”
   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”

   proof ↗⚑ flag

   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

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
   Unity✓fullprobed8/10

   Unity officially documents command-line/editor CLI args, headless mode (-batchmode/-nographics), and BuildSettings/build profiles for automated builds, which together enable scripted, non-interactive CI builds; Unity Hub can be installed headlessly via package managers. Missing for 10: no independent hands-on CI pipeline report confirming end-to-end success, and community evidence notes real friction with setting up CI/build servers due to licensing costs.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity Hub installs keylessly from Homebrew (cask unity-hub 3.21.2, 'Management tool for Unity') — the e…”
   • [community] “The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license... For the same reason, we coul…”

   proof ↗⚑ flag

   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

Server

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

   weight 2 · round to Unity
   Unity✓fullprobed8/10

   Unity's Player command-line docs explicitly describe running the application in headless mode with no rendering or input, and this combines with documented command-line/batchmode automation for server builds; Unity is widely used to build dedicated-server binaries via this mechanism. Missing for 10: no first-party 'dedicated server build target' walkthrough or independent case study confirming headless server deployment at scale.

   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”

   proof ↗⚑ flag

   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

Testing

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

   weight 2 · round to Unity
   Unity~partialcommunity5/10

   Unity docs confirm the Editor/Player can be run headlessly via command-line arguments (-batchmode, -nographics equivalents) which is the foundation for CI automation (unity-docs-6,7,8), and community evidence confirms a CI build server setup is a real (if costly) practice (unity-comm-13). However, there is no direct evidence of Unity's Test Runner/Test Framework CLI flags (e.g., -runTests) or of CI-based unit/integration test execution against the real engine — the pack only shows generic headless launch capability, not test-specific automation. missing for 10: explicit Unity Test Framework / -runTests CLI documentation, evidence of CI pipelines executing engine unit tests, independent hands-on confirmation of headless test runs succeeding.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [community] “The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license... For the same reason, we coul…”

   proof ↗⚑ flag

   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

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
   Unity—none0/10

   Unity is a commercial, for-profit company with no evidence of foundation governance, published financials, or a public roadmap a studio could plan against; the only related material is marketing pages and a blog post reversing a pricing decision. Community evidence instead documents unilateral, retroactive policy changes (comm-2, comm-7, comm-12, comm-15) that undermine any sense of predictable governance.

   • [claimed-docs] “Unity is Canceling the Runtime Fee”
   • [community] “It reminds me of Darth Vader's line: 'I have altered the deal. Pray I don't alter it further.' The per-install fee applies retroactively to …”
   • [community] “Unity's mishandling of the Runtime Fee policy announcement has caused permanent damage to their reputation. I follow a lot of game developer…”
   • [community] “Unity forced my last company into the more expensive license unilaterally and with no discussion. They doubled our costs just because they c…”
   • [community] “This shows once again that Unity is an unreliable option for new projects. The worst part is not the 4% fee, but the bluntness with which Un…”

   proof ↗⚑ flag

   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

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
   Unity!disputedcontradicted3/10

   Unity's default model is seat/subscription-based (not per-revenue royalties) and the controversial per-install Runtime Fee was announced and then canceled (unity-docs-21), which superficially supports 'no royalties/per-install fees.' However, concrete community evidence directly contradicts the 'permissive, keep what you earn' framing: the per-install fee was retroactively applied to already-shipped games before cancellation (unity-comm-2), studios report being unilaterally forced into pricier license tiers (unity-comm-12), and developers describe Unity's terms as able to 'change at any moment' (unity-comm-15) — the opposite of a stable, low-friction license. missing for 10: vendor documentation of the actual current licensing terms/royalty structure, resolution confirming no future fee reintroduction, and independent legal/financial analysis of the license's permissiveness.

   • [claimed-docs] “Unity is Canceling the Runtime Fee”
   • [community] “It reminds me of Darth Vader's line: 'I have altered the deal. Pray I don't alter it further.' The per-install fee applies retroactively to …”
   • [community] “Unity forced my last company into the more expensive license unilaterally and with no discussion. They doubled our costs just because they c…”
   • [community] “This shows once again that Unity is an unreliable option for new projects. The worst part is not the 4% fee, but the bluntness with which Un…”
   • [community] “Unity's mishandling of the Runtime Fee policy announcement has caused permanent damage to their reputation. I follow a lot of game developer…”

   proof ↗⚑ flag

   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

Source

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

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

   Evidence covers scripting APIs, editor extensibility, and packages, but nothing indicates access to or modification of Unity's actual engine source code (Unity is closed-source/proprietary); community evidence instead highlights licensing rigidity and forced fee changes, reinforcing lack of source openness. Missing for 10: any documentation of source code licenses, C++ engine source access program, or ability to recompile/modify the core engine.

   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [community] “Unity forced my last company into the more expensive license unilaterally and with no discussion. They doubled our costs just because they c…”
   • [community] “The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license... For the same reason, we coul…”

   proof ↗⚑ flag

   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

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
   Unity—none0/10

   Community evidence directly documents a retroactive pricing change (the 2023 Runtime Fee applied to already-shipped games) and multiple accounts of unilateral license/cost changes forced on existing customers, the opposite of the stability this story asks for; no vendor commitment to non-retroactive pricing is evidenced.

   • [community] “It reminds me of Darth Vader's line: 'I have altered the deal. Pray I don't alter it further.' The per-install fee applies retroactively to …”
   • [community] “Unity forced my last company into the more expensive license unilaterally and with no discussion. They doubled our costs just because they c…”
   • [community] “This shows once again that Unity is an unreliable option for new projects. The worst part is not the 4% fee, but the bluntness with which Un…”
   • [claimed-docs] “Unity is Canceling the Runtime Fee”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Godot Engine
   Unity~partialprobed5/10

   Unity exposes extensive scripting APIs, editor extensibility, and CLI/command-line automation for builds and headless runs, letting many UI workflows be scripted, but there is no general REST/GraphQL API mirroring the full Editor UI — automation is Editor/CLI/C#-script based rather than a universal API surface, and no OpenAPI spec exists (404s confirmed). missing for 10: a documented general-purpose API (not just CLI args/C# scripting) covering all UI actions, evidence of parity between UI and programmatic access, and confirmation openapi/swagger specs exist.

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Unity lets you extend the editor with your own custom inspectors and Editor Windows and you can define how properties are displayed in the i…”
   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.unity3d.com/openapi.json, https://docs.unity3d.com/swagger.json, https://docs.unity3d.c…”
   • [probe] “official CLI documented at https://docs.unity3d.com/Manual/EditorCommandLineArguments.html”

   proof ↗⚑ flag

   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

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

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

   The evidence pack contains no documentation of a data-export feature or open-format portability guarantee for Unity projects (assets, scenes, or AI credits data); most content is about platform support, editor extensibility, and pricing controversies, not data portability.

   ⚑ flag

   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

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

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

   Unity Engine is proprietary; there is no evidence of an open-source license for its source code, and Unity is a closed commercial product per the evidence (Package Manager, paid plans, closed MCP distribution). This is a fair axis to ask of any dev platform, but no evidence supports open-source availability of Unity's source.

   • [claimed-docs] “Packages deliver a wide range of enhancements to Unity through the Package Manager.”
   • [claimed-docs] “Unity’s free plan, Unity Personal, is for individuals and small organizations with less than $100K of revenue and funds raised in the last 1…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

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

   Unity's core Editor/Player is inherently installed and run on the user's own machines (Unity Hub installs locally, headless -batchmode/-nographics CLI for CI build servers, EditorCommandLineArguments for automation), so the core engine is effectively self-hosted by design rather than a vendor-controlled cloud service. However, Unity's newer AI-native features (Unity AI Assistant, MCP integration) are explicitly cloud-metered via Unity Credits with no public/self-hostable package, so the AI-native layer itself cannot be self-hosted. Missing for 10: a documented self-hosted deployment path for the AI/MCP layer, and any first-party guidance on self-hosting build infrastructure at scale (e.g. license/build-server constraints noted in community reports).

   • [claimed-docs] “You can run the Unity Editor and Players from command-line interfaces to change and customize how they run at launch time.”
   • [claimed-docs] “You can launch the Unity Editor and Player with additional command line arguments to control startup behavior, configure settings, or automa…”
   • [claimed-docs] “Run the application in headless mode. In this mode, the application doesn’t display anything or accept user input.”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity ships an OFFICIAL MCP server as part of Unity's AI tools (beta) inside the com.unity.ai.assistant…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Unity Hub installs keylessly from Homebrew (cask unity-hub 3.21.2, 'Management tool for Unity') — the e…”
   • [community] “The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license... For the same reason, we coul…”

   proof ↗⚑ flag

   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

Targets

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

   weight 3 · round to Unity
   Unity✓fullclaimed8/10

   Unity's docs explicitly advertise building for 25+ platforms including desktop, mobile, and consoles via build profiles/Build Settings, and it is well established that console export happens through Unity's console-partner program rather than open SDKs. Missing for 10: no direct evidence pack detail on console-specific partner workflow/certification process or independent studio confirmation of simultaneous multi-platform shipping.

   • [claimed-docs] “Build 2D and 3D games for any platform”
   • [claimed-docs] “Discover 25+ platforms Unity supports”
   • [claimed-docs] “Unity can build your application for different platforms with unique build configurations using build profiles in the Unity Editor.”
   • [claimed-docs] “Ship big games with small teams”

   proof ↗⚑ flag

   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

Web

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

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

   The evidence pack only offers generic cross-platform claims (e.g., '25+ platforms', 'any platform') with no mention of WebGL, WebGPU, browser payload size, or any web-specific export tooling; nothing addresses this story's specific subject.

   ⚑ flag

   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

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 drawn
   Unity—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

   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

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

   weight 2 · round drawn
   Unity—none0/10

   No evidence pack item documents a telemetry opt-out setting or privacy control for Unity; the only related evidence is a community complaint about unwanted 'phone home' logging (unity-comm-14), which if anything suggests telemetry behavior was hard to avoid rather than confirming an opt-out mechanism exists.

   • [community] “I switched to unreal several years ago because Unity had written hundreds of gigabytes of log files complaining that it could not phone home…”

   proof ↗⚑ flag

   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

Iteration

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

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

   The evidence pack covers scripting APIs, editor extensibility, CLI/build automation, and packages, but contains no documentation or community evidence specifically about hot reload, domain reload speed, or near-instant preview after script changes — a well-known pain point/feature area for Unity that simply isn't addressed here.

   ⚑ flag

   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

Language

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

   weight 3 · round to Godot Engine
   Unity~partialcommunity4/10

   Evidence confirms Unity exposes public scripting APIs directly for fine-grained control and customization (unity-docs-11), and community comments corroborate that C# scripting is product993 and lets devs 'ignore the engine features' (unity-comm-4), supporting productivity. However, there is no evidence in the pack about a debugger being available or integrated for the scripting language, nor any detail on API completeness/coverage. Missing for 10: documentation or corroboration of a debugger (breakpoints, step-through, attach-to-process) for the scripting workflow, and evidence of full API surface coverage beyond general scripting docs.

   • [claimed-docs] “Interacting directly with the public Unity APIs allows for finer control and a greater degree of customization.”
   • [community] “I used XNA, then MS killed it... then switched to Unity, been using it since 2012... As a lone indie dev I find Unreal very tedious and slow…”

   proof ↗⚑ flag

   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

Visual

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

   weight 2 · round drawn
   Unity—none0/10

   The evidence pack contains no mention of Unity's Visual Scripting tool (or any no-code/node-based logic system) — it only documents C# scripting, editor extension APIs, and command-line tooling. Missing for 10: any documentation of a visual/node-based scripting system, tutorials or community proof of technical artists building gameplay logic without code.

   ⚑ flag

   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