Babylon.js vs PlayCanvas

Agent access

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

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

   PlayCanvas✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas✓fullprobed9/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

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

   PlayCanvas~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   PlayCanvas✓fullprobed7/10

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

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

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

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

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

Agentic features

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

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

   PlayCanvas~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

Api quality

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

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

   PlayCanvas—none0/10

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

   ⚑ flag

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

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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

Agent editor

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

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

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

Codegen

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

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

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

Copilot

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

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

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

Formats

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

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

   PlayCanvas—none0/10

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

   ⚑ flag

Import

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

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

   PlayCanvas~partialcommunity3/10

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

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

   proof ↗⚑ flag

Marketplace

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

   weight 2 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

   ⚑ flag

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

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

   PlayCanvas~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas—none0/10

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

   ⚑ flag

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

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

   PlayCanvas~partialcommunity5/10

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

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

   proof ↗⚑ flag

2d

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

   weight 2 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

Performance

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

   weight 2 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

   ⚑ flag

Physics

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

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

   PlayCanvas~partialcommunity6/10

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

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

   proof ↗⚑ flag

Rendering

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

   weight 3 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

   ⚑ flag

Collaboration

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

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

   PlayCanvas!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

Editor

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

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

   PlayCanvas~partialcommunity6/10

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

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

   proof ↗⚑ flag

Extensibility

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

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

   PlayCanvas✓fullprobed7/10

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

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

   proof ↗⚑ flag

Ci

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

   weight 3 · round to Babylon.js
   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

   PlayCanvas~partialcommunity4/10

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

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

   proof ↗⚑ flag

Server

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

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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

Testing

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

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

   PlayCanvas—none0/10

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

   ⚑ flag

Governance

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

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

   PlayCanvas—none0/10

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

   ⚑ flag

License

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

   weight 3 · round to Babylon.js
   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

   PlayCanvas✓fullprobed7/10

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

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

   proof ↗⚑ flag

Source

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

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

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

Trust

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

   weight 2 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

   ⚑ flag

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

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

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas~partialcommunity5/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas✓fullprobed9/10

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

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

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Babylon.js
   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

   PlayCanvas!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

Targets

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

   weight 3 · round to Babylon.js
   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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

Web

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

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

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

Iteration

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

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

   PlayCanvas~partialcommunity6/10

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

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

   proof ↗⚑ flag

Language

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

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

   PlayCanvas~partialcommunity6/10

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

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

   proof ↗⚑ flag

Visual

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

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

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag