Unity vs PlayCanvas

Agent access

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

   weight 2 · round to PlayCanvas
   Unity~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Unity—none0/10

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to PlayCanvas
   Unity~partialprobed6/10

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

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

   proof ↗⚑ flag

   PlayCanvas✓fullprobed9/10

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

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

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Unity
   Unity✓fullprobed7/10

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

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

   proof ↗⚑ flag

   PlayCanvas~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Unity
   Unity✓fullprobed8/10

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

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

   proof ↗⚑ flag

   PlayCanvas✓fullprobed7/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to PlayCanvas
   Unity✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Unity—none0/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to PlayCanvas
   Unity—none0/10

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

   ⚑ flag

   PlayCanvas~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Unity—none0/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

Codegen

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

   weight 2 · round to PlayCanvas
   Unity—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas~partialprobed6/10

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

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

   proof ↗⚑ flag

Formats

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

   weight 2 · round drawn
   Unity—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Unity~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

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

   proof ↗⚑ flag

Performance

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

   weight 2 · round drawn
   Unity—none0/10

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to PlayCanvas
   Unity—none0/10

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

   ⚑ flag

   PlayCanvas✓fullprobed8/10

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

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

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Unity—none0/10

   The evidence pack contains no mention of data residency, regional storage options, or compliance controls for where Unity Cloud/AI data is stored; only general product, pricing, and AI-credits documentation is present. This is a fair question for a platform with cloud services and AI features, so absence of evidence means 'none' rather than 'na'.

   ⚑ flag

   PlayCanvas—none0/10

   No evidence discusses data residency, region selection, or storage location controls for PlayCanvas projects/data; one community comment even notes concerns about code living on PlayCanvas's own servers with no mention of region choice. Missing for 10: any documentation of data residency/region options, self-hosting for data control (self-hosted apps mentioned relate to app deployment, not project data storage), or compliance/data-location settings.

   • [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…”
   • [claimed-docs] “Download Apps for Self-hosting”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Unity—none0/10

   No evidence pack item addresses opting out of AI training data usage, data privacy controls for Unity AI features, or any policy/toggle preventing content from being used to train models; only unrelated docs, pricing/community drama, and MCP/CLI evidence are present.

   ⚑ flag

   PlayCanvas—none0/10

   No evidence in the pack addresses AI-training data usage, opt-out controls, or a privacy policy statement regarding model training on user content/projects; this is an applicable privacy-posture axis for a cloud-hosted product handling user assets and code, but no documentation or community source confirms such a control exists.

   ⚑ flag

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

   weight 2 · round drawn
   Unity—none0/10

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

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

   proof ↗⚑ flag

   PlayCanvas—none0/10

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

   ⚑ flag

Iteration

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

   weight 2 · round to PlayCanvas
   Unity—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

   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