Skip to content
Back to search

build-world

Build interactive 3D worlds with high-quality assets from Thrixel and your AI agent of choice.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/thrixel/build-world with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/thrixel/build-world'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/thrixel--build-world/badge.svg)](/listings/thrixel--build-world)

HTML

<a href="/listings/thrixel--build-world"><img src="/api/listings/thrixel--build-world/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Steps 1 and 2 are once per machine. After that, a new game is just step 3.

> Using [Codex](https://thrixel.com/docs/build-world#codex) or > [Gemini CLI](https://thrixel.com/docs/build-world#gemini-cli) instead? Each one > installs Thrixel its own way - the > [installation page](https://thrixel.com/docs/build-world) has the steps for both.

1. Install Claude Code and uv

claude --version
uv --version

**Both print a version? Skip to step 2.**

<details> <summary><b>Not installed? Install commands here</b></summary>

**macOS, Linux, WSL**

curl -fsSL https://claude.ai/install.sh | bash    # the agent that writes your game
curl -LsSf https://astral.sh/uv/install.sh | sh   # runs the Thrixel connector

**Windows PowerShell**

irm https://claude.ai/install.ps1 | iex
irm https://astral.sh/uv/install.ps1 | iex

⚠️ **NOW OPEN A NEW TERMINAL**, then re-run the check above. Skipping this is the number one cause of `command not found`.

</details>

2. Connect Thrixel with [Claude Code Plugins](https://code.claude.com/docs/en/plugins)

Same on every platform:

# 1. Sign up and log in. Opens a page with a code, click Approve. The only manual step here.
uvx thrixel-mcp@latest login

# 2. One plugin carries both the skill and the Thrixel connector, for every project.
claude plugin marketplace add thrixel/build-world
claude plugin install thrixel@thrixel

Confirm both pieces landed:

claude plugin list     # thrixel@thrixel -> enabled
claude mcp list        # plugin:thrixel:thrixel -> Connected

**Both lines look right? You are done. Go to step 3.**

**Turn on updates (once).** Updates are off by default. In Claude Code:

1. Type `/plugin` 2. **Marketplaces** > **thrixel** 3. **Enable auto-update**

(Or update manually anytime: `/plugin update thrixel@thrixel`. Skipped this? No problem, the agent tells you when a newer version is out.)

<details> <summary><b>Installed manually before? Remove the old copies</b></summary>

The plugin includes both pieces, so your old install is now a duplicate. Remove it once.

<details open> <summary><b>macOS, Linux, WSL</b></summary>

claude mcp remove thrixel
rm -rf ~/.claude/skills/build-world ~/.claude/skills/goal-to-game ~/.claude/skills/thrixel

</details>

<details> <summary><b>Windows PowerShell</b></summary>

claude mcp remove thrixel
Remove-Item -Recurse -Force "$HOME\.claude\skills\build-world","$HOME\.claude\skills\goal-to-game","$HOME\.claude\skills\thrixel"

</details>

</details>

3. Ask for a game

# Run this wherever you keep projects. Claude makes the project folder itself.
claude --permission-mode auto

**Into Claude Code** (not the terminal), start the line with **`/thrixel:build-world`**, then describe the game and name the engine (three.js, Roblox, Unity, or Unreal):

/thrixel:build-world build a submarine exploration game in three.js set in a bright, vibrant tropical sea with coral and fish

> [!TIP] > Type `/thr` and Claude completes **`/thrixel:build-world`** for you, so you never type it in > full. If the completion does not appear, the skill is not installed - go back to step 2.

> We recommend setting /model to Opus 5 or a more capable model, with effort set to high or above.

Claude checks your Thrixel account and starts building. Keep talking to it in plain English to change things.

<details> <summary><b>No plugin? Install the <a href="https://code.claude.com/docs/en/skills">skill</a> and the <a href="https://modelcontextprotocol.io">MCP connector</a> separately</b></summary>

Replaces steps 2 and 3 above. Same start command either way: `/thrixel:build-world`.

**2. Connect Thrixel**

<details open> <summary><b>macOS, Linux, WSL</b></summary>

# 1. Sign up and log in. Opens a page with a code, click Approve. The only manual step here.
uvx thrixel-mcp@latest login

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "thrixel",
  3. "description": "Official Thrixel plugin: AI-generated 3D game assets for your coding agent.",
  4. "owner": {
  5. "name": "Thrixel",
  6. "email": "support@thrixel.com",
  7. "url": "https://thrixel.com"
  8. },
  9. "plugins": [
  10. {
  11. "name": "thrixel",
  12. "source": "./",
  13. "description": "Build playable 3D games with AI-generated assets. Bundles the build-world skill and the Thrixel connector: generate, refine and texture game-ready .glb models, then build the game around them in Three.js, Unity, Unreal or Roblox."
  14. }
  15. ]
  16. }
README.md · README · 253 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Build World
  2. Build interactive 3D worlds with high-quality assets from [Thrixel](https://thrixel.com/) and your AI agent of choice.
  3. Claude Code (or your preferred agent) handles the logic, interactions, and scene setup. Thrixel generates, organizes, and manages the 3D assets. Save your coding agent tokens and time by using Thrixel to generate 3D assets faster and at higher quality than Claude Code.
  4. Build World currently supports **Three.js**, **Roblox**, **Unity**, and **Unreal Engine**. This page covers **Claude Code**, but the workflow works with other coding agents as well.
  5. > Build World was previously called Goal to Game. The name changed because the skill goes beyond games: it can build interactive experiences, simulations, educational experiences, virtual tourism and historical recreations, AR/VR experiences, and more.
  6. ## Thrixel inside the Gauntlet Loop
  7. Build World uses a [gauntlet loop](https://thrixel.com/learn/gauntlet-loop)-like iterative workflow for creating interactive 3D worlds. The agent calls Thrixel to generate and refine 3D assets inside the loop. The agent continuously builds, evaluates, and improves the world itself, including its gameplay, interactions, and assets. With Build World, you can [vibe out a game](https://thrixel.com/learn/vibe-gaming) or other interactive 3D experience from a single prompt, then keep refining it with follow-up prompts.
  8. <p align="center">
  9. <img src="https://raw.githubusercontent.com/ThatCharlieK/READMEAssets/main/Thrixel-1prompt-to-game-readme.gif" width="600"/>
  10. </p>
  11. ## Quick start
  12. Steps 1 and 2 are once per machine. After that, a new game is just step 3.
  13. > Using [Codex](https://thrixel.com/docs/build-world#codex) or
  14. > [Gemini CLI](https://thrixel.com/docs/build-world#gemini-cli) instead? Each one
  15. > installs Thrixel its own way - the
  16. > [installation page](https://thrixel.com/docs/build-world) has the steps for both.
  17. ### 1. Install Claude Code and uv
  18. ```bash
  19. claude --version
  20. uv --version
  21. ```
  22. **Both print a version? Skip to step 2.**
  23. <details>
  24. <summary><b>Not installed? Install commands here</b></summary>
  25. **macOS, Linux, WSL**
  26. ```bash
  27. curl -fsSL https://claude.ai/install.sh | bash # the agent that writes your game
  28. curl -LsSf https://astral.sh/uv/install.sh | sh # runs the Thrixel connector
  29. ```
  30. **Windows PowerShell**
  31. ```powershell
  32. irm https://claude.ai/install.ps1 | iex
  33. irm https://astral.sh/uv/install.ps1 | iex
  34. ```
  35. ⚠️ **NOW OPEN A NEW TERMINAL**, then re-run the check above. Skipping this is the number one cause
  36. of `command not found`.
  37. </details>
  38. ### 2. Connect Thrixel with [Claude Code Plugins](https://code.claude.com/docs/en/plugins)
  39. Same on every platform:
  40. ```bash
  41. # 1. Sign up and log in. Opens a page with a code, click Approve. The only manual step here.
  42. uvx thrixel-mcp@latest login
  43. # 2. One plugin carries both the skill and the Thrixel connector, for every project.
  44. claude plugin marketplace add thrixel/build-world
  45. claude plugin install thrixel@thrixel
  46. ```
  47. Confirm both pieces landed:
  48. ```bash
  49. claude plugin list # thrixel@thrixel -> enabled
  50. claude mcp list # plugin:thrixel:thrixel -> Connected
  51. ```
  52. **Both lines look right? You are done. Go to step 3.**
  53. **Turn on updates (once).** Updates are off by default. In Claude Code:
  54. 1. Type `/plugin`
  55. 2. **Marketplaces** > **thrixel**
  56. 3. **Enable auto-update**
  57. (Or update manually anytime: `/plugin update thrixel@thrixel`. Skipped this? No problem, the
  58. agent tells you when a newer version is out.)
  59. <details>
  60. <summary><b>Installed manually before? Remove the old copies</b></summary>
  61. The plugin includes both pieces, so your old install is now a duplicate. Remove it once.
  62. <details open>
  63. <summary><b>macOS, Linux, WSL</b></summary>
  64. ```bash
  65. claude mcp remove thrixel
  66. rm -rf ~/.claude/skills/build-world ~/.claude/skills/goal-to-game ~/.claude/skills/thrixel
  67. ```
  68. </details>
  69. <details>
  70. <summary><b>Windows PowerShell</b></summary>
  71. ```powershell
  72. claude mcp remove thrixel
  73. Remove-Item -Recurse -Force "$HOME\.claude\skills\build-world","$HOME\.claude\skills\goal-to-game","$HOME\.claude\skills\thrixel"
  74. ```
  75. </details>
  76. </details>
  77. ### 3. Ask for a game
  78. ```bash
  79. # Run this wherever you keep projects. Claude makes the project folder itself.
  80. claude --permission-mode auto
  81. ```
  82. **Into Claude Code** (not the terminal), start the line with **`/thrixel:build-world`**, then
  83. describe the game and name the engine (three.js, Roblox, Unity, or Unreal):
  84. ```text
  85. /thrixel:build-world build a submarine exploration game in three.js set in a bright, vibrant tropical sea with coral and fish
  86. ```
  87. > [!TIP]
  88. > Type `/thr` and Claude completes **`/thrixel:build-world`** for you, so you never type it in
  89. > full. If the completion does not appear, the skill is not installed - go back to step 2.
  90. > We recommend setting /model to Opus 5 or a more capable model, with effort set to high or above.
  91. Claude checks your Thrixel account and starts building. Keep talking to it in plain English to
  92. change things.
  93. <details>
  94. <summary><b>No plugin? Install the <a href="https://code.claude.com/docs/en/skills">skill</a> and the <a href="https://modelcontextprotocol.io">MCP connector</a> separately</b></summary>
  95. Replaces steps 2 and 3 above. Same start command either way: `/thrixel:build-world`.
  96. **2. Connect Thrixel**
  97. <details open>
  98. <summary><b>macOS, Linux, WSL</b></summary>
  99. ```bash
  100. # 1. Sign up and log in. Opens a page with a code, click Approve. The only manual step here.
  101. uvx thrixel-mcp@latest login
  102. # 2. Install the Thrixel connector. --scope user covers EVERY project, not just this folder.
  103. claude mcp add --scope user thrixel -- uvx thrixel-mcp@latest
  104. # 3. Install the skill. Clone, not download, so it can update itself later.
  105. git clone https://github.com/thrixel/build-world ~/.claude/skills/thrixel
  106. ```
  107. </details>
  108. <details>
  109. <summary><b>Windows PowerShell</b></summary>
  110. Same three commands. Only the path differs: `~` is not reliably expanded when PowerShell passes it
  111. to git, and a skill that lands anywhere else is invisible to Claude.
  112. ```powershell
  113. uvx thrixel-mcp@latest login
  114. claude mcp add --scope user thrixel -- uvx thrixel-mcp@latest
  115. git clone https://github.com/thrixel/build-world "$HOME\.claude\skills\thrixel"
  116. ```
  117. </details>
  118. Confirm both landed:
  119. ```bash
  120. claude mcp list # thrixel -> Connected
  121. ls ~/.claude/skills/ # thrixel listed
  122. ```
  123. If either is missing, Claude will build the game without Thrixel and never mention it.
  124. **Cloned before the rename?** `github.com/thrixel/goal-to-game` still redirects here, so an older
  125. clone keeps working and keeps updating itself. All it leaves behind is the old name, in your folder
  126. and in `git remote -v`. Point it at the current URL once:
  127. ```bash
  128. git -C ~/.claude/skills/thrixel remote set-url origin https://github.com/thrixel/build-world
  129. ```
  130. **3. Ask for a game**
  131. Identical to step 3 above, same command and all:
  132. ```text
  133. /thrixel:build-world build a submarine exploration game in three.js set in a bright, vibrant tropical sea with coral and fish
  134. ```
  135. </details>
  136. <details>
  137. <summary>Something went wrong</summary>
  138. **"command not found"** - **open a new terminal.** Fixes it almost every time. If a fresh terminal
  139. still fails, run `export PATH="$HOME/.local/bin:$PATH"` (PowerShell:
  140. `$env:Path = "$HOME\.local\bin;$env:Path"`).
  141. **Claude has no Thrixel tools** - check `claude mcp list` for `thrixel`. If missing, re-run the
  142. `claude mcp add` line, then restart Claude.
  143. **Claude says you need to sign in** - re-run `uvx thrixel-mcp@latest login` and click Approve. No
  144. restart needed, just tell Claude to continue.
  145. **"Out of cubes"** - cubes are Thrixel's generation credits. Claude shows you what is built, marks
  146. missing assets as labelled blocks, and asks how you want to continue.
  147. </details>
  148. ### 4. Publish and share
  149. When your world is ready, ask your coding agent to publish it. Build World handles the deployment and gives you a live, shareable link, with no separate hosting setup required.
  150. ```text
  151. Publish this world and give me a link I can share.
  152. ```
  153. You can continue refining the project after publishing and deploy the updated version whenever you are ready. You may also ask your agent to record an mp4 preview to share online. E.g.,
  154. ```text
  155. Create a recording of this in .mp4 format to help demonstrate the capabilities to others
  156. ```
  157. ## Working with Thrixel API
  158. Every asset generated through the Thrixel API is saved to your Thrixel workspace.
  159. **Manage and Edit**: Visit [Thrixel Web App](https://thrixel.com/create) to view, manage, and edit your assets. If you make changes in the web app, ask your coding agent to pull the updated versions back into your game.
  160. **Engine Agnostic**: Because your assets are managed in Thrixel rather than tied to one codebase, you can also reuse them across projects and engines. For example, you can prototype in Three.js and later ask your agent to rebuild the game in Unity or Roblox using the same asset library.
  161. **Parallel Processing**: Thrixel can manage and process jobs in parallel. Your coding agent can farm out parallel jobs to Thrixel while building out the logic of the game. Each [plan](https://thrixel.com/create/#upgrade) has a different concurrency limit.
  162. ## Usage and credits
  163. You can test this workflow using the free Thrixel Cubes included with your Starter account. However, building a full-scale game generally requires a wider variety of assets and rapid iteration that usually exceeds Starter limits. Upgrading to a [Paid Plan](https://thrixel.com/create/#upgrade) unlocks higher parallel job processing capacity and higher generation limits, allowing you to bring your most ambitious ideas to life. You can keep track of your remaining Cubes anytime in [Account Settings](https://thrixel.com/create/#settings/billing).
  164. ## About Thrixel
  165. Learn more about Thrixel at [thrixel.com](https://thrixel.com/).
skills/build-world/engines/threejs/lib/selftest.js · Bundled script · 100 lines · 1 finding marked
  1. /**
  2. * A 40-line assert harness for subsystem self-tests. No dependencies, runs in
  3. * node and in the browser.
  4. *
  5. * WHY IT EXISTS: a screenshot cannot show that a capsule tunnelled through a
  6. * wall, that a ragdoll is gaining energy, that a nav path is unreachable, that a
  7. * synthesised sound is silent or clipping, or that a generated mesh has NaN
  8. * vertices. Those are exactly the failures that a visual critic will report as
  9. * something else ("the enemy looks wrong") and send you hunting in the wrong
  10. * subsystem.
  11. *
  12. * The pattern that paid off in the reference project: every non-visual subsystem
  13. * ships a `selftest` that prints a TABLE of measured-vs-expected, runnable as
  14. * `node src/<system>/selftest.mjs`. Measured numbers, not assertions that pass
    • Note: Usual in code (tag names in paths and patterns): Contains a <system> block, a common wrapper for instructions hidden in a tool description
    • Line 14 on GitHub
  15. * silently — the table is the artifact you paste into a report, and a reviewer
  16. * can see a value drifting before it crosses a threshold.
  17. *
  18. * const t = suite('physics');
  19. * t.ok(hit !== null, 'ray hits the wall');
  20. * t.near(speed, 4.57, 0.12, 'walk top speed', 'm/s');
  21. * t.range(slide, 0.75, 0.95, 'slide duration', 's');
  22. * process.exit(t.report());
  23. */
  24. export function suite(name) {
  25. const rows = [];
  26. let failures = 0;
  27. const push = (pass, label, measured, expected, unit) => {
  28. rows.push({ pass, label, measured, expected, unit: unit ?? '' });
  29. if (!pass) failures++;
  30. return pass;
  31. };
  32. return {
  33. name,
  34. section(title) {
  35. rows.push({ section: title });
  36. },
  37. ok(cond, label, detail = '') {
  38. return push(!!cond, label, cond ? 'yes' : 'NO', detail || 'yes');
  39. },
  40. eq(got, want, label, unit) {
  41. return push(got === want, label, got, want, unit);
  42. },
  43. near(got, want, tol, label, unit) {
  44. return push(Number.isFinite(got) && Math.abs(got - want) <= tol, label, fmt(got), `${want} ±${tol}`, unit);
  45. },
  46. range(got, lo, hi, label, unit) {
  47. return push(Number.isFinite(got) && got >= lo && got <= hi, label, fmt(got), `${lo}..${hi}`, unit);
  48. },
  49. finite(arr, label) {
  50. let bad = 0;
  51. for (let i = 0; i < arr.length; i++) if (!Number.isFinite(arr[i])) bad++;
  52. return push(bad === 0, label, `${bad} non-finite`, '0 non-finite');
  53. },
  54. /** Report as a table. Returns the exit code: 0 = all pass. */
  55. report({ log = console.log } = {}) {
  56. const w = (s, n) => String(s).padEnd(n);
  57. log(`\n${name} — ${rows.filter((r) => r.pass === true).length}/${rows.filter((r) => 'pass' in r).length} pass`);
  58. log(w('TEST', 34) + w('MEASURED', 16) + w('EXPECTED', 18) + 'RESULT');
  59. for (const r of rows) {
  60. if (r.section) {
  61. log(`\n${r.section}`);
  62. continue;
  63. }
  64. log(w(r.label, 34) + w(r.measured + r.unit, 16) + w(r.expected + r.unit, 18) + (r.pass ? 'PASS' : 'FAIL'));
  65. }
  66. if (failures) log(`\n${failures} FAILURE${failures > 1 ? 'S' : ''}`);
  67. return failures ? 1 : 0;
  68. },
  69. get failures() {
  70. return failures;
  71. },
  72. rows,
  73. };
  74. }
  75. const fmt = (v) =>
  76. typeof v === 'number' ? (Math.abs(v) < 100 ? v.toFixed(3) : v.toFixed(1)) : String(v);
  77. /**
  78. * Statistics for measuring feel and cost. `p(0.99)` is the number that matters
  79. * for frame time; a mean or median hides exactly the stalls players notice.
  80. */
  81. export function stats(values) {
  82. const a = Float64Array.from(values).sort();
  83. const n = a.length;
  84. if (!n) return { n: 0 };
  85. let sum = 0;
  86. for (const v of a) sum += v;
  87. const p = (q) => a[Math.min(n - 1, Math.max(0, Math.floor(n * q)))];
  88. return {
  89. n,
  90. min: a[0],
  91. max: a[n - 1],
  92. mean: sum / n,
  93. p1: p(0.01), p50: p(0.5), p90: p(0.9), p95: p(0.95), p99: p(0.99),
  94. p: (q) => p(q),
  95. };
  96. }
skills/build-world/engines/threejs/templates/subsystem.js · Bundled script · 105 lines · 1 finding marked
  1. import * as THREE from 'three';
  2. import { scratch, Owned, disposeTree, compileMeshes, Pool } from '../lib/index.js';
  3. /** Module-scope scratch. Allocated once. Never inside a per-frame function. */
  4. const S = scratch();
  5. /**
  6. * <SYSTEM> — <one line: what it owns>.
    • Note: Usual in code (tag names in paths and patterns): Contains a <system> block, a common wrapper for instructions hidden in a tool description
    • Line 8 on GitHub
  7. *
  8. * Copy this file, delete what you do not need, and keep the parts that are
  9. * commented as contract. Every hook here exists because a tool depends on it.
  10. */
  11. export class TemplateSystem {
  12. /** Unique id. Others reach you with ctx.get('<id>') — never by import. */
  13. static id = 'template';
  14. /** Systems that must init() before you. Topo-sorted; order of add() is irrelevant. */
  15. static deps = ['render'];
  16. async init(ctx) {
  17. this.ctx = ctx;
  18. /** Everything disposable you create goes through this. */
  19. this.own = new Owned();
  20. /** Your OWN random stream, so your output does not depend on what another
  21. * subsystem consumed from the shared one. */
  22. this.rng = ctx.rng.fork();
  23. this.root = new THREE.Group();
  24. this.root.name = TemplateSystem.id;
  25. ctx.scene.add(this.root);
  26. const q = ctx.config.q;
  27. // Fixed-capacity pool sized from the budget. Never grows; counts rejections.
  28. this.things = new Pool(
  29. q.particleBudget,
  30. () => ({ alive: false, position: new THREE.Vector3() }),
  31. (t) => {
  32. t.alive = false;
  33. }
  34. );
  35. // Listen; never reach into another subsystem to ask what happened.
  36. ctx.events.on('example:event', (e) => this.onExample(e));
  37. }
  38. onExample(e) {
  39. const t = this.things.acquire();
  40. if (!t) return; // at budget — dropping is correct, growing is not
  41. t.alive = true;
  42. t.position.copy(e.position);
  43. }
  44. /** Deterministic simulation. 0..N times per frame. Do NOT read input edges here. */
  45. fixedUpdate(h, ctx) {}
  46. /** Once per frame. Animation, decisions, anything reading input edges. */
  47. update(dt, ctx) {
  48. // Animate off the engine clock. NEVER performance.now(). See PITFALLS A3.
  49. const t = ctx.time.elapsed;
  50. S.v0.set(Math.sin(t), 0, Math.cos(t)); // scratch, no allocation
  51. }
  52. /** After every update(), before render: anything that must see final transforms
  53. * (attachments, light-count stabilisation, instance buffer flushes). */
  54. lateUpdate(dt, ctx) {}
  55. resize(w, h, ctx) {}
  56. /**
  57. * CONTRACT: compile every material this subsystem can produce, WITHOUT spawning
  58. * gameplay objects, drawing a gameplay frame, or touching the clock or the RNG.
  59. * compileMeshes() binds a 1x1 render target first, which is what puts the right
  60. * colour space and tone mapping in the program cache key. See PITFALLS B3/B4.
  61. */
  62. async prewarmMaterials(ctx) {
  63. const meshes = [];
  64. this.root.traverse((o) => {
  65. if (o.isMesh) meshes.push(o);
  66. });
  67. return { ok: true, compiled: compileMeshes(ctx.get('render').renderer, meshes, ctx.scene, ctx.camera) };
  68. }
  69. /**
  70. * Debug hook for the shot list and the profiler. `kind === 'none'` must FULLY
  71. * clear — a looping effect that survives into the next shot produces phantom
  72. * regressions in the next review round (PITFALLS A6).
  73. *
  74. * `opts.grabFrame` is how many frames the harness pumps before the shutter; use
  75. * it to land a transient's peak on the captured frame. Re-seed the RNG so the
  76. * staged effect is identical regardless of what ran before it.
  77. */
  78. debugStage(kind, opts = {}) {
  79. this.rng.seed(0x51a6ed);
  80. if (kind === 'none' || !kind) {
  81. /* clear everything you staged */
  82. return { cleared: true };
  83. }
  84. return { staged: kind, peakAt: Math.max(4, Number(opts.grabFrame ?? 60) - 6) };
  85. }
  86. dispose() {
  87. disposeTree(this.root);
  88. this.root.parent?.remove(this.root);
  89. this.own.disposeAll();
  90. }
  91. }

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.