Godot Engine vs Bevy

Agent access

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

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

   Bevy—none0/10

   Direct probes confirm no llms.txt exists (404) and no agent-oriented docs endpoint is served; docs.rs/crates.io provide standard human docs but nothing tailored for agent consumption per the story.

   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://bevy.org/learn/.md”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   The evidence pack contains no mention of headless mode, CI integration, or automated/scripted execution of Bevy apps; only rendering, ECS, editor-live-reload and general community sentiment are covered. Running headless in CI is a reasonable ask for a game engine, but nothing in the pack demonstrates it.

   ⚑ flag

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

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

   Bevy—none0/10

   Bevy is a game engine/library, not itself an AI agent, so an MCP server axis applies as a fair question, but evidence explicitly shows no official MCP server exists — only nascent third-party tooling (bevy_brp) built on the Bevy Remote Protocol. No official MCP server is documented.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   No evidence of an official Bevy CLI tool anywhere in the evidence pack; only cargo (Rust's generic build tool) and community projects like bevy_brp are mentioned, not a first-party CLI for AI-native workflows.

   ⚑ flag

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

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

   Bevy~partialprobed5/10

   Bevy ships a documented Rust API (in-depth reference docs, docs.rs) and even a first-party 'Bevy Remote Protocol' that a nascent community tool (bevy_brp) uses to drive the engine externally, but there is no AI-oriented public API surface: no llms.txt, no OpenAPI/swagger spec, and no official MCP server, and the remote-protocol tooling is described as nascent/community-only rather than a robust public API for programmatic driving. Missing for 10: an official machine-readable API spec (OpenAPI/llms.txt), first-party remote-control docs beyond community wrappers, and evidence of stable AI-agent usage against the API.

   • [claimed-docs] “Learn how to use Bevy's types, traits and methods using the in-depth reference documentation, complete with inline examples.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bevy.org/openapi.json, https://bevy.org/swagger.json, https://bevy.org/api/openapi.json, htt…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

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

   Bevy~partialprobed6/10

   Bevy itself ships as an official, versioned Rust SDK (the `bevy` crate on crates.io) with first-party API reference docs, quick-start guides, and migration guides, which is what an AI-native developer would build against (bevy-docs-21, bevy-docs-27, bevy-docs-15, bevy-probe-rt-1). However, pre-1.0 status with breaking changes on nearly every release, community complaints about docs being thin once you leave the intro book, and confirmed absence of llms.txt/AI-consumable doc formats make it harder for AI agents to reliably target the 'official SDK' surface (bevy-probe-rt-1, bevy-comm-12, bevy-comm-14, bevy-probe-1, bevy-probe-rt-2). Missing for 10: llms.txt/AI-friendly doc export, stability guarantees across versions, and independent evidence of AI agents successfully building against the SDK.

   • [claimed-docs] “Bevy is just a normal Rust dependency. You can either add it to an existing Rust project or create a new one.”
   • [claimed-docs] “Learn how to use Bevy's types, traits and methods using the in-depth reference documentation, complete with inline examples.”
   • [claimed-docs] “Every Bevy update brings new functionality and improvements. Follow these guides to migrate your project to the latest Bevy has to offer!”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”
   • [community] “Things have started to stabilize, but unless you're willing to get your hands dirty and deal with regular breaking changes, I don't yet reco…”
   • [community] “I'm put off by the limited docs. I've read the Bevy book, only takes a few minutes, and just like that I'm out of resources to turn to when …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Godot Engine—none0/10

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

   ⚑ flag

   Bevy—none0/10

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

   ⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Godot Engine—none0/10

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

   ⚑ flag

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

   Bevy—none0/10

   Bevy is a Rust game engine/library with no evidence of any natural-language command interface; probes confirm no llms.txt, no MCP server, and only nascent third-party remote-protocol tooling (bevy_brp), not a natural-language control layer.

   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://bevy.org/learn/.md”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

Api quality

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

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

   Bevy~partialprobed5/10

   Bevy advertises 'in-depth reference documentation, complete with inline examples' and a separate gallery of wasm-compiled examples that run directly in the browser, giving some interactive/runnable exploration of the API surface. But these are two disconnected resources rather than a unified interactive API reference, docs.rs is static/crawlable with no live-run capability, and there's no llms.txt, MCP, or agent-facing interactive console. Missing for 10: a single integrated interactive reference (e.g. rustdoc playground-style 'run' buttons on API docs), agent-facing tooling (llms.txt/MCP) to programmatically explore it, and independent confirmation the wasm examples are tied to the API reference itself.

   • [claimed-docs] “Learn how to use Bevy's types, traits and methods using the in-depth reference documentation, complete with inline examples.”
   • [claimed-docs] “Browse bevy examples compiled to wasm and running directly in your browser!”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Godot Engine—none0/10

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

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

   proof ↗⚑ flag

   Bevy—none0/10

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

   ⚑ flag

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

   weight 1 · round drawn
   Godot Engine—none0/10

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

   ⚑ flag

   Bevy—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 to Bevy
   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

   Bevy!disputedcontradicted3/10

   Bevy publishes migration guides for each release (bevy-docs-15) implying some versioning discipline, but there is no documented deprecation policy, and hands-on evidence shows the API is pre-1.0 with frequent breaking changes each release requiring real rework (bevy-comm-12, bevy-comm-13, bevy-probe-rt-1), directly undercutting reliability for an AI agent trained on prior APIs. Missing for 10: an explicit deprecation/versioning policy document, semver guarantees, and evidence that breaking changes are flagged/deprecated before removal rather than silently changed.

   • [claimed-docs] “Every Bevy update brings new functionality and improvements. Follow these guides to migrate your project to the latest Bevy has to offer!”
   • [community] “Things have started to stabilize, but unless you're willing to get your hands dirty and deal with regular breaking changes, I don't yet reco…”
   • [community] “On the last update 0.10 -> 0.11, I had to make quite a few changes on my app, but this time it compiled out of the box!”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   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 Godot Engine
   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

   Bevy~partialprobed3/10

   Bevy has a first-party Bevy Remote Protocol that could support programmatic scene/entity manipulation, and a community tool (bevy_brp) built on it, but there is no official documentation, no llms.txt, and no official MCP server — the community tooling itself is described as nascent (70 stars). Since Bevy is a code-first Rust crate, most 'scripting' is done by writing/recompiling Rust code rather than through a documented runtime scriptable interface for driving an editor. Missing for 10: first-party documented API/schema for the Remote Protocol, official MCP or agent-facing tooling, evidence of hands-on agent use creating scenes/nodes and triggering builds via that interface.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [claimed-docs] “Create, save, and load ECS worlds using Bevy's Scene system”

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

   Bevy!disputedcontradicted4/10

   Bevy has abundant examples and reference docs (bevy-docs-16, bevy-docs-22, bevy-docs-27) which help LLM familiarity, but concrete community evidence shows the API is unstable pre-1.0 with breaking changes almost every release, requiring real migration work each time (bevy-comm-12, bevy-comm-13, bevy-probe-rt-1) — meaning LLMs trained on older versions likely generate code that fails to compile against current APIs. Docs are also reported as thin/outdated relative to the pace of change (bevy-comm-14, bevy-comm-15), and there's no llms.txt or first-party AI-consumption docs (bevy-probe-1, bevy-probe-rt-2). missing for 10: evidence of first-try success rate for LLM-generated Bevy code, stable API surface across versions, and first-party AI-friendly documentation.

   • [community] “Things have started to stabilize, but unless you're willing to get your hands dirty and deal with regular breaking changes, I don't yet reco…”
   • [community] “On the last update 0.10 -> 0.11, I had to make quite a few changes on my app, but this time it compiled out of the box!”
   • [community] “I'm put off by the limited docs. I've read the Bevy book, only takes a few minutes, and just like that I'm out of resources to turn to when …”
   • [community] “There's an unofficial complement to the docs... Unfortunately it's somewhat out of date... The effort to keep it up to date is somewhat low …”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [claimed-docs] “Examples that show how to use the various features of Bevy.”

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

   Bevy—none0/10

   Bevy is a Rust game engine/library with no evidence of an official in-engine AI assistant; probes confirm no llms.txt, no official MCP, and only nascent third-party tooling (bevy_brp).

   • [probe] “PROBE llms.txt: HTTP 404 at https://bevy.org/llms.txt”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

Formats

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

   weight 2 · round drawn
   Godot Engine—none0/10

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   No evidence anywhere in the pack mentions glTF, FBX, USD, or any interchange-format import/asset-pipeline support; only glTF is a commonly known Bevy asset format but it's not cited here. Missing for 10: any docs or community mention of glTF/FBX/USD import, format fidelity, or asset-pipeline tooling.

   ⚑ flag

Import

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

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

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

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

   proof ↗⚑ flag

   Bevy~partialcommunity3/10

   Bevy's Asset V2 system does support preprocessing and .meta files, which one community commenter calls 'super useful' for pipeline automation, but no first-party docs describe import hooks, presets, or scripting workflows for batch/automated asset processing. missing for 10: official documentation on asset import hooks/presets, evidence of scripted/batch pipeline tooling, and independent confirmation beyond a single community mention.

   • [community] “Bevy is one of my favorite game engines, especially for larger projects. Asset V2 preprocessing and .meta files look super useful.”

   proof ↗⚑ flag

Marketplace

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

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

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

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

   proof ↗⚑ flag

   Bevy~partialcommunity5/10

   Bevy explicitly maintains an official third-party 'Assets' page listing community plugins, tools, and learning resources (bevy-docs-17), and community comments confirm an active ecosystem contributing new features and crates (bevy-comm-19). However, this is a curated links page rather than an integrated in-engine asset store, and the ecosystem is described as young/fragmented with docs gaps and frequent breaking changes affecting third-party plugin compatibility (bevy-comm-12, bevy-comm-15). Missing for 10: evidence of a large volume/maturity of ready-made models or marketplace-scale assets, integrated store UI, and quantified ecosystem size or quality assurance for third-party plugins.

   • [claimed-docs] “A collection of third-party Bevy assets, plugins, learning resources, and apps made by the community.”
   • [community] “Something delightful about this update: it has a lot of new features, some very early, but all by different authors. Seems like such a commu…”
   • [community] “Things have started to stabilize, but unless you're willing to get your hands dirty and deal with regular breaking changes, I don't yet reco…”
   • [community] “There's an unofficial complement to the docs... Unfortunately it's somewhat out of date... The effort to keep it up to date is somewhat low …”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Bevy—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 userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Godot Engine—none0/10

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

   ⚑ flag

   Bevy—none0/10

   The evidence pack describes Bevy's ECS, rendering, audio, and UI features but never mentions an event/trigger/rule system (e.g., Bevy Events, Observers, or ECS hooks) that would let a user define rules firing automatically on events. While such automation is plausible for a game engine's ECS, no evidence in the pack substantiates it.

   ⚑ flag

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

   weight 1 · round drawn
   Godot Engine—none0/10

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

   ⚑ flag

   Bevy—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
   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

   Bevy~partialclaimed5/10

   Bevy's official docs explicitly list 2D rendering as a first-class feature alongside 3D (bevy-docs-2, bevy-docs-3), suggesting parity rather than a 3D-only focus, and community feedback confirms active engine use for real projects. However, there is no evidence in the pack of built-in tilemap support or first-party 2D physics (these are known to be third-party crates in the Bevy ecosystem), so the story's specific claims about tilemaps and 2D physics being first-class are unconfirmed. Missing for 10: evidence of native/first-party tilemap support, evidence of native/first-party 2D physics integration, and any community confirmation of 2D-specific workflow maturity.

   • [claimed-docs] “Render real-time 2D graphics for games and apps”
   • [claimed-docs] “A modern and flexible 3D renderer”
   • [claimed-docs] “Extensible: custom shaders, materials, and render pipelines”

   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 to Bevy
   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

   Bevy~partialcommunity4/10

   Bevy's data-oriented ECS is well documented as the foundation for all engine/game logic (bevy-docs-1, bevy-docs-14, bevy-docs-20), and community accounts corroborate its data-driven, ECS-first workflow (bevy-comm-17). However, the evidence pack contains no mention of a built-in profiler/diagnostics tool, explicit job/parallel-system scheduling, or GPU instancing for heavy scenes — core parts of the story. Missing for 10: dedicated profiler tooling (e.g. tracing/diagnostics plugin), explicit job-system/parallelism documentation, and instancing support evidence.

   • [claimed-docs] “All engine and game logic uses Bevy ECS, a custom Entity Component System”
   • [claimed-docs] “Components: Rust structs that implement the Component trait”
   • [claimed-docs] “Unlike other Rust ECS implementations, which often require complex lifetimes, traits, builder patterns, or macros, Bevy ECS uses normal Rust…”
   • [community] “Pros: Very nice to work in Rust engine + Rust game. Once you get your brain thinking ECS it's tough to go back, feels very flexible. Very li…”

   proof ↗⚑ flag

Physics

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

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

   Bevy—none0/10

   The evidence pack covers ECS, rendering, audio, UI, and scenes but contains no mention of physics, rigid bodies, collision detection, or raycasting capabilities. Built-in physics is a fair question for a game engine's core-engine axis, but nothing in the docs or community evidence shows Bevy ships this out of the box.

   ⚑ 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 Bevy
   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

   Bevy~partialcommunity5/10

   Docs confirm a 'modern and flexible 3D renderer' with extensible custom shaders/materials/pipelines, and community hands-on feedback confirms shadows exist (though called 'jagged/low-res, reminds me of early Unity shadows'). However, the evidence pack never mentions global illumination, baked lighting, or a post-processing stack explicitly. Missing for 10: explicit documentation of GI/baked lighting support, explicit post-processing feature list, and independent corroboration of PBR material quality beyond the shadow-quality caveat.

   • [claimed-docs] “A modern and flexible 3D renderer”
   • [claimed-docs] “Extensible: custom shaders, materials, and render pipelines”
   • [community] “Not a criticism, but model projected shadows are very jagged or really low-res, reminds me of early Unity shadows.”

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

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

   ⚑ flag

   Bevy—none0/10

   Evidence mentions a Scene system for saving/loading ECS worlds (bevy-docs-8) but nothing about its text format being diffable/mergeable, nor any built-in multi-user collaboration tooling. The 'code-first' workflow noted in bevy-probe-rt-2 is framed around agent-driven development, not team version-control workflows, so it doesn't substantiate this story.

   • [claimed-docs] “Create, save, and load ECS worlds using Bevy's Scene system”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”

   proof ↗⚑ flag

Editor

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   Bevy's evidence describes a code-first Rust ECS engine (components, systems, scenes-as-data, hot reloading) but nothing about a visual editor with viewport, inspector, or prefab/scene composition UI; comment bevy-comm-8 even suggests users hope NOT to be forced into an in-engine editor, and probes show no official tooling filling this gap. Missing for full/partial credit: any first-party viewport/inspector GUI, prefab authoring workflow, or scene-composition editor.

   • [claimed-docs] “Create, save, and load ECS worlds using Bevy's Scene system”
   • [claimed-docs] “Get instant feedback on your changes without app restarts or recompiles”
   • [community] “The integrated code editor in Godot is actually something I don't like... I hope that Bevy users won't be forced to use the Bevy editor for …”

   proof ↗⚑ flag

Extensibility

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   Bevy's evidence shows only a code-first workflow (ECS, scenes, plugins) and mentions no official editor application to extend; the closest hint is a third-party 'bevy_brp' remote-protocol tool with just 70 stars, not first-party editor scripting/plugin support for manipulating scenes and assets. missing for 10: any first-party editor product, documented editor scripting/plugin API, or mature ecosystem tooling for automating scene/asset manipulation via an editor UI.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [claimed-docs] “Create, save, and load ECS worlds using Bevy's Scene system”

   proof ↗⚑ flag

Ci

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

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

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

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

   proof ↗⚑ flag

   Bevy~partialprobed5/10

   Bevy is a code-first Rust library built and run via cargo, with no mandatory editor (bevy-docs-21, bevy-comm-8, bevy-probe-rt-2), which inherently supports command-line/CI builds. However, there is no explicit documentation of a headless mode flag, export pipeline, or CI-specific tooling/examples, and no official CI templates or GitHub Actions references are present in the evidence pack. missing for 10: explicit headless-mode/export documentation, CI pipeline examples or templates, and confirmation of asset-building/export automation without a GUI step.

   • [claimed-docs] “Bevy is just a normal Rust dependency. You can either add it to an existing Rust project or create a new one.”
   • [community] “The integrated code editor in Godot is actually something I don't like... I hope that Bevy users won't be forced to use the Bevy editor for …”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): bevy.org serves no llms.txt (HTTP 404; docs.rs likewise) and no official MCP exists — communit…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

Server

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   The evidence pack covers Bevy's ECS, rendering, UI, audio, and platform support, but contains no mention of a headless/dedicated-server build mode, disabling rendering plugins, or server-runtime configuration. Since this is a plausible and common need for a game engine, absence of evidence means the axis is unmet rather than inapplicable.

   ⚑ flag

Testing

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

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

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   The evidence pack contains no mention of headless mode, CI test execution, integration testing, or automated test frameworks for Bevy game logic — nothing about running engine/game tests without a display or in continuous integration.

   ⚑ flag

Governance

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

   weight 1 · round drawn
   Godot Engine—none0/10

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   Evidence documents Bevy's open-source MIT/Apache-2.0 licensing and community activity, but nothing about a governing foundation, published finances, or an official public roadmap a studio could plan against — only migration guides for past releases are mentioned. missing for 10: evidence of a foundation or legal entity, published budget/financials, and a forward-looking public roadmap.

   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [claimed-docs] “Every Bevy update brings new functionality and improvements. Follow these guides to migrate your project to the latest Bevy has to offer!”
   • [community] “Something delightful about this update: it has a lot of new features, some very early, but all by different authors. Seems like such a commu…”

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

   Bevy✓fullprobed9/10

   Bevy's own site explicitly states it is 100% free forever, MIT OR Apache-2.0 licensed, with no contracts, no license fees, and no sales cuts, directly satisfying the studio-lead's ask of no royalties or per-install fees. This is corroborated independently by crates.io license metadata and by community commentary praising the permissive MIT licensing as 'no strings attached.' Missing for 10: no explicit legal/contract analysis or enterprise-scale case study confirming zero royalty obligations at large studio scale.

   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [community] “MIT License, well done! It's so refreshing to see things released with no strings attached... a breathe of fresh air as a potential end user…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

