Babylon.js vs Bevy

Agent access

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

   weight 2 · round to Babylon.js
   Babylon.js✓fullprobed9/10

   Both doc.babylonjs.com and www.babylonjs.com serve dedicated llms.txt files (confirmed by live probe returning HTTP 200) with structured, categorized documentation summaries covering setup, features, and tooling, directly enabling an agent to be pointed at these files. missing for 10: no independent third-party confirmation of agent usage/consumption of these files in practice, and no .md mirrors of the full docs for deeper agent crawling.

   • [probe] “PROBE llms.txt: HTTP 200 at https://doc.babylonjs.com/llms.txt # Babylon.js Documentation > Babylon.js is a powerful, beautiful, simple, an…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [claimed-docs] “Setup & Installation: Framework packages, NPM support, ES6 modules”
   • [claimed-docs] “Scene Management: Multiple canvases, offscreen rendering, optimization”
   • [claimed-docs] “Playground: Interactive code editor and sharing”

   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 Babylon.js
   Babylon.js✓fullprobed7/10

   Babylon.js explicitly documents server-side/Node.js usage and provides a NullEngine specifically for headless rendering without a browser/WebGL context, which is the standard mechanism for running Babylon in CI or automated pipelines; NPM packages and ES6 modules further support scripted/headless integration. missing for 10: no independent/hands-on report of a CI pipeline actually using NullEngine, no explicit CI recipe or GitHub Actions example, and no MCP/agent-specific automation tooling.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “NPM packages for all modules”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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
   Babylon.js—none0/10

   Babylon.js is a rendering/game engine (not an agent), so the MCP-server axis applies as an ecosystem feature, but evidence explicitly shows no official MCP server exists — only a tiny, inactive community repo with 9 stars.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): despite Microsoft parentage, Babylon.js has essentially no MCP ecosystem — no official server,…”

   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 drawn
   Babylon.js—none0/10

   Babylon.js is a library/engine and the story asks whether it ships an official CLI for AI-native workflows; the evidence pack covers NPM packages, docs, and runtime probes but never mentions a CLI tool of any kind, official or otherwise.

   ⚑ 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 Babylon.js
   Babylon.js✓fullprobed8/10

   Babylon.js exposes its full functionality through a well-documented TypeScript/JavaScript API (TypeDoc class references, NPM packages for all modules, tree-shakable ES6 modules) that is the primary way any AI or human driver would programmatically control the engine, and community feedback independently praises the documentation quality and API discoverability. Missing for 10: no formal API stability/versioning contract or independent third-party audit of API completeness beyond community sentiment.

   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “TypeScript support with full IntelliSense”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [community] “Babylon is amazing, the documentation and backwards compatibility is quite something. Just finished a project with it, while the learning cu…”
   • [community] “My wife found that ThreeJS breaks backwards compatibility a lot, while Babylon is exactly the opposite. Babylon also has vastly superior doc…”

   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 to Babylon.js
   Babylon.js✓fullprobed8/10

   Babylon.js ships official, versioned NPM packages (@babylonjs/core, etc.), full TypeScript typings/IntelliSense, modular ES6 tree-shakable modules, and extensive first-party API docs plus a Playground/Inspector for iterative development — exactly what an AI-native builder needs to target a stable official SDK, corroborated by the npm registry probe (234k weekly downloads, Apache-2.0) and multiple community accounts of strong documentation and active maintenance. missing for 10: no AI-specific SDK affordances like llms.txt-formatted API references beyond the top-level doc index, and no evidence of official AI-agent tooling (MCP server) wrapping the SDK.

   • [claimed-docs] “Setup & Installation: Framework packages, NPM support, ES6 modules”
   • [claimed-docs] “TypeScript support with full IntelliSense”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [community] “Babylon is amazing, the documentation and backwards compatibility is quite something. Just finished a project with it, while the learning cu…”
   • [community] “My wife found that ThreeJS breaks backwards compatibility a lot, while Babylon is exactly the opposite. Babylon also has vastly superior doc…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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
   Babylon.js—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 drawn
   Babylon.js—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

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

   weight 3 · round drawn
   Babylon.js—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
   Babylon.js—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 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 Babylon.js
   Babylon.js~partialprobed6/10

   Babylon.js has a TypeDoc-based API reference (e.g. BABYLON.NullEngine class docs) and a separate interactive Playground for runnable code examples/sharing, which together support exploring the API with live examples. However, the evidence doesn't show these are integrated (e.g. runnable snippets embedded directly inside API reference pages) nor is there independent/hands-on corroboration of this specific workflow. Missing for 10: evidence of direct API-reference-to-playground integration, and community validation of the interactive-reference experience.

   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Playground: Interactive code editor at playground.babylonjs.com”
   • [probe] “PROBE llms.txt: HTTP 200 at https://doc.babylonjs.com/llms.txt # Babylon.js Documentation > Babylon.js is a powerful, beautiful, simple, an…”

   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
   Babylon.js—none0/10

   Babylon.js exposes only human-oriented TypeDoc API references and llms.txt files; explicit probes for OpenAPI/swagger endpoints (openapi.json, swagger.json, etc.) all returned 404, showing no machine-readable API spec is published.

   • [probe] “PROBE openapi: all candidate paths 404 (https://doc.babylonjs.com/openapi.json, https://doc.babylonjs.com/swagger.json, https://doc.babylonj…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://doc.babylonjs.com/llms.txt # Babylon.js Documentation > Babylon.js is a powerful, beautiful, simple, an…”

   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 to Babylon.js
   Babylon.js~partialclaimed4/10

   Babylon.js offers a NullEngine for headless/server-side testing and dedicated Playground/Sandbox tools (playground.babylonjs.com, sandbox.babylonjs.com) that let developers test scenes and code in isolation, which loosely maps to sandboxed testing without touching a 'production' environment. However, as a client-side rendering engine there is no concept of production data/environments analogous to a SaaS backend, so the story only partially applies. Missing for 10: explicit documentation framing these tools as a prod/test separation mechanism, and independent evidence of AI-native agents actually using NullEngine/Playground as a safe sandbox.

   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Sandbox: Model viewer at sandbox.babylonjs.com”
   • [claimed-docs] “Playground: Interactive code editor at playground.babylonjs.com”

   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

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

   weight 2 · round to Babylon.js
   Babylon.js~partialprobed4/10

   Babylon.js ships versioned npm packages (e.g. @babylonjs/core at 9.26.1) and community reports strong backward compatibility across releases, but there is no evidence of a documented, formal deprecation policy (e.g. deprecation timelines, breaking-change notices, semver commitments in docs). missing for 10: explicit documented deprecation policy, versioning/semver commitment docs, migration guides for breaking changes.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [community] “Babylon is amazing, the documentation and backwards compatibility is quite something. Just finished a project with it, while the learning cu…”
   • [community] “My wife found that ThreeJS breaks backwards compatibility a lot, while Babylon is exactly the opposite. Babylon also has vastly superior doc…”

   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 Babylon.js
   Babylon.js~partialprobed4/10

   Babylon.js exposes a fully documented JS/TS API (scenes, meshes, materials, physics, NPM packages, TypeScript IntelliSense) letting code programmatically create scenes/nodes and edit properties, plus browser tools like Inspector, Playground, and Node Material Editor for scene editing. However these are interactive browser UIs, not designed for external programmatic driving by an agent, there's no 'build' trigger concept, and a runtime probe explicitly notes no official MCP server or agent-integration layer exists (largest community MCP repo has 9 stars, inactive since mid-2025). missing for 10: a documented agent-facing interface (e.g. MCP server or CLI) to drive the Playground/Inspector/NME externally, a build-trigger mechanism, and independent evidence of agents successfully automating editor workflows.

   • [claimed-docs] “Scene Management: Multiple canvases, offscreen rendering, optimization”
   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Node Material Editor: Visual shader editor at nme.babylonjs.com”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): despite Microsoft parentage, Babylon.js has essentially no MCP ecosystem — no official server,…”

   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 Babylon.js
   Babylon.js~partialprobed6/10

   Babylon.js ships dedicated llms.txt files, extensive typed API docs, and community testimony praising documentation quality and strong backwards compatibility (stability helps LLM-generated code stay valid across versions). However, community evidence also notes it has notably less public content/examples than competitors like Three.js ('a lot more written about three than Babylon'), which limits training-data exposure for LLMs, and docs are client-rendered Next.js with no markdown mirrors, hurting scrapability. Missing for 10: direct evidence of LLM code-generation success rates, broader public example corpus comparable to more-documented competitors, and machine-readable doc mirrors beyond llms.txt.

   • [claimed-docs] “Setup & Installation: Framework packages, NPM support, ES6 modules”
   • [community] “Babylon is amazing, the documentation and backwards compatibility is quite something. Just finished a project with it, while the learning cu…”
   • [community] “My wife found that ThreeJS breaks backwards compatibility a lot, while Babylon is exactly the opposite. Babylon also has vastly superior doc…”
   • [community] “Babylon seemed much more approachable than three for basic stuff (a box and a camera). However there is a lot more written about three than …”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): despite Microsoft parentage, Babylon.js has essentially no MCP ecosystem — no official server,…”

   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
   Babylon.js—none0/10

   No evidence of an official in-engine AI assistant for generating scripts, answering API questions, or scaffolding scenes; the pack only shows llms.txt documentation files (aimed at external AI tools consuming docs) and explicitly notes an essentially nonexistent MCP ecosystem with no official server.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): despite Microsoft parentage, Babylon.js has essentially no MCP ecosystem — no official server,…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://doc.babylonjs.com/llms.txt # Babylon.js Documentation > Babylon.js is a powerful, beautiful, simple, an…”

   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 to Babylon.js
   Babylon.js~partialcommunity5/10

   Babylon.js has strong, well-documented glTF import support (dedicated importer docs, sandbox/model viewer, and general multi-format support including .babylon/glTF/STL/OBJ), and community feedback praises smooth import of 3D model data. However, there is no evidence in the pack of native FBX or USD import support, which are explicitly part of the story's required format set — missing for 10: FBX import documentation/tooling, USD import support, independent confirmation of clean FBX/USD round-tripping.

   • [claimed-docs] “source: https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF”
   • [claimed-docs] “Supports multiple file formats including .babylon, glTF, STL, OBJ, and more”
   • [claimed-docs] “Sandbox: Model viewer at sandbox.babylonjs.com”
   • [community] “Babylon.js is an amazing framework. The 3d concepts are ingrained into the API and framework. The ability to read 3d model data from Blender…”

   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 Babylon.js
   Babylon.js~partialclaimed4/10

   Babylon.js exposes glTF/OBJ/STL import via a programmatic SceneLoader API and can run headlessly via NullEngine/server-side rendering (babylonjs-docs-2, babylonjs-docs-3, babylonjs-docs-6, babylonjs-docs-8), which implies imports can be scripted rather than hand-clicked, but there is no dedicated documentation of import hooks, batch presets, or a formal asset-pipeline/automation tool for technical artists. Missing for 10: explicit pipeline/preset tooling, CLI or build-step asset processors, documented hook system for custom import automation, and independent evidence of technical artists using it this way.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “source: https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF”
   • [claimed-docs] “Supports multiple file formats including .babylon, glTF, STL, OBJ, and more”

   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 Bevy
   Babylon.js~partialprobed4/10

   Babylon.js has a real npm package ecosystem (234k weekly downloads, modular tree-shakable modules) and supports many asset import formats (glTF, OBJ, STL, .babylon), plus community-built tools like Spector.js debugger and React-BabylonJS integration mentioned in community threads. However, there is no evidence of a dedicated asset store or marketplace for ready-made models comparable to Unity/Unreal asset stores, and the runtime probe explicitly notes the ecosystem around it (e.g., MCP tooling) is thin. Missing for 10: a curated marketplace/asset store for models, a rich plugin directory analogous to Unity Asset Store, and independent evidence of third-party asset packs beyond a couple of community-mentioned tools.

   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [claimed-docs] “Supports multiple file formats including .babylon, glTF, STL, OBJ, and more”
   • [claimed-docs] “source: https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF”
   • [community] “Babylon is awesome! I just started writing a game with it. The integration with TypeScript works well and there also are very fun things lik…”
   • [community] “The impressive thing about Babylon.js is Spector, a fully functional WebGL debugger extension in Chrome which makes 3D development on the we…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): despite Microsoft parentage, Babylon.js has essentially no MCP ecosystem — no official server,…”

   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 drawn
   Babylon.js—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 userDefine rules that trigger actions automatically on events

   weight 3 · round to Babylon.js
   Babylon.js~partialcommunity3/10

   Babylon.js does include an ActionManager subsystem for defining triggers (e.g., on-pick, on-intersect) that fire actions automatically, referenced by a community user noting it 'has an action manager,' but this is not documented in the first-party doc excerpts provided and no detail on its rule scope or AI-native usage is given. Missing for 10: official documentation of the ActionManager/trigger system, examples of complex rule chaining, and any AI-agent-specific automation hooks.

   • [community] “I would say it is more of a game engine, especially compared to three.js. Babylon.js supports physics plug-ins and collisions, has an action…”

   proof ↗⚑ 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
   Babylon.js—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 Bevy
   Babylon.js~partialcommunity3/10

   Babylon.js is documented primarily as a 3D/WebGL engine; only a single community comment notes 'sprite support and other 2d-graphics functionality' and the docs mention a 2D/3D GUI system, but there is no evidence of tilemap tooling or a dedicated 2D physics workflow — 2D appears as an add-on rather than a first-class pipeline. missing for 10: tilemap support, dedicated 2D physics engine/workflow, first-party docs treating 2D as a core (not secondary) workflow, independent corroboration of sprite tooling.

   • [community] “Babylon.js is based on the Babylon Toolkit for Silverlight, and includes significantly more features than Three.js, including sprite support…”
   • [claimed-docs] “GUI System: 2D and 3D user interfaces”
   • [claimed-docs] “Physics: Havok, Cannon.js, Ammo.js integration”

   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 drawn
   Babylon.js~partialcommunity4/10

   Babylon.js clearly ships real profiling tools — the Inspector/Scene Inspector for runtime debugging and scene analysis, plus community confirmation of the Spector.js WebGL debugger — but there is no documented ECS, job/worker system, or GPU instancing API in the evidence pack for scaling heavy scenes. Community notes even flag historical GC/allocation pressure concerns around performance-sensitive code. missing for 10: explicit ECS architecture, job/worker-based parallelism, and documented instancing API/guidance for scaling heavy scenes.

   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Scene Inspector: Runtime debugging and scene analysis tools”
   • [community] “The impressive thing about Babylon.js is Spector, a fully functional WebGL debugger extension in Chrome which makes 3D development on the we…”
   • [community] “It seems to be pretty heavy on object allocation, e.g. BABYLON.Vector3.prototype.add creates a new Vector3 each time, unlike gl-matrix's in-…”
   • [community] “The next version (1.2) will remove the pressure on GC by using in-place operators and by reusing more entities.”

   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 to Babylon.js
   Babylon.js!disputedcontradicted5/10

   Docs confirm built-in physics engine integration (Havok, Cannon.js, Ammo.js, Oimo.js) and community posts mention 'physics plug-ins and collisions' as part of the engine's game-engine-like feature set, but a detailed hands-on critique explicitly calls the physics implementation 'inexcusably my first game engine level of incompetence,' citing broken velocity/acceleration handling and frame-rate dependent world time, plus another comment noting it 'doesn't care for real-world physics scale.' This is a concrete first-hand contradiction of the 'works out of the box' claim, not mere skepticism. missing for 10: raycast-specific evidence, independent benchmark refuting or confirming the physics bug claims, resolution/fix documentation.

   • [claimed-docs] “Physics: Havok, Cannon.js, Ammo.js integration”
   • [claimed-docs] “Support for multiple physics engines (Cannon.js, Oimo.js, Ammo.js)”
   • [community] “The 'Physics' in Babylon.js is at the inexcusably 'my first game engine' level of incompetence. Velocity and acceleration treated as if they…”
   • [community] “I had high hopes for babylon.js... My gripes: no 'preferred navigation feel', doesn't care for real-world physics scale, setting up a defaul…”
   • [community] “I would say it is more of a game engine, especially compared to three.js. Babylon.js supports physics plug-ins and collisions, has an action…”

   proof ↗⚑ 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
   Babylon.js~partialcommunity4/10

   Evidence confirms Babylon.js is a real-time WebGL/WebGPU rendering engine with a Node Material Editor and native glTF PBR material import, implying baseline PBR support, but the pack contains no explicit documentation of shadow mapping, global illumination/baked lighting, or a post-processing pipeline. Community threads praise visual quality and demos but don't confirm these specific pipeline features either. Missing for 10: explicit shadow system docs, GI/lightmapping baked-lighting docs, post-process stack documentation, and independent corroboration of PBR material fidelity.

   • [claimed-docs] “source: https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF”
   • [claimed-docs] “Node Material Editor”
   • [claimed-docs] “WebGL and WebGPU rendering support”
   • [claimed-docs] “WebGPU Support: Next-generation graphics API”
   • [community] “This has so many more capabilities than Three.js and the gap seems to be growing.”

   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
   Babylon.js—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

   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 Babylon.js
   Babylon.js~partialcommunity4/10

   Babylon.js ships an Inspector for runtime scene debugging/editing, a Node Material Editor, Playground, and Sandbox model viewer, but these are auxiliary tools layered on a code-first engine rather than a unified viewport+prefab+scene-composition editor that serves as the primary level-building workflow. Community commentary confirms it's approached as a programming API/game engine, not an artist-first editor. missing for 10: a full prefab/scene-composition system, an integrated single viewport combining inspector+asset placement+hierarchy editing as the primary workflow, and evidence of technical artists building levels without code.

   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Scene Inspector: Runtime debugging and scene analysis tools”
   • [claimed-docs] “Node Material Editor”
   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Sandbox: Model viewer at sandbox.babylonjs.com”
   • [community] “I switched from Three to Babylon two years ago... Babylon has a compact, active set of devs (I've made bug reports and seen the fix in the n…”
   • [community] “I would say it is more of a game engine, especially compared to three.js. Babylon.js supports physics plug-ins and collisions, has an action…”

   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 drawn
   Babylon.js—none0/10

   Evidence mentions an Inspector for visual scene debugging/editing and a Playground/Node Material Editor, but nothing documents an extensibility API, plugin system, or scripting interface for building custom editor tools or automating the editor itself. Missing for 10: editor plugin/extension API, documented editor scripting hooks, examples of third-party editor tools or automation scripts.

   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Scene Inspector: Runtime debugging and scene analysis tools”
   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Node Material Editor”

   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 drawn
   Babylon.js~partialprobed5/10

   Babylon.js is a library, not an editor-centric tool, so scenes are inherently built via code/npm (NullEngine for headless rendering, server-side support, NPM/ES6 modules) — this enables CLI/CI usage in principle. However, there is no documented official CLI, build/export pipeline, or CI/headless-testing example specific to game export workflows; the evidence only shows generic headless-engine primitives, not an end-to-end automated build/export toolchain. missing for 10: an official CLI or build tool for scene/asset export, documented CI pipeline examples, evidence of automated packaging/export without any editor interaction, independent confirmation of headless CI usage.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “Scene Management: Multiple canvases, offscreen rendering, optimization”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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 Babylon.js
   Babylon.js~partialclaimed6/10

   Babylon.js documents server-side usage and a NullEngine specifically designed for headless execution (no rendering context) on Node.js, which supports running game logic/physics without a GPU or DOM, per babylonjs-docs-2 and babylonjs-docs-3. However, this is a headless rendering-engine mode rather than a dedicated 'server-runtime build' product, and there's no independent/hands-on corroboration of production server deployments or performance at scale. missing for 10: independent verification of NullEngine in production server use, benchmarks/scale evidence, and any purpose-built 'server build' distinct from just importing core modules headlessly.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “NPM packages for all modules”

   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 Babylon.js
   Babylon.js✓fullclaimed7/10

   Babylon.js ships a documented NullEngine specifically for running the engine headlessly (no WebGL context) plus a dedicated server-side/Node.js support guide, which is the standard mechanism for executing engine logic in CI/unit tests. Missing for 10: independent/community corroboration of real CI pipelines using NullEngine, and no example test harness or CI config shown in the evidence.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “NPM packages for all modules”

   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
   Babylon.js—none0/10

   No evidence pack item addresses governance structure, foundation status, published finances, or a public roadmap for Babylon.js; the pack is entirely feature docs and community sentiment about technical quality.

   ⚑ 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 to Bevy
   Babylon.js✓fullprobed8/10

   The runtime probe confirms Babylon.js core packages are published under Apache-2.0, a permissive license with no royalties or per-install fees, and this is corroborated by wide npm adoption figures. Missing for 10: no explicit first-party licensing page/FAQ evidence in the pack addressing commercial game revenue or royalty terms directly, and no independent legal/community discussion confirming this understanding.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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 to Bevy
   Babylon.js✓fullprobed7/10

   Babylon.js is confirmed Apache-2.0 licensed and distributed as open npm packages (@babylonjs/core), and community reports describe developers filing GitHub bug reports and seeing fixes merged within nightly builds, indicating the source is open, forkable, and modifiable in practice. Missing for 10: explicit product docs on the contribution/build-from-source workflow and any direct developer account of forking the engine to patch internals.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [community] “three.js seems more well known/established than babylon... I went with babylon and I'm glad I did. Better performance and the object names a…”
   • [community] “I switched from Three to Babylon two years ago... Babylon has a compact, active set of devs (I've made bug reports and seen the fix in the n…”
   • [community] “I would say it is more of a game engine, especially compared to three.js. Babylon.js supports physics plug-ins and collisions, has an action…”

   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 drawn
   Babylon.js✓fullprobed7/10

   Babylon.js is confirmed as Apache-2.0 licensed open-source software (babylonjs-probe-rt-1), a permissive license model that structurally cannot retroactively reprice shipped games — there is no paid-tier or revenue-share license to alter. No evidence in the pack shows any history of license or pricing changes, and community discussion focuses on technical quality, not licensing disputes. Missing for 10: an explicit historical narrative confirming multi-year license stability or any statement addressing past licensing changes (or lack thereof).

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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 Babylon.js
   Babylon.js~partialclaimed5/10

   Babylon.js is fundamentally a code-first library (NPM/ES6 modules, TypeScript, NullEngine for headless/server-side use) so most scene, mesh, material and physics functionality is exposed programmatically, and NullEngine explicitly supports server-side/headless scenarios without any UI [babylonjs-docs-2, babylonjs-docs-3, babylonjs-docs-24, babylonjs-docs-25]. However, the evidence never explicitly confirms that visual-only tools like the Node Material Editor, Inspector, or Playground have complete 1:1 API equivalents for every feature they expose, so full UI/API parity is inferred rather than documented. Missing for 10: explicit documentation stating NME/Inspector-generated configurations are always fully reproducible via API alone, and independent confirmation of this parity.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “Node Material Editor”
   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Node Material Editor: Visual shader editor at nme.babylonjs.com”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”

   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
   Babylon.js~partialprobed5/10

   Babylon.js is open-source (Apache-2.0) and supports open, standard 3D file formats like glTF, OBJ, and STL alongside its own .babylon format, so scene/asset data isn't locked into a single proprietary format and can be exported or moved elsewhere. However, there is no first-party or community evidence of a comprehensive 'export all my data and leave' workflow, no discussion of data portability/lock-in avoidance as a stated goal, and no independent confirmation that full round-trip export preserves all engine-specific features (physics, materials, animations). missing for 10: explicit data-export/migration documentation, independent verification of full-fidelity export to open formats, and any framing of this as an intentional anti-lock-in feature.

   • [claimed-docs] “Supports multiple file formats including .babylon, glTF, STL, OBJ, and more”
   • [claimed-docs] “source: https://doc.babylonjs.com/features/featuresDeepDive/importers/glTF”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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
   Babylon.js✓fullprobed9/10

   Babylon.js core is confirmed Apache-2.0 licensed and published on npm (v9.26.1), and the project is well known to be hosted openly on GitHub with full source visible; runtime probe corroborates the license and package registry data. Missing for 10: no explicit evidence pack citation of the GitHub repository page itself or contribution guidelines to fully corroborate open-source hosting beyond the npm license field.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   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 drawn
   Babylon.js✓fullprobed7/10

   Babylon.js is an Apache-2.0 licensed npm package/library that runs entirely client-side or server-side (NullEngine, documented server-side support), so a user can self-host the core engine simply by installing it in their own infrastructure with no vendor cloud dependency; runtime probe confirms open license and active npm distribution. Missing for 10: no explicit self-hosting/deployment guide (e.g., Docker image, on-prem playground/inspector hosting instructions) and no independent report of someone self-hosting the full toolchain (playground, inspector, sandbox) rather than just the core engine.

   • [claimed-docs] “source: https://doc.babylonjs.com/setup/support/serverSide”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”
   • [claimed-docs] “NPM packages for all modules”

   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 drawn
   Babylon.js~partialclaimed5/10

   Babylon.js supports web (WebGL/WebGPU) export and claims native cross-platform via Babylon Native, which could enable desktop/mobile builds, but the evidence pack contains no documentation of console export (PlayStation, Xbox, Switch) or partner pipelines, and no independent confirmation of Babylon Native's mobile/desktop deployment maturity. missing for 10: console export/partner program details, hands-on evidence of desktop/mobile builds via Babylon Native, independent corroboration of cross-platform deployment success.

   • [claimed-docs] “Cross-Platform: Runs seamlessly on web browsers and natively with Babylon Native”
   • [claimed-docs] “WebGL and WebGPU rendering support”
   • [claimed-docs] “WebGPU Support: Next-generation graphics API”

   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 to Babylon.js
   Babylon.js~partialcommunity6/10

   Docs confirm both WebGL and WebGPU rendering support plus tree-shakable ES6/NPM modules for payload optimization, but community evidence flags real payload concerns (Babylon is described as 3x the size of Three.js, and long load times/50MB scenes were reported), which Babylon's own reps acknowledge and only partially address via incremental loading. Missing for 10: independent verification of actual bundle sizes after tree-shaking, benchmarked WebGPU performance/adoption data, and confirmation that payload complaints have been resolved in recent versions.

   • [claimed-docs] “WebGL and WebGPU rendering support”
   • [claimed-docs] “WebGPU Support: Next-generation graphics API”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [community] “My wife found that ThreeJS breaks backwards compatibility a lot, while Babylon is exactly the opposite. Babylon also has vastly superior doc…”
   • [community] “demos look quite nice but wow they take a long time to load, took about 5 minutes to download 50mb for a short scene, makes me wonder if dow…”
   • [community] “To avoid having too long loading time, we have support for incremental loading. But we definitely need to work on optimizing the size of our…”

   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 to Babylon.js
   Babylon.js✓fullprobed9/10

   Babylon.js ships as NPM packages (@babylonjs/core, confirmed live on npm registry with real version/downloads), documents ES6 module support, and explicitly advertises a modular, tree-shakable ES6 architecture for bundlers. TypeScript support with full IntelliSense further confirms standard toolchain integration. Missing for 10: independent third-party benchmark/case study of tree-shaking effectiveness in a real bundler beyond vendor docs.

   • [claimed-docs] “Setup & Installation: Framework packages, NPM support, ES6 modules”
   • [claimed-docs] “NPM packages for all modules”
   • [claimed-docs] “Modular design with tree-shakable ES6 modules”
   • [claimed-docs] “TypeScript support with full IntelliSense”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view @babylonjs/core version` → 9.26.1 (Apache-2.0, 234,040 weekly downloads via the public npm AP…”

   proof ↗⚑ 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
   Babylon.js~partialclaimed4/10

   Babylon.js offers a Playground for instant in-browser code iteration and NullEngine/headless testing, which supports fast preview cycles, but there is no evidence of actual hot-reload tooling (e.g., a dev server with HMR for local project scripts) or documentation describing an edit-run loop for typical game-dev workflows outside the Playground sandbox. missing for 10: dedicated hot-reload/watch tooling for local script changes, first-party dev-server integration, independent hands-on confirmation of near-instant reload during real project development.

   • [claimed-docs] “Playground: Interactive code editor and sharing”
   • [claimed-docs] “Playground: Interactive code editor at playground.babylonjs.com”
   • [claimed-docs] “source: https://doc.babylonjs.com/typedoc/classes/BABYLON.NullEngine”
   • [claimed-docs] “Inspector: Visual debugging and scene editing”

   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 Babylon.js
   Babylon.js✓fullcommunity7/10

   Babylon.js uses JavaScript/TypeScript as its scripting language, with full TypeScript IntelliSense exposing the entire engine API (babylonjs-docs-12), and ships the Inspector/Scene Inspector for runtime debugging plus community corroboration of the Spector WebGL debugger extension making development easier (babylonjs-docs-13, babylonjs-docs-20, babylonjs-comm-10). Community testimonials also confirm productive TS integration in real projects (babylonjs-comm-17). missing for 10: independent benchmarking of scripting productivity vs other engines, deeper evidence the debugger covers full script-level breakpoints/stepping (vs just WebGL call inspection), and first-party docs explicitly tying TypeScript API completeness to debugger workflow.

   • [claimed-docs] “TypeScript support with full IntelliSense”
   • [claimed-docs] “Inspector: Visual debugging and scene editing”
   • [claimed-docs] “Scene Inspector: Runtime debugging and scene analysis tools”
   • [community] “The impressive thing about Babylon.js is Spector, a fully functional WebGL debugger extension in Chrome which makes 3D development on the we…”
   • [community] “Babylon is awesome! I just started writing a game with it. The integration with TypeScript works well and there also are very fun things lik…”

   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
   Babylon.js—none0/10

   Evidence shows a Node Material Editor (visual shader/material editor) and a code-based Playground, but nothing about a visual scripting system for gameplay logic (e.g., a node-based behavior/flow graph) that would let a technical artist avoid writing code for game logic.

   • [claimed-docs] “Node Material Editor”
   • [claimed-docs] “Node Material Editor: Visual shader editor at nme.babylonjs.com”
   • [claimed-docs] “Playground: Interactive code editor and sharing”

   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