Unreal Engine vs three.js
three.js
three.js contributors (mrdoob)
Unreal Engine wins · 16–15 (16 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to three.jsUnreal Enginenone0/10A direct probe found no llms.txt on Epic's domains, and appending .md to docs URLs returns the HTML SPA shell rather than agent-readable markdown, meaning there is no mechanism to point an agent at machine-readable docs.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Unreal EngineDocs show real automation building blocks: command-line launch arguments (unreal-docs-7, unreal-docs-14), UAT commands for cooking/packaging/deploying (unreal-docs-16, unreal-docs-17), and Python editor scripting for automating asset tasks (unreal-docs-4), all of which are commonly used to run Unreal headlessly in CI pipelines. However, there is no explicit first-party 'headless mode' or CI-integration guide, and the probe notes Unreal's docs/repos are largely non-machine-readable (403s, no llms.txt, no official MCP), suggesting automation setup requires manual/expert configuration rather than a turnkey CI story. Missing for 10: dedicated headless-mode documentation, official CI/CD templates (e.g., GitHub Actions), and independent hands-on confirmation of CI pipelines running Unreal successfully.
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
three.jsnone0/10Three.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'.
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnUnreal Enginenone0/10Unreal Engine is a platform/tool (not itself an agent), so an official MCP server axis applies, but evidence shows no official Epic MCP server exists — a GitHub org search returns 0 results, and the most popular community MCP integration is unmaintained since 2025.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userUse an official CLI
weight 2 · round to Unreal EngineUnreal ships an official CLI surface: UnrealEditor.exe/UAT commands for cooking, packaging, deploying and running projects, plus documented command-line arguments for automation and testing, and Python editor scripting for scriptable workflows — all first-party and independently confirmed as keylessly fetchable per the probe. missing for 10: explicit AI-native framing or agent-oriented tooling around the CLI, and independent hands-on validation of using it in agentic workflows.
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userDrive the product through a documented public API
weight 3 · round drawnUnreal ships genuinely documented public APIs — a Python editor-scripting API for automating asset/editor tasks, a C++ gameplay API, and command-line/UAT automation flags — which a user or script can drive programmatically. However, the probe evidence shows these are not AI-native accessible: no official Epic MCP server, no llms.txt, docs served only as an HTML SPA (no .md fetch), and the GitHub source repo is EULA/account-gated returning 404 to unauthenticated API calls, with the leading community MCP abandoned since April 2025. Missing for 10: AI-agent-discoverable/machine-readable API docs, an official MCP or agent-facing interface, and keyless programmatic access to source/API metadata.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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 );”
ai-native userBuild against official SDKs
weight 2 · round drawnUnreal ships extensive official build surfaces — C++ APIs, Python editor-scripting API, Blueprint visual scripting, plugin SDK, and CLI/automation tooling — all documented on dev.epicgames.com, which functions as an official SDK for building games/tools. However, the probe evidence shows these are poorly suited for AI-native/agentic consumption: no official MCP server exists, GitHub source access is gated (404 without auth), main sites 403 non-browser clients, no llms.txt, and docs aren't served as fetchable markdown, undercutting AI-native usability of the SDK. Missing for 10: official MCP server or agent-friendly API, machine-readable/llms.txt documentation, keyless programmatic access to source and APIs.
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “Plugins are collections of code and data that developers can easily enable or disable within the Editor on a per-project basis.”
- [claimed-docs] “Access to the source code All platforms & features Forums and documentation on the Epic Developer Community”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnUnreal Enginenone0/10No evidence in the pack of Unreal Engine surfacing AI-generated insights or suggestions from project data; docs cover Blueprints, C++, Python scripting, plugins, and networking but nothing about analytics/AI-driven suggestions, and the probe notes the engine has no official MCP or AI-native tooling exposure.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Unreal EngineUnreal exposes Python editor scripting, commandlets, and UAT/command-line automation that can be scripted to run unattended (e.g., asset processing, cooking, packaging) which supports background automation, but nothing in the evidence describes an AI-native agent framework, scheduler, or official API/MCP for autonomous orchestration — and the probe explicitly notes no official Epic MCP and no machine-readable API, undermining AI-native automation setup. missing for 10: official AI-agent/automation orchestration layer, documented scheduling/trigger system for unattended runs, first-party API or MCP for AI agents to invoke automations.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnUnreal Enginenone0/10No evidence in the pack of any built-in AI assistant inside Unreal Editor that users can delegate tasks to; all documentation covers Blueprints, C++, Python scripting, plugins, and CLI tools, not an AI agent. The probe evidence even notes the lack of any official Epic AI/MCP integration.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “Plugins can add runtime gameplay functionality, modify built-in Engine features (or add new ones), create new file types, and extend the cap…”
ai-native userOperate the product with natural-language commands
weight 2 · round to three.jsUnreal Enginenone0/10Evidence shows only traditional scripting/programming interfaces (Blueprints, C++, Python, CLI args) with no natural-language command layer; the probe explicitly notes no official Epic MCP server, no llms.txt, and only an unmaintained community MCP project, meaning there's no documented way to operate Unreal via natural-language commands.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to three.jsUnreal Enginenone0/10The evidence shows only standard static documentation pages (C++, Blueprints, Python scripting, plugins) with no interactive API reference or runnable/executable code examples; the probe evidence explicitly notes Unreal's docs are not even machine-readable (no llms.txt, .md URLs return HTML shell) and there's no official API sandbox or live-code explorer mentioned anywhere.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
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…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to three.jsUnreal Enginenone0/10No evidence of an OpenAPI or similar machine-readable API spec; the probe evidence explicitly finds Unreal's docs and APIs are not machine-readable (no llms.txt, .md docs serve HTML shells, no official MCP/API spec), confirming absence rather than just lack of mention.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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 '## …”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnUnreal Enginenone0/10The 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.)
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to three.jsUnreal Enginenone0/10No evidence pack item documents API versioning conventions or a deprecation policy for Unreal's C++/Blueprint/Python APIs; the docs cover feature usage (Blueprints, C++, plugins, replication) but never mention deprecation macros, version compatibility guarantees, or a documented sunset policy. The probe evidence further shows Unreal's docs/API surface is poorly machine-readable, with no llms.txt or markdown API references that would expose such a policy.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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…”
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Agent editor
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 Unreal EngineUnreal documents a genuine scriptable interface — the Python Editor Scripting API for asset/property automation (docs-4, docs-12), Blueprints for visual node-based logic (docs-1), and CLI/UAT commands for cooking, packaging and triggering builds (docs-7,14,16,17) — which together let a script or agent create/edit content and trigger builds. However, the probe evidence shows no official Epic MCP server or AI-agent-oriented interface exists (0 results for org:EpicGames MCP repos), the most popular community MCP wrapper is unmaintained since 2025, and the docs themselves are not agent-friendly (SPA HTML, no llms.txt, .md suffix doesn't return markdown), undermining ease of programmatic/agentic access despite the underlying scripting capability being real. Missing for 10: official AI-agent/MCP integration, machine-readable documentation, evidence of an agent actually driving these interfaces end-to-end.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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)”
Codegen
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.jsUnreal Enginenone0/10No evidence directly addresses whether LLM-generated Unreal C++/Blueprint code works reliably on first try; the pack only shows general API docs exist and community comments about C++ complexity and blueprint limitations. The probe evidence even indicates docs are poorly machine-readable (403s, no llms.txt, gated source) which undercuts the 'abundant examples models have seen' premise but isn't a direct test of code-gen success either.
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [community] “My main problem with UE is C++, I don't want to even try to download files or read json in a blueprint.”
- [community] “blueprints are great for prototyping, but once you have too much complexity in a BP it can easily cascade inefficiencies to the point it bec…”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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…”
Copilot
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 drawnUnreal Enginenone0/10No evidence of an official in-engine AI assistant for generating scripts, answering API questions, or scaffolding scenes; the pack only covers Blueprints, C++, Python editor scripting, and plugins as manual tooling. The probe evidence explicitly notes no official Epic MCP/AI integration and that the most popular community MCP project is unmaintained.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
three.jsnone0/10Evidence 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…”
Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline
Getting content in — automated import, formats, marketplaces
Formats
technical artistStandard interchange formats — glTF, FBX, USD — import cleanly
weight 2 · round to three.jsUnreal Enginenone0/10The evidence pack contains no documentation, community, or probe citations addressing glTF, FBX, or USD import functionality in Unreal Engine; all provided docs cover Blueprints, C++, plugins, networking, and licensing instead. Since asset-pipeline import is a fair and applicable axis for a game engine, but no supporting evidence exists in this pack, the verdict is none.
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…”
Import
technical artistAsset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one
weight 2 · round to Unreal EngineDocs confirm Python scripting can automate asset-management tasks like LOD generation, and the Asset Manager gives programmatic control over asset discovery/loading, while Plugins can add new file-type handling — together these support scripted, non-interactive asset pipelines. However, there's no explicit documentation of dedicated 'import hooks' (e.g. post-import delegates/factories) or preset-based automated import workflows, and no independent/community confirmation that artists actually use this for hands-off batch import. missing for 10: explicit import-hook/factory API docs, named import-preset tooling, and third-party/community validation of automated import pipelines.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “provides a framework for managing Assets that can divide content into chunks that make sense in the context of your project”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [claimed-docs] “Plugins can add runtime gameplay functionality, modify built-in Engine features (or add new ones), create new file types, and extend the cap…”
- [claimed-docs] “Plugins are collections of code and data that developers can easily enable or disable within the Editor on a per-project basis.”
three.jsnone0/10three.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.”
Marketplace
game developerA large asset store or package ecosystem gives me ready-made models, tools, and plugins
weight 2 · round to Unreal EngineDocs show a genuine plugin and asset-management ecosystem (plugins can add gameplay features, new file types, editor extensions; Asset Manager for content organization) and community comment notes strong third-party program/community support, but there is no direct evidence in the pack describing the actual Marketplace/Fab asset store, its catalog size, or the quality of ready-made models — the probe entry only notes fab.com exists but is API-gated, not its content richness. Missing for 10: concrete marketplace/store catalog evidence, examples of ready-made models/tools available, and independent user reviews of the store experience.
- [claimed-docs] “Plugins can add runtime gameplay functionality, modify built-in Engine features (or add new ones), create new file types, and extend the cap…”
- [claimed-docs] “Plugins are collections of code and data that developers can easily enable or disable within the Editor on a per-project basis.”
- [claimed-docs] “provides a framework for managing Assets that can divide content into chunks that make sense in the context of your project”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [community] “Unreal was already the best engine purely on being easy to work with, support from third party programs and community, none of those things …”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
three.jsnone0/10Evidence 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…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Unreal EngineUnreal's Python editor-scripting API and Asset Manager are documented to automate time-consuming asset tasks (e.g., batch-generating LODs for Static Meshes) and manage large sets of Assets in chunks, which supports bulk operations across many items, and UAT/command-line tooling and cooking commands support batch build/deploy across multiple platforms/targets. However there is no concrete first-party example of an AI-native agent performing bulk edits, no official MCP server, and the probe evidence flags Unreal as the least machine-readable/agent-accessible of comparable products (gated APIs, 403s, no llms.txt), undercutting AI-native automation-depth claims. Missing for 10: worked examples of bulk operations orchestrated end-to-end, official AI/agent tooling or MCP integration, independent hands-on confirmation of scripted bulk workflows.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “provides a framework for managing Assets that can divide content into chunks that make sense in the context of your project”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Unreal EngineUnreal's Blueprint visual scripting and C++ delegate system explicitly support binding functions to be invoked automatically at a future time/event (dynamic delegates), and Blueprints expose event graphs for designers to wire up event-triggered logic without code. Community commentary confirms Blueprints are used for prototyping event-driven logic though complexity pushes users to C++. Missing for 10: explicit documentation of Event Dispatchers/Event Graph event-binding UI, and independent hands-on validation of rule-trigger reliability at scale.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “You can dynamically bind a delegate to a member function of an arbitrary object, calling the function on the object at a future time”
- [community] “blueprints are great for prototyping, but once you have too much complexity in a BP it can easily cascade inefficiencies to the point it bec…”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnUnreal Enginenone0/10The evidence pack covers Blueprints, C++, Python scripting, plugins, asset management, and cooking, but contains no mention of version control integration, change review/diffing, or rollback mechanisms for Blueprints, Python scripts, or other automations. This is a plausible axis for a dev engine (e.g., source control on Blueprints), but no supporting evidence exists.
Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine
The engine core — rendering, 2D, physics, performance at scale
2d
game developer2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought
weight 2 · round drawnUnreal Enginenone0/10The evidence pack contains no mention of sprites, tilemaps, Paper2D, or 2D physics support in Unreal Engine—only C++, Blueprints, plugins, networking, and licensing topics. Since a 3D-first engine could plausibly ship a first-class 2D workflow, this axis applies, but no evidence documents it, so the story is unsupported.
three.jsnone0/10The 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 …”
Performance
game developerProfile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy
weight 2 · round drawnUnreal Enginenone0/10The evidence pack contains no documentation or community evidence about Unreal Insights, stat/profiling commands, GPU profiling, or data-oriented paths like Mass Entity/ECS, job systems, or GPU instancing — only generic command-line-argument docs mentioning 'testing and optimizing' in passing. Profiling and data-oriented scaling are core, expected capabilities for a AAA game engine, so the axis applies, but nothing in the pack demonstrates a real profiler or ECS/jobs/instancing systems.
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
three.jsnone0/10No 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)”
Physics
game developerBuilt-in physics — rigid bodies, collisions, raycasts — works out of the box
weight 2 · round drawnUnreal Enginenone0/10The evidence pack contains no documentation, community reports, or probes specifically addressing Unreal's physics system (rigid bodies, collision detection, raycasting, Chaos/PhysX). Coverage is entirely about Blueprints, C++, plugins, asset management, networking, licensing, and community sentiment on cost/usability — none of which substantiates the built-in physics story.
three.jsnone0/10three.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.
Rendering
game developerThe engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing
weight 3 · round to Unreal EngineCommunity evidence confirms Unreal's renderer includes Lumen for real-time global illumination/reflections and general praise for lighting quality, supporting the GI/rendering claim, but the evidence pack lacks first-party documentation or hands-on confirmation of PBR material workflows, shadow systems, or the post-processing pipeline explicitly. missing for 10: explicit docs/evidence on PBR material editor, shadow mapping/ray-traced shadows, and post-process volume/effects stack.
- [community] “Lumen implements efficient Software Ray Tracing, allowing for global illumination and reflections to run on a wide range of video cards, whi…”
- [community] “For someone who's actually using UE4 as an artistic break for web dev, I thoroughly recommend it. It allows you to create great environments…”
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.”
Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling
The editor as a product — scene tools, extensibility, team workflows
Collaboration
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 drawnUnreal Enginenone0/10The evidence pack contains no mention of Unreal's scene/level file formats, diffability, source-control integration (e.g., Perforce/Git-LFS workflows), or any built-in multi-user collaboration tooling; it only covers Blueprints, C++, plugins, networking replication, and licensing. Missing for 10: any documentation or community evidence on .uasset/.umap format mergeability, text-based diffable formats, or built-in collaboration features like Multi-User Editing.
three.jsnone0/10three.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)”
Editor
technical artistA full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels
weight 3 · round to Unreal EngineUnreal's editor-centric workflow (Blueprints visual scripting, Editor extensions, Asset Manager, Level building/testing via UE Toolbar) is well documented as the primary way to construct levels and gameplay without programmer-only tools, and community comments (comm-3, comm-11, comm-16) corroborate that it's an actual GUI-driven editor experience artists use. missing for 10: explicit documentation naming 'viewport' and 'inspector' panels, and 'prefab' terminology (Unreal uses Blueprint/Actor classes instead) with independent hands-on confirmation of scene-composition workflow specifically for technical artists.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “Plugins can add runtime gameplay functionality, modify built-in Engine features (or add new ones), create new file types, and extend the cap…”
- [claimed-docs] “provides a framework for managing Assets that can divide content into chunks that make sense in the context of your project”
- [claimed-docs] “Use UE Toolbar to quickly test a part of your currently loaded Level for testing and debugging.”
- [community] “Unreal was already the best engine purely on being easy to work with, support from third party programs and community, none of those things …”
- [community] “What I hate about unity is the whole interface editor thing... Is this Unreal Engine more earth to earth when it comes to programming?”
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)”
Extensibility
game developerExtend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically
weight 3 · round to Unreal EngineDocs confirm multiple official extension paths: Python editor scripting for automating asset/editor tasks, Blueprints for designer-level scripting, C++ for deep gameplay/editor class extension, and a Plugins system explicitly designed to 'extend the capabilities of the Editor.' These are core, well-documented first-party mechanisms for programmatic scene/asset manipulation and editor customization. Missing for 10: independent hands-on corroboration specifically of the Python/editor-scripting API (community evidence mostly discusses C++/Blueprint complexity rather than editor automation), and no mention of newer scripting surfaces like the Editor Utility Widgets or Python API depth in third-party sources.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “Plugins can add runtime gameplay functionality, modify built-in Engine features (or add new ones), create new file types, and extend the cap…”
- [claimed-docs] “Plugins are collections of code and data that developers can easily enable or disable within the Editor on a per-project basis.”
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [community] “blueprints are great for prototyping, but once you have too much complexity in a BP it can easily cascade inefficiencies to the point it bec…”
three.jsnone0/10Evidence 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)”
Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation
The engine without a human — CLI builds, CI test runs, dedicated servers
Ci
game developerBuild and export the project from the command line, headless, in CI — no human clicking an editor
weight 3 · round to Unreal EngineOfficial docs give concrete CLI commands for headless building/cooking/packaging/deploying a project (UnrealEditor.exe -run=cook, and the build/cook/package/deploy/run automation command), plus a dedicated command-line-arguments reference for scripted/CI use, all without needing to open the editor UI. Missing for 10: independent third-party CI pipeline case study confirming it works end-to-end, and explicit mention of UAT/BuildCookRun tool name or exit-code/scripting integration details.
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
three.jsnone0/10Evidence 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…”
Server
game developerGame logic runs headless on servers — a dedicated-server or server-runtime build without rendering
weight 2 · round drawnUnreal Enginenone0/10The evidence pack covers general networking/replication (client-server sync), command-line arguments, and cooking/packaging, but nowhere mentions Unreal's dedicated-server build target, a headless/no-rendering server runtime, or how to produce a server-only executable. Without explicit documentation of a server-only build path, this axis is unsupported by the given evidence. Missing for 10: any mention of a 'Server' build target, -server or -nullrhi headless launch flags, or dedicated-server packaging instructions.
- [claimed-docs] “Replication is the name for the process of synchronizing data and procedure calls between clients and servers”
- [claimed-docs] “Replication is the name for the process of synchronizing data and procedure calls between clients and servers.”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
three.jsnone0/10three.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.
Testing
game developerTests run headlessly — unit and integration tests of game code execute in CI against the real engine
weight 2 · round drawnUnreal Enginenone0/10The evidence pack only shows generic command-line argument docs and a UE Toolbar mention for ad-hoc level testing/debugging; there is no evidence of Unreal's Automation System, Gauntlet, or any documented headless unit/integration test execution flow running the real engine in CI. Missing for 10: mention of the Automation Testing framework, -nullrhi/-unattended/-ExecCmds test invocation, CI integration examples, or independent reports of headless test runs against the real engine.
three.jsnone0/10No 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.
Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness
The terms you build on — licenses, royalties, source access, pricing stability
Governance
studio leadThe project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan against
weight 1 · round drawnUnreal Enginenone0/10Evidence covers licensing costs, royalty terms, and technical documentation, but nothing indicates a governing foundation, published financial statements, or a public roadmap for Unreal Engine — Epic Games remains a private, closed-governance company with only EULA/royalty terms disclosed (unreal-docs-10, unreal-comm-9, unreal-comm-13).
- [claimed-docs] “Access to the source code”
- [community] “For those who don't know what the deal is with Unreal Engine, there's no charge until you get the first million dollars in revenue. Then the…”
- [community] “It appears they've backed off on the royalties, too: originally, it was 5% of gross, and now it's 5% of gross after $3000 sales per quarter.”
License
studio leadThe license is permissive with no royalties or per-install fees — I keep what my game earns
weight 3 · round to three.jsUnreal Enginenone0/10Community evidence explicitly documents that Unreal charges a 5% royalty on gross revenue after the first $1M (or $3,000/quarter) — this is the opposite of 'no royalties, keep what you earn.' No evidence pack item supports a royalty-free/no-fee licensing model; instead multiple citations (comm-1, comm-9, comm-13, comm-2) confirm a royalty-based commercial license.
- [community] “UE offers everything free... Only way to pay to use Unreal Engine is to earn more than $1,000,000 USD which for most people means everything…”
- [community] “For those who don't know what the deal is with Unreal Engine, there's no charge until you get the first million dollars in revenue. Then the…”
- [community] “It appears they've backed off on the royalties, too: originally, it was 5% of gross, and now it's 5% of gross after $3000 sales per quarter.”
- [community] “i know games with $3 million dollar budgets that chose Unity over Unreal because with Unreal that would have cost them $150k whereas with Un…”
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…”
Source
game developerRead and modify the full engine source when I hit a wall
weight 2 · round to three.jsEpic's license page explicitly grants 'Access to the source code' and docs describe creating new Gameplay C++ classes that recompile directly into the Editor, and community comments corroborate 'source code included.' Missing for 10: independent hands-on account of actually patching core engine internals (not just gameplay classes), and the probe notes the source repo is EULA/GitHub-account gated rather than freely open, which adds friction to the 'when I hit a wall' scenario.
- [claimed-docs] “Access to the source code”
- [claimed-docs] “Access to the source code All platforms & features Forums and documentation on the Epic Developer Community”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [community] “Crytek has financial worries. Plus it's the most difficult to use, because it's almost all C++. Unity is very accessible thanks to C# script…”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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.”
Trust
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.jsUnreal Enginenone0/10The pack shows royalty terms changed over time (5% of gross → 5% after $3,000/quarter) but no evidence addresses whether such changes were ever applied retroactively to already-shipped titles or whether Epic has an explicit no-retroactive-repricing policy/track record. Missing for 10: documented policy or community confirmation that license terms are grandfathered for shipped games, evidence of any past retroactive-change controversy or its resolution.
- [community] “It appears they've backed off on the royalties, too: originally, it was 5% of gross, and now it's 5% of gross after $3000 sales per quarter.”
- [community] “For those who don't know what the deal is with Unreal Engine, there's no charge until you get the first million dollars in revenue. Then the…”
- [claimed-docs] “Access to the source code”
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…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Unreal EngineUnreal exposes substantial programmatic surfaces (Python editor scripting, C++ gameplay/engine API, Blueprints, command-line/UAT automation) that cover many editor and runtime tasks, but there is no documentation or evidence claiming full UI/API parity — some editor UI workflows (e.g. certain asset browser, viewport, or complex tooling operations) are not confirmed as scriptable, and the probe notes the engine is poorly machine-accessible overall (gated source repo, 403s on core domains, no official MCP, docs not served as markdown). missing for 10: an explicit statement/spec of full UI-API parity, evidence that every UI action has an API equivalent, and better machine-readable API discovery for AI agents.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnUnreal Enginenone0/10Evidence covers Blueprints, C++, plugins, source-code access, and asset management, but nothing addresses exporting a project's proprietary .uasset/.umap data into open interchange formats to allow a clean migration away from Unreal. The probe evidence even highlights poor machine-readable/open access to Epic's own ecosystem, reinforcing the lack of a data-portability story.
- [claimed-docs] “provides a framework for managing Assets that can divide content into chunks that make sense in the context of your project”
- [claimed-docs] “there may be cases where you want precise control over when and how Assets are discovered, loaded, and audited. For these cases, the Asset M…”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
ai-native userRead the product's source under an open license
weight 2 · round to three.jsUnreal Enginedisputedcontradicted3/10Epic's own licensing page claims 'access to the source code' (unreal-docs-10, unreal-docs-18), but this is EULA/account-gated rather than an open-license grant — the probe confirms the GitHub source repo returns 404 without an authenticated, linked Epic account and all first-party domains block non-browser access, meaning the source is not freely readable under an open license as an AI-native user would need. Missing for 10: no OSI-approved or otherwise open license governing the source, no keyless/anonymous access to the code, no llms.txt or machine-readable confirmation of licensing terms.
- [claimed-docs] “Access to the source code”
- [claimed-docs] “Access to the source code All platforms & features Forums and documentation on the Epic Developer Community”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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…”
ai-native userSelf-host the core product
weight 3 · round to three.jsUnreal ships as a locally-installed engine with source-code access (unreal-docs-10/18), so the core product is inherently self-hostable rather than SaaS-only. However, the probe evidence shows source access is EULA/account-gated (must link a GitHub account to Epic), the GitHub repo is not publicly discoverable via API, and there is no simple open self-hosting path comparable to fully open-source engines. Missing for 10: unrestricted/public source access, no account-gating requirement, first-party documentation framing self-hosting as an explicit feature.
- [claimed-docs] “Access to the source code”
- [claimed-docs] “Access to the source code All platforms & features Forums and documentation on the Epic Developer Community”
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
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.”
Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export
Shipping everywhere — desktop, mobile, console, browser payloads
Targets
studio leadOne project exports to desktop, mobile, and (directly or via partners) consoles
weight 3 · round to Unreal EngineDocs show a single project can be cooked/packaged/deployed to multiple target platforms via the cook/package pipeline (unreal-docs-16, unreal-docs-17) and tested across platforms via the toolbar (unreal-docs-9), and community mentions cross-platform export (e.g., HTML5) confirm this in practice (unreal-comm-14). However, the evidence pack contains no explicit documentation or independent confirmation of console export specifics (partner/licensee console SDK integration), so console support is inferred rather than directly evidenced. Missing for 10: explicit console-platform export/partner-program documentation, independent studio confirmation of a single project shipping to consoles.
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
- [claimed-docs] “Use UE Toolbar to quickly test a part of your currently loaded Level for testing and debugging.”
- [community] “For someone who's actually using UE4 as an artistic break for web dev, I thoroughly recommend it. It allows you to create great environments…”
three.jsnone0/10The 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…”
Web
web developerMy game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU story
weight 2 · round to three.jsUnreal Enginenone0/10The only evidence touching web export is a decade-old community comment noting 'UE4.7 can export to HTML5 too' (unreal-comm-14) — there is no current documentation, no mention of WebGL, no mention of WebGPU, and no discussion of browser payload size or a credible modern web-export pipeline. Given Unreal actually removed HTML5/WebGL export in later versions, this stale anecdote does not establish a current capability.
- [community] “For someone who's actually using UE4 as an artistic break for web dev, I thoroughly recommend it. It allows you to create great environments…”
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…”
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.jsUnreal Enginenone0/10The 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.)
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].”
Scripting — writing the game — languages, visual scripting, iteration speedScripting
Writing the game — languages, visual scripting, iteration speed
Iteration
game developerThe edit-run loop is fast — hot reload or near-instant preview after a script change
weight 2 · round to Unreal EngineDocs confirm Blueprints allow instant in-editor scripting changes without recompilation, and C++ changes are 'reflected in the Unreal Editor after compiling' via Visual Studio/XCode, indicating a hot-reload/live-coding workflow exists. However, no evidence quantifies compile/reload speed, mentions the dedicated 'Live Coding' feature explicitly, or provides independent hands-on confirmation that the loop is fast rather than just functional. Missing for 10: benchmark/timing evidence on hot reload speed, explicit mention of Live Coding feature, independent developer testimony on edit-run loop responsiveness.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
Language
game developerThe primary scripting language is productive and fully exposes the engine API, with a debugger behind it
weight 3 · round to three.jsDocs show C++ as the primary language with full engine API exposure (new Gameplay classes, delegates binding to arbitrary objects) and it compiles/reflects via Visual Studio/XCode, implying standard IDE debugger support, while Blueprints (the more 'scripting'-like option) explicitly trades off some API depth for accessibility (unreal-docs-1,2,3,11). Community evidence corroborates a productivity/API-completeness tension: Blueprints alone are 'not sufficient' for real scripting tasks and require C++ fallback, and multiple developers cite C++ as their 'main problem' with UE (unreal-comm-4, unreal-comm-7, unreal-comm-15). Missing for 10: no explicit documentation of an integrated scripting debugger workflow (only external Visual Studio/Xcode debugging is implied), and no first-party evidence that any single primary language achieves both full productivity and full API coverage without trade-offs.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [claimed-docs] “You can dynamically bind a delegate to a member function of an arbitrary object, calling the function on the object at a future time”
- [claimed-docs] “Creating new Gameplay classes in C++, and all changes will be reflected in the Unreal Editor after compiling with either Visual Studio or XC…”
- [community] “With no scripting support, adding content like vehicles is pretty much impossible. Blueprints are not sufficient for such a task. A few peop…”
- [community] “My main problem with UE is C++, I don't want to even try to download files or read json in a blueprint.”
- [community] “blueprints are great for prototyping, but once you have too much complexity in a BP it can easily cascade inefficiencies to the point it bec…”
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…”
Visual
technical artistBuild gameplay logic with visual scripting without writing code
weight 2 · round to Unreal EngineUnreal Enginedisputedcontradicted6/10Epic's docs confirm Blueprints let designers use most programmer-level tools without code (unreal-docs-1), and this is Unreal's flagship visual-scripting system for gameplay logic. However, hands-on community reports concretely contradict full no-code sufficiency: one dev states Blueprints were 'not sufficient' for adding content like vehicles and required C++ (unreal-comm-4), and another notes complex Blueprint graphs 'cascade inefficiencies' making C++ necessary at scale (unreal-comm-15), with a third citing C++ as the main pain point when trying to avoid it (unreal-comm-7). Missing for 10: independent case studies of large shipped games built purely in Blueprints without C++ fallback, and clearer scoping of what gameplay complexity Blueprints alone can handle.
- [claimed-docs] “provides the ability for designers to use virtually the full range of concepts and tools generally only available to programmers”
- [community] “With no scripting support, adding content like vehicles is pretty much impossible. Blueprints are not sufficient for such a task. A few peop…”
- [community] “blueprints are great for prototyping, but once you have too much complexity in a BP it can easily cascade inefficiencies to the point it bec…”
- [community] “My main problem with UE is C++, I don't want to even try to download files or read json in a blueprint.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableUnreal Enginenone0/10Unreal Engine is a platform/tool (not an agent), so the MCP-server axis fairly applies, but evidence shows no official Epic-maintained MCP server exists (GitHub search for `mcp org:EpicGames` returns 0 results) and the most popular community MCP integration is unmaintained since 2025, meaning there's no first-party way to plug MCP servers into Unreal for tool use.
- [probe] “PROBE runtime negative (recorded 2026-09-15): Unreal is the least machine-readable presence of the eight — api.github.com/repos/EpicGames/Un…”
three.jsn/athree.js is a 3D graphics library, not an agent or platform that consumes external tools via MCP; the evidence explicitly confirms no MCP server exists and coding agents just use the library directly through npm. This axis is a category error for a rendering library.
- [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 '## …”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · not comparableUnreal Enginenone0/10No evidence anywhere in the pack describes an API credential system, scoped tokens, or least-privilege access controls for AI agents interacting with Unreal Engine or its services; the docs cover Blueprints, C++, plugins, and CLI tools but not credential/permission management. Missing for 10: any mention of API keys/tokens, scoped or role-based access, or agent-specific credential issuance.
ai-native userSubscribe to events via webhooks
weight 2 · not comparableUnreal Enginen/aUnreal Engine is a game engine/development platform, not a SaaS/service with an event stream; webhook subscriptions for external event notification are not a fit axis for this product category.
game developerRun ML models inside the game — an official inference runtime for on-device model execution
weight 1 · not comparableUnreal Enginenone0/10The evidence pack contains no mention of an on-device ML inference runtime (e.g., NNE, ONNX Runtime integration) for Unreal Engine; documentation citations cover Blueprints, C++, Python scripting, plugins, networking, and packaging, but nothing about running ML models in-game. Since game engines can plausibly ship such runtimes, this axis applies, but no supporting evidence exists.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableUnreal Enginenone0/10Evidence shows Unreal has CLI automation, Python editor scripting, and UAT commands for one-off automation tasks (e.g. asset processing, cooking/packaging), but nothing about built-in scheduling of recurring jobs or workflows — that would require external tooling like Jenkins/cron, which isn't documented here.
- [claimed-docs] “Automate time-consuming Asset management tasks in the Unreal Editor, like generating Levels of Detail (LODs) for Static Meshes.”
- [claimed-docs] “command-line arguments can be an invaluable tool for testing and optimizing your project”
- [claimed-docs] “Command-line Arguments, also called Additional Launch Parameters, customize how the engine runs on startup.”
- [claimed-docs] “UnrealEditor.exe <GameName or uproject> -run=cook -targetplatform=<Plat1>+<Plat2>”
- [claimed-docs] “This command can cook content for a platform, package it up into a platform's native format for distribution, deploys it to the device, and …”
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableUnreal Enginen/aUnreal Engine is a locally-installed/self-hosted game engine, not a cloud SaaS that stores user data on the vendor's servers; data residency/region selection is not a meaningful axis for this product category. Evidence pack contains no mention of hosted data storage or region choice, consistent with this being a category error rather than a missing feature.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableUnreal Enginen/aUnreal Engine is a game engine/development tool, not an AI model provider or SaaS with a data-training policy; the evidence pack contains nothing about AI training data opt-outs and this axis is a category error for an engine product.
ai-native userControl data retention and deletion
weight 2 · not comparableUnreal Enginen/aUnreal Engine is a game engine/development tool, not a data-processing SaaS or AI service that collects user data on users' behalf; data retention/deletion controls are a category mismatch — this axis is designed for hosted services handling user data, not a locally-installed engine/SDK.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableUnreal Enginenone0/10No evidence in the pack addresses telemetry, analytics, or usage-tracking opt-out settings for Unreal Engine or the Editor; all docs and community items concern scripting, licensing, and pricing topics unrelated to privacy controls.