Godot Engine vs three.js

Agent access

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

   weight 2 · round to three.js
   Godot Engine—none0/10

   Explicit probes show no llms.txt (404 at docs.godotengine.org/llms.txt), no .md doc mirrors, and no agent-oriented docs endpoint; the only doc format is standard human-facing HTML documentation.

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

   Evidence explicitly shows no official Godot MCP server exists (GitHub org search for 'mcp' returns 0 results, no llms.txt, no official endpoint); only third-party community MCP projects exist. The axis applies since Godot could plausibly ship an official MCP integration for editor automation, but no such first-party offering is documented.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

   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 Godot Engine
   Godot Engine✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

   Godot exposes a documented, scriptable surface (command-line/headless mode, EditorScript for in-editor automation, full GDScript/C# class API, and a keyless JSON Asset Library API) that an agent could drive programmatically, per godot-docs-3/5/12/14 and godot-probe-rt-1/2. However this is a traditional engine API/CLI, not an AI-native interface: probes confirm no llms.txt, no OpenAPI spec, and no official MCP server (godot-probe-1/2/3, godot-probe-rt-3), leaving only third-party community MCP wrappers of uneven maintenance. Missing for 10: an official machine-readable API spec (OpenAPI/llms.txt) and a first-party MCP or agent-oriented interface layer.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “Godot is designed to be friendly to them, so here are the steps for working entirely from the command line.”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Godot installs keylessly from Homebrew (cask godot 4.7.2, '2D and 3D game engine') — one command to the…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the Godot Asset Library exposes a keyless JSON API — GET godotengine.org/asset-library/api/asset?godot_…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.godotengine.org/openapi.json, https://docs.godotengine.org/swagger.json, https://docs.g…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

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

   Godot ships official, well-documented SDKs/language bindings — GDScript, C# via .NET, and GDExtension/C++ — plus a command-line interface and a queryable Asset Library JSON API, all of which an AI-native developer could build against (godot-docs-1, godot-docs-2, godot-docs-8, godot-docs-3, godot-probe-rt-2). However, there is no AI/agent-specific SDK, no official MCP server, and no machine-readable docs (llms.txt/.md mirrors return 404), with only unofficial community MCP projects filling that gap. Missing for 10: an official AI-agent SDK or MCP server, machine-readable/llms.txt documentation, and first-party AI integration tooling.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [claimed-docs] “Keep your code modular with an object-oriented API using Godot's own GDScript, C#, C++, or bring your own using GDExtension.”
   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the Godot Asset Library exposes a keyless JSON API — GET godotengine.org/asset-library/api/asset?godot_…”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”

   proof ↗⚑ flag

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

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

   ⚑ flag

   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 Godot Engine
   Godot Engine~partialprobed3/10

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

   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 three.js
   Godot Engine—none0/10

   Evidence shows only conventional scripting (GDScript, C#), CLI tooling, and editor plugin APIs — none of which constitute natural-language command operation. No official MCP server or NL interface exists (GitHub search for org:godotengine mcp returns 0 results), and only unofficial third-party community MCP projects (godot-mcp, godot-ai) exist, which are not part of the product itself.

   • [claimed-docs] “Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirel…”
   • [probe] “official CLI documented at https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html”
   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

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

   Godot ships extensive static class/API reference docs (godot-docs-1–17) but none of the evidence shows an interactive reference with runnable/executable code examples (no REPL, playground, or in-browser code execution is mentioned), and probes confirm no llms.txt, no OpenAPI spec, and no .md-mirrored interactive docs.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.godotengine.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://docs.godotengine.org/en/stable/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.godotengine.org/openapi.json, https://docs.godotengine.org/swagger.json, https://docs.g…”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

   The evidence pack contains no documentation of a versioned API policy or deprecation schedule for Godot's scripting/engine APIs (GDScript, C#, GDExtension); community notes only mention version differences (3.5.2 LTS vs 4.0) informally, not a documented deprecation policy. Since engine APIs could plausibly have such policies, absence of evidence yields 'none' rather than 'na'.

   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”

   proof ↗⚑ flag

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

   Godot documents multiple genuine programmatic surfaces — GDScript/C# scripting, EditorScript for in-editor automation, EditorPlugin for extending the editor, and a full command-line interface supporting headless mode and export/build triggering — which together let a script or external process create scenes/nodes, edit properties, and build. However these are general-purpose developer APIs, not an agent-oriented interface, and there is no official MCP server or agent-facing wrapper (GitHub search found zero official MCP results, llms.txt 404s, only community MCP projects of varying activity). Missing for 10: an official/first-party agent-facing API or MCP server, and independent hands-on evidence of an agent actually driving the editor end-to-end via these interfaces.

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

   proof ↗⚑ flag

   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
   Godot Engine~partialcommunity4/10

   Godot's GDScript/C# APIs are extensively documented (godot-docs-1/2) and the engine has a large public codebase/asset library that could supply LLM training examples, but there is no direct evidence about LLM-generated code success rates, and community reports note documentation gaps in the past and major GDScript/API syntax breaks between Godot 3 and 4 (godot-comm-11, godot-comm-14, godot-comm-15) that would fragment what models have seen. missing for 10: direct evidence of LLM code-generation success, confirmation that version-specific API drift (3.x vs 4.x GDScript) doesn't cause mismatched generations, independent benchmarks of first-try correctness.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “C# is a high-level programming language developed by Microsoft. In Godot, it is implemented with the modern .NET runtime.”
   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”
   • [community] “gdscript is pretty awful. It's only python-like for someone who's never used python. No list comprehensions, no tuples... It's like Python 1…”
   • [community] “I have tried to use it something like 2 years ago and just gave up in front of the poorly documented custom scripting language they used.”

   proof ↗⚑ flag

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

   No evidence of any official AI assistant built into the Godot editor for generating scripts, answering API questions, or scaffolding scenes; the evidence pack only shows scripting languages, plugins, CLI tools, and asset import pipelines — plus explicit probes confirming no official MCP/AI integration exists and only unofficial community projects (e.g., godot-mcp, godot-ai) fill the gap.

   • [probe] “PROBE runtime negative (recorded 2026-09-15): godotengine.org serves no llms.txt (HTTP 404; docs.godotengine.org 404 as well) and docs pages…”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Godot Engine
   Godot Engine✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

   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 Godot Engine
   Godot Engine✓fullcommunity7/10

   First-party docs explicitly market Godot's 'dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes,' distinguishing 2D as first-class rather than a 3D afterthought, and the asset library segments 2D vs 3D tools, reinforcing separate 2D-focused workflows. Community threads corroborate Godot's strength and ease relative to competitors for indie/2D-style projects, though none specifically praise tilemaps or 2D physics. Missing for 10: explicit documentation/evidence on TileMap editor and 2D physics engine (Box2D-like) specifics, and independent hands-on confirmation of 2D-specific workflow quality.

   • [claimed-docs] “Make crisp and performant 2D games with Godot's dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes.”
   • [claimed-docs] “Godot Asset Library ... Category Any 2D Tools 3D Tools Shaders Materials Tools Scripts Misc Templates Projects Demos”
   • [claimed-docs] “Godot's Node and Scene system gives you both power and flexibility to create anything.”
   • [community] “I'm using it every day at work... Godot was just what I needed since I wanted a visual editor but still be able to code. The scripting langu…”

   proof ↗⚑ flag

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

   The evidence pack contains no mention of Godot's built-in profiler, ECS, job/threading system, or MultiMesh/instancing APIs for scaling heavy scenes; only a community note that hitting high framerates may require dropping to C++/GDExtension, which doesn't confirm profiling or data-oriented tooling. missing for 10: evidence of a real profiler UI, ECS support, job/threading system, and instancing APIs for scaling.

   • [community] “The other con will likely be around performance, it's passable at 90hz, but if you want to start hitting framerates like 144hz, the critical…”

   proof ↗⚑ flag

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

   The evidence pack contains no mention of Godot's physics system, rigid bodies, collision detection, or raycasting APIs — only general engine features like 2D rendering, node/scene system, scripting, and export tooling are cited. Absence of evidence for this applicable core-engine capability means it cannot be credited as full/partial.

   ⚑ flag

   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 three.js
   Godot Engine—none0/10

   The evidence pack documents Godot's 2D rendering engine explicitly (godot-docs-7) but contains no mention of a 3D renderer, PBR materials, global illumination/baked lighting, shadows, or post-processing pipeline anywhere in the docs, GitHub, or community citations.

   • [claimed-docs] “Make crisp and performant 2D games with Godot's dedicated 2D rendering engine with real 2D pixel coordinates and 2D nodes.”
   • [claimed-docs] “Godot's Node and Scene system gives you both power and flexibility to create anything.”

   proof ↗⚑ flag

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

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

   ⚑ flag

   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 Godot Engine
   Godot Engine✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Godot Engine
   Godot Engine~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 drawn
   Godot Engine✓fullcommunity9/10

   Godot is MIT-licensed, explicitly described as 'completely free and open source... no royalties, nothing' and 'free to use for any purpose,' with community corroboration noting no forced splash screen requirement unlike Unity. Missing for 10: no explicit discussion of edge cases like trademark/logo usage restrictions or third-party asset licensing nuances.

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

   proof ↗⚑ flag

   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 drawn
   Godot Engine✓fullcommunity9/10

   Godot is MIT-licensed open source, with full source available on GitHub, permissive rights to use/modify/redistribute per the license page, and an active core team accepting PRs/code reviews from contributors — directly enabling developers to read and modify engine internals when needed. missing for 10: no explicit evidence pack citation of the exact source-code repo browsing/build docs beyond compilation instructions link.

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

   proof ↗⚑ flag

   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 Godot Engine
   Godot Engine✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 to Godot Engine
   Godot Engine~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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 drawn
   Godot Engine✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   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 drawn
   Godot Engine✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 Godot Engine
   Godot Engine✓fullclaimed7/10

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

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

   proof ↗⚑ flag

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

   Evidence confirms Godot supports one-click export to Web platforms (godot-gh-1) and community reports web export working well for GDScript-based projects in the 3.x LTS line (godot-comm-11), but a community report specifically flags that C#/.NET export to web does not work (godot-comm-5), and there is no evidence at all in the pack addressing WebGPU support, payload size optimization, or a build pipeline story for it. Missing for 10: WebGPU backend documentation/evidence, payload-size guidance, and clarity on C# web-export limitations vs GDScript.

   • [github] “Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platfor…”
   • [community] “It works relatively well, and actually better than in Unity (which uses an older C# version), but unfortunately it does not work everywhere.…”
   • [community] “Godot 3.5.2 is still the LTS version and still exports just great for the web... I decided to switch from Godot 4.0 C# to Godot 3.5.2 with G…”

   proof ↗⚑ flag

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

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

   ⚑ flag

   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 to Godot Engine
   Godot Engine~partialclaimed4/10

   Evidence shows editor plugins can be built in GDScript without reloading the editor (godot-docs-4/13) and Godot's scene/node system supports live editing, implying reasonably fast iteration, but there is no direct documentation or community confirmation of hot-reloading running gameplay scripts or near-instant preview after a script change during play mode. missing for 10: explicit docs on script hot-reload during play, independent hands-on confirmation of edit-run loop speed for gameplay code, comparison benchmarks.

   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “It can be made entirely with GDScript and standard scenes, without even reloading the editor.”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [claimed-docs] “This is useful for adding custom in-editor functionality to Godot.”

   proof ↗⚑ flag

   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
   Godot Engine~partialcommunity6/10

   GDScript is documented as Godot's native, high-level, object-oriented, gradually-typed language that fully exposes the engine API (nodes/scenes, editor plugins, EditorScript), and community reports back this up as reasonably fast to learn and productive for people with programming experience. However, the evidence pack contains no explicit documentation of a GDScript-specific debugger (only C#'s Visual Studio debugging is called out), and some community feedback calls GDScript's ergonomics and documentation poor (comm-14, comm-15), creating real caveats rather than a clean full delivery. Missing for 10: explicit docs on the built-in GDScript debugger/breakpoints workflow, and stronger independent confirmation that GDScript is unambiguously productive for professional use.

   • [claimed-docs] “GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot.”
   • [claimed-docs] “Keep your code modular with an object-oriented API using Godot's own GDScript, C#, C++, or bring your own using GDExtension.”
   • [claimed-docs] “A plugin is a great way to extend the editor with useful tools. It can be made entirely with GDScript and standard scenes, without even relo…”
   • [claimed-docs] “Scripts extending this class and implementing its _run() method can be executed from the Script Editor's File > Run menu option (or by press…”
   • [community] “I'm using it every day at work... Godot was just what I needed since I wanted a visual editor but still be able to code. The scripting langu…”
   • [community] “gdscript is pretty awful. It's only python-like for someone who's never used python. No list comprehensions, no tuples... It's like Python 1…”
   • [community] “I have tried to use it something like 2 years ago and just gave up in front of the poorly documented custom scripting language they used.”
   • [community] “Godot 4 is using actual .NET instead of Mono, so you get all the tooling support that implies, including seamless debugging with Visual Stud…”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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