Unity vs three.js

Agent access

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

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

   three.js✓fullprobed9/10

   three.js publishes a llms.txt at its site root (HTTP 200 confirmed by probe) with an explicit 'Instructions for Large Language Models' section and a 363KB llms-full.txt covering complete docs, giving agents a direct machine-readable path. missing for 10: independent/community confirmation that agents actually use this llms.txt successfully in practice, and per-page markdown docs are hash-routed rather than statically addressable.

   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks - Type-safe, composable shader n…”

   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

   three.js—none0/10

   Three.js is fundamentally a browser WebGL/WebGPU library requiring a GPU-backed rendering context; the evidence pack contains no mention of headless rendering, Node.js server-side use, headless-gl/puppeteer integration, or CI automation support. This is a fair question for a rendering engine (other engines in this space document headless CI paths), so absence of evidence means 'none' rather than 'na'.

   ⚑ flag

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

   weight 3 · round to Unity
   Unity~partialprobed6/10

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

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

   proof ↗⚑ flag

   three.js—none0/10

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

   ⚑ flag

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

   three.js—none0/10

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

   ⚑ flag

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

   three.js~partialprobed6/10

   three.js exposes a well-documented JS API (WebGLRenderer/WebGPURenderer, TSL, GLTFLoader, controls) and even publishes llms.txt/llms-full.txt files explicitly aimed at LLM consumption, which supports AI-native driving of the library via npm. However this is a client-side JS library API, not a service with an OpenAPI/REST spec or an MCP server, and probes confirm no OpenAPI endpoints and no official MCP server exist. missing for 10: OpenAPI/machine-readable API spec, official MCP server, per-page static doc URLs (docs are hash-routed, only llms.txt is the structured machine path).

   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://threejs.org/openapi.json, https://threejs.org/swagger.json, https://threejs.org/api/openapi.…”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks”
   • [claimed-docs] “[GLTFLoader](https://threejs.org/docs/#examples/en/loaders/GLTFLoader)”
   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Unity
   Unity✓fullprobed7/10

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

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

   proof ↗⚑ flag

   three.js~partialprobed5/10

   three.js publishes an llms.txt/llms-full.txt with explicit LLM instructions and is consumable directly via npm, and it is an official, well-documented SDK (WebGL/WebGPU renderers, TSL, GLTFLoader, controls). However, this is a library/API rather than an 'agentic' SDK with tool-calling or agent-specific integration hooks, and there is no official MCP server or agent-oriented tooling beyond docs formatted for LLM consumption. missing for 10: no agent-specific SDK features (e.g., function-calling schemas, MCP server), no independent verification of llms.txt actually improving agent code generation, human docs are hash-routed rather than crawlable per-page.

   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks”
   • [claimed-docs] “[GLTFLoader](https://threejs.org/docs/#examples/en/loaders/GLTFLoader)”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   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

   three.js—none0/10

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

   ⚑ flag

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

   three.js—none0/10

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

   ⚑ flag

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

   three.js—none0/10

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

   ⚑ flag

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

   weight 2 · round to Unity
   Unity~partialprobed6/10

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

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

   proof ↗⚑ flag

   three.js~partialprobed3/10

   three.js publishes an llms.txt/llms-full.txt specifically to let AI coding agents generate code that drives the library, which is a step toward AI-native operability, but there is no natural-language command interface, chat layer, or MCP server that lets a user directly 'command' the renderer in natural language — an agent still has to write and run JavaScript. Missing for 10: a direct natural-language control layer, an MCP server or agent API, and independent evidence of agents successfully operating three.js purely via NL commands.

   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks”

   proof ↗⚑ flag

Api quality

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

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

   three.js~partialprobed6/10

   three.js has a documented interactive examples gallery (threejs.org/examples) and an extensive docs/manual with API references, plus an llms.txt/llms-full.txt tailored for AI agents to consume the API reference programmatically. However, the examples are not runnable/editable inline within the docs reference itself in an AI-native interactive way, there's no API playground or embedded live code editor tied to reference pages, and human doc pages are hash-routed rather than having stable per-page URLs, limiting agentic navigation. missing for 10: inline runnable/editable examples embedded in API reference pages, stable per-page doc URLs for agent navigation, and any dedicated interactive playground/sandbox tool.

   • [claimed-docs] “three.js examples”
   • [claimed-docs] “[docs](manual/#en/creating-a-scene) [examples](examples/#webgl_animation_keyframes)”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [community] “the three.js examples are good (if a little sloppy in coding style). I think the main thing that helps is some kind of previous knowledge ab…”

   proof ↗⚑ flag

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

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

   three.js~partialprobed5/10

   Three.js has no OpenAPI/Swagger spec (explicit probe of openapi.json/swagger.json paths all 404), but it does publish an 'equivalent' machine-readable artifact for AI consumption: a root-level llms.txt with an explicit 'Instructions for Large Language Models' section and a 363KB llms-full.txt covering the full API surface. This is a documentation-style machine-readable spec rather than a structured, typed API schema (no parameter/type schema, no endpoint-like structure). Missing for 10: a structured schema format (OpenAPI-equivalent with typed signatures), and any indication the llms.txt is treated as a formal versioned spec rather than prose docs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://threejs.org/openapi.json, https://threejs.org/swagger.json, https://threejs.org/api/openapi.…”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Unity—none0/10

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

   ⚑ flag

   three.js—none0/10

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

   ⚑ flag

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

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

   three.js~partialprobed4/10

   There is a Migration Guide and per-release notes documenting breaking changes between versions (e.g. 185→186), and npm shows a clear version number (0.186.0), but nothing describes a formal deprecation policy (notice periods, stable API guarantees, semver commitments) — three.js is known for frequent breaking changes on its own rolling release cadence. missing for 10: explicit deprecation policy statement, semver/API-stability guarantees, notice period before removals.

   • [claimed-docs] “[Migration Guide](/mrdoob/three.js/wiki/Migration-Guide)”
   • [claimed-docs] “https://github.com/mrdoob/three.js/wiki/Migration-Guide#185--186”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   proof ↗⚑ flag

Agent editor

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

   weight 3 · round to Unity
   Unity✓fullprobed8/10

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

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

   proof ↗⚑ flag

   three.js~partialprobed4/10

   Three.js's core JS API lets an agent create scenes, nodes, meshes, and materials and edit properties programmatically (documented in llms.txt for LLM consumption), but this is just using the library — there's no evidence of a documented scripting/automation interface for the standalone three.js editor app itself, nor any 'trigger build' concept or API. Missing for 10: documented editor automation/scripting API, evidence of programmatic control of the editor UI, and any build/export trigger mechanism.

   • [claimed-docs] “three.js editor”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [github] “This code creates a scene, a camera, and a geometric cube, and it adds the cube to the scene. It then creates a `WebGL` renderer for the sce…”
   • [claimed-docs] “[docs](manual/#en/creating-a-scene) [examples](examples/#webgl_animation_keyframes)”

   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 three.js
   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

   three.js~partialprobed6/10

   Three.js is hugely popular (12M weekly npm downloads) with abundant public examples and even a dedicated llms.txt/llms-full.txt tailored for LLM consumption, which strongly favors first-try LLM code generation. However, community evidence and the docs themselves point to real friction: frequent breaking API changes requiring per-version migration guides, explicit warnings to use 'CORRECT - modern pattern' import maps (implying old LLM-trained patterns break), and hands-on reports that seemingly simple tasks (loading a model) were unexpectedly hard, undermining 'mostly works on the first try.' Missing for 10: independent benchmark/report of LLM-generated three.js code success rate, and stronger evidence that API stability (not just doc richness) prevents version-mismatch failures.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [claimed-docs] “CORRECT - modern pattern (always use latest version): html <script type="importmap">”
   • [claimed-docs] “[Migration Guide](/mrdoob/three.js/wiki/Migration-Guide)”
   • [community] “I've tried to follow three.js's own tutorials, and slip into coma every time. These are a vast improvement!”
   • [community] “I was super excited to use Three.js and thought it would be easy to do what I wanted. What I wanted to do was load a simple .obj model and d…”
   • [community] “there are some function signatures that don't match what's in the code using @types/three, and mrdoob does not want to maintain this. This g…”

   proof ↗⚑ flag

Copilot

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

   weight 2 · round to Unity
   Unity~partialprobed6/10

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

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

   proof ↗⚑ flag

   three.js—none0/10

   Evidence shows only LLM-friendly documentation (llms.txt) and no in-engine AI assistant, chat copilot, or code-generation assistant feature; probe explicitly notes no MCP server or agent integration exists, official or community.

   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”

   proof ↗⚑ flag

Formats

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

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

   three.js~partialcommunity4/10

   Only GLTFLoader is explicitly evidenced as a documented import path; there is no mention of FBX or USD loaders in the evidence pack, and a community report describes friction loading even a simple OBJ model, undercutting the 'imports cleanly' framing. Missing for 10: FBXLoader/USDLoader documentation or examples, first-party guidance on interchange-format fidelity, and independent confirmation that glTF/FBX/USD assets import without manual fixes.

   • [claimed-docs] “[GLTFLoader](https://threejs.org/docs/#examples/en/loaders/GLTFLoader)”
   • [community] “I was super excited to use Three.js and thought it would be easy to do what I wanted. What I wanted to do was load a simple .obj model and d…”

   proof ↗⚑ flag

Import

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

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

   three.js—none0/10

   three.js is a rendering library with a GLTFLoader and asset loaders, but there is no evidence of automatable asset-import pipelines, import hooks, presets, or scripted batch-processing of incoming assets — everything in the evidence pack concerns runtime rendering APIs, TSL/WebGPU, and manual loader usage rather than pipeline automation.

   • [claimed-docs] “[GLTFLoader](https://threejs.org/docs/#examples/en/loaders/GLTFLoader)”
   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”

   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

   three.js—none0/10

   Evidence only shows three.js's own built-in addons (GLTFLoader, OrbitControls, editor, devtools) and npm package popularity, not a third-party asset store or plugin marketplace comparable to Unity/Unreal ecosystems; community commentary even notes basic model loading (.obj) was painful. missing for 10: any evidence of a dedicated asset store, marketplace, or curated third-party plugin ecosystem for game assets/tools.

   • [claimed-docs] “[GLTFLoader](https://threejs.org/docs/#examples/en/loaders/GLTFLoader)”
   • [claimed-docs] “[OrbitControls](https://threejs.org/docs/#examples/en/controls/OrbitControls) - [TransformControls](https://threejs.org/docs/#examples/en/co…”
   • [claimed-docs] “three.js editor”
   • [claimed-docs] “[devtools](https://chromewebstore.google.com/detail/threejs-devtools/jechbjkglifdaldbdbigibihfaclnkbo)”
   • [community] “I was super excited to use Three.js and thought it would be easy to do what I wanted. What I wanted to do was load a simple .obj model and d…”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   proof ↗⚑ flag

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

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

   three.js—none0/10

   No evidence describes batch/bulk APIs (e.g., instancing, scene-graph batch edits) or automation tooling for operating on many items at once; the evidence pack only covers renderer setup, TSL, loaders, and controls.

   ⚑ 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

   three.js—none0/10

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

   ⚑ flag

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

   weight 1 · round drawn
   Unity—none0/10

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

   ⚑ flag

   three.js—none0/10

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

   ⚑ flag

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

   three.js—none0/10

   The evidence pack shows three.js is positioned and documented purely as a 3D graphics library (WebGL/WebGPU renderers, TSL shaders, GLTFLoader, OrbitControls) with no mention of sprites, tilemaps, or 2D physics as first-class citizens; 2D is at best an afterthought achievable via workarounds, consistent with community comments about needing workarounds for things it wasn't built for.

   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”
   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”
   • [claimed-docs] “**Use WebGPURenderer** when you need: - Custom shaders/materials using TSL (Three.js Shading Language) - Compute shaders - Advanced node-bas…”
   • [community] “Three.js is insane, in a good way. Great abstraction of WebGL, very user friendly, and surprisingly few things that it can't do, as long as …”

   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

   three.js—none0/10

   No evidence of a built-in profiler, ECS, job system, or GPU/CPU instancing tooling in the pack — only renderer setup, TSL/WebGPU shading, loaders, and controls are documented. Three.js is a rendering library, not a full engine, so profiling and data-oriented scaling primitives fall to external tools (Chrome DevTools extension is mentioned but that's a generic browser profiler, not a real-time engine profiler), and no ECS/jobs/instancing capability is cited.

   • [claimed-docs] “[devtools](https://chromewebstore.google.com/detail/threejs-devtools/jechbjkglifdaldbdbigibihfaclnkbo)”

   proof ↗⚑ flag

Physics

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

   weight 2 · round drawn
   Unity—none0/10

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

   ⚑ flag

   three.js—none0/10

   three.js is a rendering library — no evidence of any built-in physics engine (rigid bodies, collisions, raycasts as physics) shipped out of the box; evidence only covers rendering (WebGL/WebGPU), loaders, and controls. Raycaster exists in three.js for picking but no physics/collision system is documented, and physics is a well-known gap requiring third-party libraries like Cannon.js or Ammo.js.

   ⚑ 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

   three.js~partialcommunity4/10

   Evidence confirms a modern rendering pipeline (WebGLRenderer/WebGPURenderer, antialiasing, and node-based 'MeshStandardNodeMaterial' implying PBR-style materials) but the pack contains no explicit documentation of shadow mapping, global illumination/baked lighting, or a post-processing pipeline — a community comment even asks uncertainly whether lightmaps are possible. missing for 10: explicit shadow-mapping docs, GI/lightmap baking evidence, post-processing/effects pipeline documentation, independent confirmation of PBR material fidelity.

   • [claimed-docs] “When using TSL, use node-based materials: - MeshBasicNodeMaterial - MeshStandardNodeMaterial”
   • [claimed-docs] “Use WebGPURenderer when you need: - Custom shaders/materials using TSL (Three.js Shading Language) - Compute shaders - Advanced node-based m…”
   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [community] “That is called aliasing. Three.js defaults to it, but you can turn antialiasing on by passing the option to the WebGLRenderer.”
   • [community] “Can you actually generate lightmaps with three.js? I did a lot with it years ago. Really nice abstraction library.”

   proof ↗⚑ flag

Collaboration

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

   weight 2 · round to Unity
   Unity~partialclaimed2/10

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

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

   proof ↗⚑ flag

   three.js—none0/10

   three.js is a rendering library/API, not a scene-authoring tool with a project file format; evidence shows only a code-based API, an optional visual editor, and no mention of diffable scene formats, merge tooling, or multi-user collaboration features. This axis applies to engines/authoring tools generally, but nothing in the evidence indicates three.js ships mergeable/diffable project files or built-in collaboration.

   • [claimed-docs] “three.js editor”
   • [github] “This code creates a scene, a camera, and a geometric cube, and it adds the cube to the scene. It then creates a `WebGL` renderer for the sce…”
   • [claimed-docs] “[docs](manual/#en/creating-a-scene) [examples](examples/#webgl_animation_keyframes)”

   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

   three.js~partialclaimed3/10

   three.js ships a browser-based editor (threejs.org/editor) and devtools/TransformControls, but evidence only names the editor's existence with no documentation of an inspector, prefab system, or scene-composition workflow, and the library's primary workflow is code-first (constructing scenes via API) rather than a visual editor. Missing for 10: documented inspector UI, prefab/asset composition workflow, evidence the editor is treated as the primary level-building tool rather than a supplementary demo tool.

   • [claimed-docs] “three.js editor”
   • [claimed-docs] “[OrbitControls](https://threejs.org/docs/#examples/en/controls/OrbitControls) - [TransformControls](https://threejs.org/docs/#examples/en/co…”
   • [claimed-docs] “[devtools](https://chromewebstore.google.com/detail/threejs-devtools/jechbjkglifdaldbdbigibihfaclnkbo)”

   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

   three.js—none0/10

   Evidence confirms three.js ships an editor (threejs.org/editor) and a devtools browser extension, but nothing in the pack describes any plugin API, scripting console, or extension mechanism for programmatically automating the editor itself — the docs excerpts focus on the library API (TSL, renderers, loaders, controls), not editor extensibility.

   • [claimed-docs] “three.js editor”
   • [claimed-docs] “[devtools](https://chromewebstore.google.com/detail/threejs-devtools/jechbjkglifdaldbdbigibihfaclnkbo)”

   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

   three.js—none0/10

   Evidence shows three.js is a code-first WebGL/WebGPU library installed via npm/git and used with standard `WebGLRenderer` setup, but nothing documents a CLI or automated pipeline for building/exporting a 'project' headlessly in CI (no headless rendering support, no export tooling, no CI recipes) — the only editor mentioned (threejs.org/editor) is a browser GUI requiring human interaction. missing for 10: any documented headless rendering approach (e.g. headless-gl/Node canvas), a CLI build/export command, and CI pipeline examples.

   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [github] “git clone --depth=1 https://github.com/mrdoob/three.js.git”
   • [claimed-docs] “three.js editor”
   • [github] “This code creates a scene, a camera, and a geometric cube, and it adds the cube to the scene. It then creates a `WebGL` renderer for the sce…”

   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

   three.js—none0/10

   three.js is fundamentally a browser-based WebGL/WebGPU rendering library requiring a canvas/GPU context; the evidence pack shows no headless/server-runtime build, no dedicated-server mode, and no mention of running game logic without rendering on Node.js servers. missing for 10: any headless rendering context (e.g. node-canvas/gl bindings), a documented server-runtime build, or dedicated-server examples.

   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”
   • [probe] “PROBE runtime (recorded 2026-09-15): threejs.org publishes llms.txt at the site root pointing to a docs llms.txt that carries a literal '## …”

   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

   three.js—none0/10

   No evidence in the pack addresses headless testing, CI integration, or running WebGLRenderer/WebGPURenderer without a browser context (e.g. via node-canvas, jsdom, or headless GL). All evidence covers rendering setup, docs, and community sentiment, none of it about automated/headless test execution.

   ⚑ 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

   three.js—none0/10

   No evidence of a foundation, published finances, or public roadmap; three.js governance appears to be maintainer-driven (mrdoob) via GitHub releases/migration guides with no financial transparency artifacts in the pack.

   ⚑ 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 three.js
   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

   three.js✓fullprobed9/10

   npm registry confirms three.js is MIT licensed, a permissive license with no royalties or per-install fees, verified directly from the package registry. Missing for 10: no explicit first-party licensing FAQ or legal statement addressing commercial game royalties specifically, relying instead on the generic MIT registry classification.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   proof ↗⚑ flag

Source

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

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

   three.js✓fullprobed9/10

   three.js is open-source (MIT license per npm registry) with full source hosted on GitHub, clonable and directly modifiable, and community evidence confirms active engagement with the codebase (e.g., @ts-ignore workarounds, discussion of internals like antialiasing defaults). Missing for 10: no explicit first-party statement encouraging source modification as a supported workflow, and no case study of a game dev forking/patching the engine for a shipped title.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”
   • [github] “git clone --depth=1 https://github.com/mrdoob/three.js.git”
   • [community] “there are some function signatures that don't match what's in the code using @types/three, and mrdoob does not want to maintain this. This g…”
   • [community] “That is called aliasing. Three.js defaults to it, but you can turn antialiasing on by passing the option to the WebGLRenderer.”

   proof ↗⚑ flag

Trust

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

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

   three.js~partialprobed5/10

   three.js is MIT-licensed, verified from the npm registry, which is a free, permissive open-source license with no pricing terms to retroactively change — this structurally supports licensing stability. However, there is no explicit evidence pack documentation of license history, versioning of terms, or any studio commentary confirming a track record of stability over time. Missing for 10: explicit license-history documentation, third-party confirmation of no relicensing/repricing events, and studio-lead testimonials on licensing trust.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   proof ↗⚑ flag

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

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

   three.js—none0/10

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

   ⚑ flag

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

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

   three.js—none0/10

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

   ⚑ flag

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

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

   three.js✓fullprobed9/10

   three.js source is hosted publicly on GitHub (mrdoob/three.js) and distributed via npm under the MIT license, verified directly from the npm registry; the repo is clonable and openly browsable. missing for 10: no explicit license file text quoted in the evidence pack, only registry-confirmed MIT license metadata.

   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [github] “git clone --depth=1 https://github.com/mrdoob/three.js.git”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

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

   three.js✓fullprobed9/10

   three.js is an open-source (MIT) client-side library distributed via npm/GitHub that can be cloned, built, and self-hosted entirely without any vendor service, as shown by the git clone instructions and npm registry data. missing for 10: no explicit first-party 'self-hosting guide' doc beyond generic clone/build instructions, and no independent case study of a fully self-hosted deployment.

   • [github] “git clone --depth=1 https://github.com/mrdoob/three.js.git”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”
   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”

   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

   three.js—none0/10

   The evidence pack shows three.js is a browser-based WebGL/WebGPU rendering library with no documentation of a build/export pipeline to native desktop, mobile, or console targets — no mention of Electron/Cordova wrapping, console SDK partnerships, or platform-specific packaging tools. While the axis is fair to ask of any 3D technology a studio might adopt, there is no evidence three.js provides or facilitates such multi-platform export beyond running inside a web browser.

   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://threejs.org/llms.txt # Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphi…”

   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 three.js
   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

   three.js✓fullprobed8/10

   three.js runs in-browser via WebGLRenderer (widely used, huge npm install base) and has a credible, actively developed WebGPU story through WebGPURenderer plus TSL shaders that target both WebGL and WebGPU backends, with SVG/CSS3D as lighter addons keeping core payload lean. Community confirms it's a solid abstraction over WebGL, though payload/performance specifics for WebGPU maturity aren't independently benchmarked in evidence. missing for 10: independent bundle-size/payload benchmarks, and hands-on confirmation of WebGPU production readiness beyond docs claims.

   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [github] “The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.”
   • [claimed-docs] “**Use WebGPURenderer** when you need: - Custom shaders/materials using TSL (Three.js Shading Language) - Compute shaders - Advanced node-bas…”
   • [claimed-docs] “TSL benefits: - Works with both WebGL and WebGPU backends - No string manipulation or onBeforeCompile hacks”
   • [community] “Three.js is insane, in a good way. Great abstraction of WebGL, very user friendly, and surprisingly few things that it can't do, as long as …”
   • [community] “THREE.js adds a nice layer of abstraction atop that metal [WebGL].”
   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”

   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 three.js
   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

   three.js✓fullprobed9/10

   three.js is published on npm (12M+ weekly downloads, MIT license per registry probe) and is widely used as an ES module import (importmap pattern shown in docs), consistent with standard bundler/tree-shaking workflows; community feedback confirms TypeScript compatibility and typical dependency usage patterns. Missing for 10: no explicit first-party documentation or evidence specifically confirming tree-shaking behavior/bundle-size optimization guidance.

   • [probe] “PROBE runtime (recorded 2026-09-15): `npm view three version` → 0.186.0, and the public npm downloads API reports 12,206,532 weekly download…”
   • [claimed-docs] “CORRECT - modern pattern (always use latest version): html <script type="importmap">”
   • [community] “Btw three.js works flawlessly with Typescript too in case anyone is interested.”
   • [community] “there are some function signatures that don't match what's in the code using @types/three, and mrdoob does not want to maintain this. This g…”
   • [community] “THREE.js adds a nice layer of abstraction atop that metal [WebGL].”

   proof ↗⚑ flag

Iteration

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

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

   three.js—none0/10

   three.js is a rendering library, not a game engine or dev environment with a build/watch pipeline; no evidence in the pack of any hot-reload, live-reload, or fast edit-run tooling shipped by the project itself (only unrelated docs, editor mentions, and API references).

   ⚑ 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 three.js
   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

   three.js✓fullcommunity7/10

   Three.js is a plain JavaScript/TypeScript library, so the 'scripting language' is JS itself, giving full, direct access to the entire engine API with no separate scripting sandbox or restricted binding layer (threejs-gh-1, threejs-gh-4). Debugging is supported via standard browser devtools plus a dedicated official Chrome three.js DevTools extension (threejs-docs-8), and TypeScript works well though community reports note occasional @types/three signature mismatches requiring ts-ignore (threejs-comm-4, threejs-comm-5). Missing for 10: deeper first-party documentation of the debugger extension's capabilities and stronger independent corroboration of TypeScript API completeness.

   • [github] “const renderer = new THREE.WebGLRenderer( { antialias: true } ); renderer.setSize( width, height );”
   • [github] “This code creates a scene, a camera, and a geometric cube, and it adds the cube to the scene. It then creates a `WebGL` renderer for the sce…”
   • [claimed-docs] “[devtools](https://chromewebstore.google.com/detail/threejs-devtools/jechbjkglifdaldbdbigibihfaclnkbo)”
   • [community] “Btw three.js works flawlessly with Typescript too in case anyone is interested.”
   • [community] “there are some function signatures that don't match what's in the code using @types/three, and mrdoob does not want to maintain this. This g…”

   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

   three.js—none0/10

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

   ⚑ flag