Source

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

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

   Bevy✓fullprobed9/10

   Bevy is fully open-source (MIT/Apache 2.0), with source hosted openly, allowing developers to read and modify the engine itself; community confirms code is clean/readable and license is unrestricted ('no strings attached'). Missing for 10: no explicit hands-on account of a developer patching/forking the engine source to unblock themselves, only license and code-quality corroboration.

   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [claimed-docs] “Why are we continuing to build up the ecosystems of closed-source monopolies that take cuts of our sales and deny us visibility into the tec…”
   • [community] “Got the chance of running the examples and glance over the code... it looks incredibly elegant and clean. Almost feels like this could make …”
   • [community] “MIT License, well done! It's so refreshing to see things released with no strings attached... a breathe of fresh air as a potential end user…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

Trust

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

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

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

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

   proof ↗⚑ flag

   Bevy✓fullcommunity7/10

   Bevy is licensed under MIT/Apache 2.0 with explicit 'no contracts, no license fees, no sales cuts, forever' commitments, and these are irrevocable open-source licenses that cannot retroactively reprice already-shipped games — corroborated by community praise for the license having 'no strings attached.' Missing for 10: a long multi-year track record (Bevy is a young, pre-1.0 project) and any explicit governance statement committing to never relicense future versions restrictively.

   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [community] “MIT License, well done! It's so refreshing to see things released with no strings attached... a breathe of fresh air as a potential end user…”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Bevy—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 userExport all of my data in open formats and leave

   weight 3 · round drawn
   Godot Engine~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Bevy~partialprobed5/10

   Bevy is a local, open-source Rust engine (MIT/Apache-2.0) with no cloud data lock-in, and its Scene system lets you save/load ECS worlds in the open RON format, which aligns with the openness theme. However there's no explicit documentation or tooling framed around 'exporting all your data and leaving' (e.g., data migration guides, guaranteed format stability) since Bevy isn't a hosted service holding user data in the first place. Missing for 10: explicit data-export/migration documentation, guarantees around long-term format stability given breaking API changes each release, and any first-party statement on data portability beyond the general OSS license.

   • [claimed-docs] “Create, save, and load ECS worlds using Bevy's Scene system”
   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Godot Engine✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   Bevy✓fullprobed9/10

   Bevy's source and docs are explicitly MIT OR Apache-2.0 licensed, confirmed both by first-party docs and independent runtime crates.io metadata, and community commenters corroborate the open, permissive licensing and code readability. Missing for 10: no direct GitHub repo citation in the evidence pack, though license and source availability are otherwise well-documented.

   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [community] “MIT License, well done! It's so refreshing to see things released with no strings attached... a breathe of fresh air as a potential end user…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

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

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

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

   proof ↗⚑ flag

   Bevy✓fullcommunity7/10

   Bevy is not a hosted service at all — it's an open-source (MIT/Apache-2.0) Rust library added directly as a dependency to your own project and compiled/run entirely on your own machine, satisfying self-hosting by default with no server or cloud dependency (bevy-docs-18, bevy-docs-21, bevy-docs-25). Community corroboration confirms the open license and local dev workflow (bevy-comm-2). missing for 10: explicit vendor-authored self-hosting/deployment guidance (e.g., docs discussing running Bevy apps as self-hosted servers or headless builds) and independent verification of self-hosted production deployments.

   • [claimed-docs] “It is free and open-source forever under your choice of the MIT or Apache 2.0 licenses.”
   • [claimed-docs] “Bevy is just a normal Rust dependency. You can either add it to an existing Rust project or create a new one.”
   • [claimed-docs] “100% free. Forever and always * Open Source under the permissive MIT or Apache 2.0 licenses * No contracts * No license fees * No sa…”
   • [community] “MIT License, well done! It's so refreshing to see things released with no strings attached... a breathe of fresh air as a potential end user…”

   proof ↗⚑ flag

Targets

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

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

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

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

   proof ↗⚑ flag

   Bevy~partialcommunity5/10

   Docs confirm one Bevy project can target desktop (Windows/macOS/Linux), mobile (iOS/Android) and Web via a single codebase [bevy-docs-6], and community feedback corroborates real-world mobile/web use [bevy-comm-10][bevy-comm-20]. However, there is no evidence—first-party or community—of console export capability, whether direct or via third-party porting partners, which is a key part of the story. Missing for 10: any mention of console targets (Switch/PlayStation/Xbox), official or partner-based console export tooling, or case studies of console shipping.

   • [claimed-docs] “Support for all major platforms: Windows, MacOS, Linux, Web, iOS, Android”
   • [community] “We support low-end devices well! Bevy runs well on iOS currently... Fans spinning is a known issue, but it is generally decoupled from frame…”
   • [community] “Man, you guys really kill it with blog/changelog announcements. Great job! For my use case, Bevy web (and mobile is nice too) support would …”

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

   Bevy~partialcommunity5/10

   Bevy documents official Web platform support and showcases live wasm-compiled examples running in-browser, and a community comment shows real interest in adopting Bevy specifically for web/mobile targets. However, the evidence never mentions WebGPU explicitly, payload size/optimization guidance, or any hands-on report of browser performance/bundle size — the WebGPU 'credible story' half of the claim is unevidenced. Missing for 10: explicit WebGPU backend documentation or roadmap, payload-size/optimization guidance, and independent hands-on confirmation of web build performance.

   • [claimed-docs] “Support for all major platforms: Windows, MacOS, Linux, Web, iOS, Android”
   • [claimed-docs] “Browse bevy examples compiled to wasm and running directly in your browser!”
   • [community] “Man, you guys really kill it with blog/changelog announcements. Great job! For my use case, Bevy web (and mobile is nice too) support would …”

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

   Bevy—none0/10

   Bevy is distributed exclusively as a Rust crate via crates.io/cargo (bevy-docs-21, bevy-probe-rt-1), not as an npm/JS package; its 'Web' platform support (bevy-docs-6) means compiling to WASM as a game binary, not shipping a tree-shakeable JS library a web developer imports and bundles. No evidence shows npm registry presence, ES-module packaging, or tree-shaking support.

   • [claimed-docs] “Bevy is just a normal Rust dependency. You can either add it to an existing Rust project or create a new one.”
   • [claimed-docs] “Support for all major platforms: Windows, MacOS, Linux, Web, iOS, Android”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

   proof ↗⚑ flag

Iteration

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

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

   Bevy~partialprobed5/10

   Bevy's own docs directly claim 'instant feedback on your changes without app restarts or recompiles' and cite very fast compile times (0.8–3.0s) with a 'fast compiles' config, which matches the story's intent. However, Bevy is a Rust-native engine (not script-based), so this reload speed is achieved via build tooling/dynamic linking rather than a true scripting hot-reload workflow, and there is no independent/hands-on community confirmation of this specific edit-run loop experience — community comments focus on ECS ergonomics, docs quality, and breaking changes instead. Missing for 10: independent/hands-on verification of the hot-reload claim, clarity on scripting vs. Rust recompilation semantics, and community testimony specifically about iteration speed.

   • [claimed-docs] “Get instant feedback on your changes without app restarts or recompiles”
   • [claimed-docs] “With Bevy you can expect 0.8-3.0 seconds with the "fast compiles" configuration”
   • [probe] “PROBE runtime (recorded 2026-09-15): bevy resolves on crates.io — `cargo search bevy` → 'bevy = "0.19.1" # A refreshingly simple data-driven…”

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

   Bevy~partialcommunity5/10

   Bevy uses plain Rust as its 'scripting' layer, and docs plus community comments confirm the ECS API is idiomatic, fully native Rust with no macros/lifetimes needed (bevy-docs-14, bevy-docs-20, bevy-comm-3, bevy-comm-4), which is a strong productivity/API-exposure signal. However, there is no evidence at all of a dedicated debugger or debugging workflow behind this scripting layer, and community feedback flags limited/out-of-date docs and frequent breaking changes as productivity friction (bevy-comm-14, bevy-comm-15, bevy-comm-12). Missing for 10: explicit debugger/debugging-tool evidence, confirmation of full API surface coverage beyond ECS basics, and independent hands-on accounts of debugging Bevy games.

   • [claimed-docs] “Components: Rust structs that implement the Component trait”
   • [claimed-docs] “Unlike other Rust ECS implementations, which often require complex lifetimes, traits, builder patterns, or macros, Bevy ECS uses normal Rust…”
   • [community] “I have to say the API seems to be very pleasant and simple at a glance. Kudos to the author! This pattern is a great example of how Rust ach…”
   • [community] “This is amazing. Seriously: I had a look at nearly every game engine/GUI solution in Rust and this is by far the most thought out, ergonomic…”
   • [community] “I'm put off by the limited docs. I've read the Bevy book, only takes a few minutes, and just like that I'm out of resources to turn to when …”
   • [community] “There's an unofficial complement to the docs... Unfortunately it's somewhat out of date... The effort to keep it up to date is somewhat low …”
   • [community] “Things have started to stabilize, but unless you're willing to get your hands dirty and deal with regular breaking changes, I don't yet reco…”

   proof ↗⚑ flag

Visual

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

   weight 2 · round drawn
   Godot Engine—none0/10

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

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

   proof ↗⚑ flag

   Bevy—none0/10

   Bevy is explicitly a code-first, Rust-based ECS engine (bevy-docs-1, bevy-docs-14, bevy-docs-20, bevy-docs-21) with no mention of a visual scripting system or node-based logic editor anywhere in the evidence; community feedback even discusses concerns about being forced into a code editor, reinforcing the code-only workflow.

   • [claimed-docs] “All engine and game logic uses Bevy ECS, a custom Entity Component System”
   • [claimed-docs] “Components: Rust structs that implement the Component trait”
   • [claimed-docs] “Unlike other Rust ECS implementations, which often require complex lifetimes, traits, builder patterns, or macros, Bevy ECS uses normal Rust…”
   • [claimed-docs] “Bevy is just a normal Rust dependency. You can either add it to an existing Rust project or create a new one.”
   • [community] “The integrated code editor in Godot is actually something I don't like... I hope that Bevy users won't be forced to use the Bevy editor for …”

   proof ↗⚑ flag