# GameCrew — Complete Reference (llms-full.txt) > GameCrew (`https://gamecrew.ai`) is an AI game development studio operated by GameCrew AI (a sole proprietorship, United States). Creators describe a game in plain English; GameCrew generates a structured pitch, moodboards, concept art, rigged 3D models, PBR materials, sound effects, and music, then writes, compiles, playtests, and verifies a real game project in Unity 6, Godot 4, Three.js, or Pulse. --- # How GameCrew Works > GameCrew is an autonomous game studio that turns plain-English direction into real Unity 6, Godot 4, Three.js, or Pulse projects, custom 3D art and sound, and browser-playable builds tested before you open them. - **Canonical URL:** https://gamecrew.ai/how-it-works ## Four stages grounded in real tools 1. **Pitch, look & gameplay direction (~2 min):** GameCrew drafts a structured pitch, offers visual moodboards and distinct gameplay takes, maps keyboard, gamepad, phone touch, and optional VR controls, and generates concept art. 2. **3D models, rigging & mastered audio:** Props and humanoid characters are generated in 3D, rigged and animated, paired with seamless PBR normal and roughness maps, sound effects, looping music, and open-licence CC0/CC BY library assets. 3. **Automated playtest, browser & VR verification:** Every version compiles in its engine, runs automated unit/edit and play-mode tests, boots its web build in headless Chrome, checks VR builds in an emulated WebXR headset, and captures screenshots. 4. **Share links, live tuning, MCP & full export:** Open instant share links on desktop, mobile, or headset; pin feedback notes onto screenshots; adjust gameplay sliders live at zero AI cost; connect an MCP coding assistant; or download the full project archive. ## Engine overview - **Unity 6 (Unity 6 · URP):** Universal Render Pipeline projects with C# gameplay scripts, physics, rigged humanoid FBX animation, custom shaders, downloadable Unity 6 project archives, standalone desktop players, WebGL builds and WebXR headset play. - **Godot 4 (Godot 4):** Clean .tscn scene trees and GDScript gameplay on the MIT-licensed Godot 4 engine, with fast headless verification, WebXR headset support, HTML5 web exports and zero engine licensing friction. - **Three.js (Three.js):** TypeScript 3D web games with three-mesh-bvh triangle-mesh physics, WebP/meshopt-compressed glTF models, responsive phone touch controls and WebXR headset play. - **Pulse (Pulse):** GameCrew’s compact deterministic TypeScript engine with declarative JSONC areas and witnessed gameplay scenarios that verify in under a second and boot instantly on phones and desktops. Compare all four engines in detail at https://gamecrew.ai/engines, or see MCP & source export docs at https://gamecrew.ai/developers. ## Workflow & pipeline FAQ ### How do you update or tune a game after the first version is built? You can describe changes in plain English, pin feedback notes directly onto screenshots or inside a running shared game, adjust live gameplay tuning sliders at zero AI cost, compare screenshots across versions side by side, or roll back to any earlier git-tagged version. ### Can I connect Claude Code, Cursor, or another MCP assistant to GameCrew? Yes. Creators can generate a scoped access token on the studio Usage page and connect any MCP-compatible coding assistant to inspect the project map, edit scripts and scenes, look up offline engine APIs, and run sandboxed engine verification. ### Where do GameCrew’s 3D models, textures, and audio come from? GameCrew generates bespoke concept art, 3D meshes, humanoid rigs and animation clips, seamless PBR normal and roughness maps, sound effects, and looping music, alongside a curated CC0 and CC BY open-licence asset library that automatically tracks creator attribution credits. ### What happens when a build hits a compile error or fails a gameplay test? GameCrew’s verification harness captures exact compiler diagnostics, scene transform issues, failed playtest assertions, and headless browser errors, feeding them back to the build agents so broken code or unplayable cameras are fixed before you see the version. --- # Game Engines in GameCrew: Unity 6, Godot 4, Three.js, Pulse & WebXR VR > GameCrew builds real, downloadable game projects in four engines — Unity 6 (URP), Godot 4, Three.js, and Pulse — with browser WebXR VR headset support on Three.js, Godot 4, and Unity 6. - **Canonical URL:** https://gamecrew.ai/engines ## Side-by-side engine comparison | Engine | Scripting & Scenes | Rendering | Platforms | WebXR VR | Verification Gates | Source & Build Export | Best For | | --- | --- | --- | --- | --- | --- | --- | --- | | **Unity 6** | C# (.cs) + generated URP scenes | Universal Render Pipeline 3D, custom shaders, PBR maps & baked FBX LODs | Desktop & mobile browser (WebGL), WebXR VR headsets, macOS / Windows / Linux standalone | Yes — WebXR head & hand tracking in headset browsers | Batch compile, SceneScan transform check, EditMode & PlayMode tests, Chrome WebGL boot, emulated WebXR headset check & captures | Full Unity 6 project (.zip), WebGL build (.tar.gz) & standalone desktop players | Multi-area 3D adventures, stylized worlds, rigged characters & standalone desktop releases | | **Godot 4** | GDScript (.gd) + .tscn scene trees | Open-source 2D & 3D rendering, PBR materials & rigged GLB animations | Desktop & mobile browser (HTML5 WebAssembly) & WebXR VR headsets | Yes — WebXR head & hand tracking in headset browsers | Headless compile, check.gd scene scan, playthrough tests, Chrome boot, emulated WebXR headset check & contact sheets | Full Godot 4 project (.zip, MIT engine) & HTML5 web build (.tar.gz) | Open-source 2D/3D indie games, royalty-free source ownership & browser VR | | **Three.js** | TypeScript (.ts) + Three.js & three-mesh-bvh | WebGL2 PBR with procedural RoomEnvironment IBL, compressed glTF & bloom | Instant desktop & mobile browser bundle & WebXR VR headsets | Yes — WebXR head & hand tracking in headset browsers | TypeScript & AST safety lint, unit & playthrough tests, headless Chrome boot, emulated WebXR headset check & captures | Full TypeScript project (.zip) & bundled web build (.tar.gz) | Rapid 3D browser games, mobile touch play & instant-loading WebXR VR experiences | | **Pulse** | TypeScript systems + deterministic JSONC areas | Lightweight WebGPU / browser 3D & 2D runtime | Instant-boot desktop & mobile browser | Flat browser & mobile | TypeScript type-check, witnessed deterministic scenarios, parameter sweeps & headless Chrome boot | Full Pulse TypeScript/JSONC project (.zip) & web build (.tar.gz) | Crisp arcade, puzzle or simulation games with sub-second verification loops | ## WebXR VR browser games (Three.js, Godot 4 & Unity 6) Games built with the VR target in Three.js, Godot 4 or Unity 6 play directly in headset browsers via WebXR (`Enter VR`) with stereo eye rendering, 6DoF head and hand controller tracking, comfort locomotion (stick walk with vignette, snap turn, teleport), and world-space UI panels — while the exact same share link plays flat on desktop and mobile. ## Engine & export FAQ ### Which game engine should I choose in GameCrew? Leave the engine on Recommended to let the pitch pick automatically: Three.js for fast 3D web and VR games, Godot 4 for open-source 2D/3D and VR with zero engine royalties, Unity 6 URP for rich stylized 3D worlds, VR and desktop downloads, or select Pulse manually for instant-boot deterministic web games. ### How do WebXR VR games work in GameCrew? Three.js, Godot 4 and Unity 6 games built with the VR target run in headset browsers via WebXR with no app store install: players press Enter VR for stereo rendering, tracked head and hands, comfort locomotion, and world-space UI, while the same link plays flat on desktops and phones. ### Are exported GameCrew projects standard Unity 6 and Godot 4 projects? Yes. GameCrew scaffolds clean engine projects under standard git version control: C# scripts, URP materials, and FBX prefabs for Unity 6; .tscn scenes and GDScript for Godot 4; and TypeScript sources for Three.js and Pulse. ### How does GameCrew verify VR games automatically? Whenever a VR game is saved, GameCrew boots the exported web build in headless Chrome with an emulated WebXR headset and controllers, verifying distinct left/right eye views, head-rotation camera tracking, controller trigger and stick input, and clean exit back to flat play. --- # Build games together on GameCrew AI: branches, merge requests and rewards > Make branches of each other's games, merge verified merge requests into main, share 3D/PBR assets and proven engine techniques, and earn build credits when other people genuinely adopt your work. - **Canonical URL:** https://gamecrew.ai/collaborate - **Engine technique commons:** https://gamecrew.ai/techniques - **Agent onboarding guide:** https://gamecrew.ai/agents.md ## How collaborative craft stays high-signal 1. **Branches & verified merge requests:** Make a branch of any game you can see (`create_branch`), run automated engine compiles and playtests, and open a merge request into its main line with `open_merge_request`. Owners accept only changes that improve the game. Forks (a game of your own) are for games whose owner allows them, like the showcase games. 2. **Shared 3D models & seamless PBR textures:** Reusable 3D props, rigged characters, and seamless textures enter the studio library with automatic provenance and `credits.json` attribution (while generated sound effects and music stay owner-only). 3. **Growing engine technique library:** Curated and compile-verified techniques across Unity 6, Godot 4, Three.js, and Pulse (`search_techniques`, `read_technique`, `contribute_technique`) compound shared engine craft. 4. **Opt-in `@handle` maker profiles:** Handles stay private to merge request threads unless a creator turns on their public profile at `/makers/` — grounded strictly in verified games, merged merge requests, and shared craft. ## Craft reward schedule (downstream adoption only) | Collaborative Milestone | Earned Reward | Verification & Anti-Farming Guardrails | | --- | --- | --- | | Verified merge request merged into another creator’s game | +15 build credits · +10 daily engine minutes | Compile + playtest gate must pass, owner must merge manually, self-merges pay 0, idempotent per merge request | | Platform-shared 3D model or PBR texture used in another creator’s verified build | +3 build credits · +5 daily engine minutes | Target build must pass automated verification, raw/unused uploads pay 0, sound & external CC0/BY excluded | | Rolling 30-day safeguards | Up to 120 credits · up to 60 daily engine minutes | Max 2 rewarded events per counterparty pair per 30 days | ## Frequently asked questions ### How do branches and verified merge requests work between two creators? Anyone signed in (or connected via a coding assistant over MCP) can make a branch of a game they can see with create_branch, improve scripts or levels in it, pass automated compile and playtest checks, and open a merge request into the game's main line with open_merge_request. Only merges accepted by the game owner land in main. The owner decides who may branch (anyone who can see the game, the crew only, or nobody) and whether forks, a separate game of your own, are allowed at all: they are off unless the owner switches them on, and on for every showcase game. ### How do collaborative craft rewards avoid spam and low-effort submissions? GameCrew never rewards raw uploads, self-merges, or unverified drafts. Creators earn bonus build credits and daily engine minutes strictly from downstream adoption by other people: +15 credits and +10 daily engine minutes when another creator merges your verified merge request, and +3 credits and +5 daily engine minutes when another creator ships a verified build containing your shared 3D model or seamless PBR texture. ### Are there safeguards against farming rewards across friendly accounts? Yes. Every milestone is idempotent (the same merge request merge or asset-in-game adoption can never pay twice), each contributor/adopter pair is capped at 2 rewarded events per rolling 30 days, and total rolling 30-day collaboration bonuses are capped at 120 credits and 60 daily engine minutes. ### Why are generated sound effects and music private while 3D models and textures can be shared? By platform policy, generated 3D models and seamless PBR textures can enter the shared studio library (with an option to mark any item private), earning adoption rewards when other creators build with them. Generated sound effects and music stay owner-only in your own library and are excluded from cross-account sharing and rewards. ### How do public @handle maker profiles work? Handles are private to merge request threads by default. Creators who choose to turn on their public profile in the studio Usage page get a verified page at /makers/ displaying only their showcase games, merged contributions, and craft milestones — never email addresses, external link spam, or clout counters. --- # GameCrew Engine Technique Commons — Unity 6, Godot 4, Three.js & Pulse > Reusable, compile-verified game development techniques, camera rigs, shaders, physics patterns, multiplayer syncing, and WebXR setups curated across all four GameCrew engines. - **Canonical URL:** https://gamecrew.ai/techniques - **Collaboration & rewards overview:** https://gamecrew.ai/collaborate - **Indexed techniques:** 102 ## Unity 6 (10) - **[Atmospheric Height Fog, Sun Shafts & Rim-Readable Lighting in Unity 6 URP](https://gamecrew.ai/techniques/unity/atmospheric-lighting-fog)** ([Markdown](https://gamecrew.ai/techniques/unity/atmospheric-lighting-fog.md)) [lighting] — Three-point outdoor/interior URP lighting recipe combining directional sun + warm/cool fill, exponential height/distance fog, ACES/Neutral post-processing, and anti-darkness floors so captures never read black or washed out. - **[Cel-Shading, Shadow Ramps & Width-Compensated Outlines in Unity 6 URP](https://gamecrew.ai/techniques/unity/cel-shading-outlines)** ([Markdown](https://gamecrew.ai/techniques/unity/cel-shading-outlines.md)) [shaders] — Two-pass URP stylized cel shader combining main-light shadow-attenuated diffuse ramps, crisp specular/rim accents, and clip-space distance-compensated inverted-hull outlines. - **[CharacterController Slope Projection & Floor Snap in Unity 6](https://gamecrew.ai/techniques/unity/character-controller-kinematic-slopes)** ([Markdown](https://gamecrew.ai/techniques/unity/character-controller-kinematic-slopes.md)) [physics] — Deterministic Unity 6 CharacterController locomotion with SphereCast ground projection, ramp stickiness, steep-slope slide, and coyote jumps. - **[Context Steering, Telegraphed Combat & Attack-Token Encounters in Unity 6](https://gamecrew.ai/techniques/unity/enemy-npc-ai-encounters)** ([Markdown](https://gamecrew.ai/techniques/unity/enemy-npc-ai-encounters.md)) [ai] — Readable enemy and companion AI in Unity 6 using 8-ray context steering maps, FOV + line-of-sight hysteresis, telegraph/active/recovery state machines, and an encounter attack-token director. - **[GPU-Instanced Wind Foliage & Interactive Player Bend in Unity 6 URP](https://gamecrew.ai/techniques/unity/gpu-instanced-foliage-wind)** ([Markdown](https://gamecrew.ai/techniques/unity/gpu-instanced-foliage-wind.md)) [optimization] — Draw thousands of swaying grass blades, reeds, or wildflowers in 1–4 draw calls using Graphics.RenderMeshInstanced, URP instanced HLSL wind gusts, tip flutter, and player-sphere pushback. - **[Frame-Rate-Independent Procedural Springs, Squash-Stretch & Trauma Feel in Unity 6](https://gamecrew.ai/techniques/unity/procedural-springs-game-feel)** ([Markdown](https://gamecrew.ai/techniques/unity/procedural-springs-game-feel.md)) [gameplay] — Exact dt-invariant second-order critically/under-damped spring dampers, Squirrel Eiserloh T^2 rotational Perlin camera trauma, volume-preserving squash-and-stretch, and TestClock-safe hit-stop. - **[Stylized Water, Depth Shoreline Foam & Gerstner Waves in Unity 6 URP](https://gamecrew.ai/techniques/unity/stylized-water-caustics)** ([Markdown](https://gamecrew.ai/techniques/unity/stylized-water-caustics.md)) [water] — URP transparent water surface with analytical Gerstner wave displacement and normals, scene-depth Beer-Lambert dual-color absorption, Worley shoreline foam, and crisp sun specular. - **[Unity 6 URP RenderGraph Custom Screen-Space Pass](https://gamecrew.ai/techniques/unity/urp-rendergraph-custom-pass)** ([Markdown](https://gamecrew.ai/techniques/unity/urp-rendergraph-custom-pass.md)) [rendering] — Custom Unity 6 URP 17.6 ScriptableRendererFeature overriding RecordRenderGraph with transient TextureHandle creation and AddBlitPass. - **[Volumetric Cloud Rendering in Unity 6 URP](https://gamecrew.ai/techniques/unity/volumetric-clouds)** ([Markdown](https://gamecrew.ai/techniques/unity/volumetric-clouds.md)) [atmosphere] — Height-band raymarched volumetric cloud dome in Unity 6 URP HLSL using Perlin-Worley FBM, Schneider's Beer-Powder law, dual-lobe Henyey-Greenstein silver lining, interleaved gradient noise jitter, WebGL 2 loop/LOD rules, and llvmpipe step scaling. - **[Physical 6DoF VR Hand Interactions, Throw Windows & Spatial Comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics)** ([Markdown](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics.md)) [vr] — Tactile 6DoF VR interactions in Unity 6 using CCGD.GameXR: articulated hands that wrap what they hold, near-grab + distance-pull cones, 6-sample sliding-window throws, snap holsters, diegetic world panels, and flat+VR parity. ### The AI crew on Unity 6: its prompts and set-up (18) - [How the AI crew builds a Unity 6 game: the set-up and the lead's prompt](https://gamecrew.ai/techniques/unity/ai-crew-lead.md) - [Project notes for a Unity 6 game: layout, conventions and checks the AI crew works to](https://gamecrew.ai/techniques/unity/ai-crew-project-notes.md) - [AI & encounter designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-ai-designer.md) - [Animator: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-animator.md) - [Asset artist: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-asset-artist.md) - [Critic: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-critic.md) - [Game feel & juice designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-feel-designer.md) - [Implementer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-implementer.md) - [Level designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-level-designer.md) - [Narrative designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-narrative-designer.md) - [Playtester & balance QA: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-playtester.md) - [Puzzle designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-puzzle-designer.md) - [Scout: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-scout.md) - [Sound designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-sound-designer.md) - [Storyboarder: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-storyboarder.md) - [Technique researcher: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-technique-researcher.md) - [UI designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-ui-designer.md) - [VR interaction designer: the AI crew's Unity 6 role prompt](https://gamecrew.ai/techniques/unity/ai-crew-vr-designer.md) ## Godot 4 (7) - **[CharacterBody3D Slopes, Snap & Coyote Jump in Godot 4](https://gamecrew.ai/techniques/godot/characterbody3d-platformer-controller)** ([Markdown](https://gamecrew.ai/techniques/godot/characterbody3d-platformer-controller.md)) [physics] — Crisp Godot 4 CharacterBody3D locomotion combining floor_snap_length, apex hang gravity, jump-cut, coyote time, and zero-arg move_and_slide. - **[Context Steering, Patrol Paths & Telegraphed Enemy Encounters in Godot 4](https://gamecrew.ai/techniques/godot/enemy-npc-ai-steering)** ([Markdown](https://gamecrew.ai/techniques/godot/enemy-npc-ai-steering.md)) [ai] — Typed GDScript 4 context steering, LevelData patrol-path following, line-of-sight perception with memory hysteresis, attack-token pacing, and telegraphed combat state machines. - **[Frame-Rate-Independent Springs, Squash-Stretch & Ribbon Trails in Godot 4](https://gamecrew.ai/techniques/godot/procedural-springs-trails)** ([Markdown](https://gamecrew.ai/techniques/godot/procedural-springs-trails.md)) [gameplay] — Typed GDScript 4 second-order damped springs, volume-preserving visual squash-stretch, Eiserloh T^2 FastNoiseLite camera trauma, and ImmediateMesh sword/dash ribbon trails. - **[Stylized Water, Gerstner Waves & Depth Shoreline Foam in Godot 4 Compatibility](https://gamecrew.ai/techniques/godot/stylized-water-foam)** ([Markdown](https://gamecrew.ai/techniques/godot/stylized-water-foam.md)) [water] — Godot 4.7 Compatibility spatial water shader using analytical Gerstner vertex waves, hint_depth_texture shoreline foam, Beer-Lambert depth absorption, and Fresnel horizon sheen. - **[Raymarched Volumetric Cloud Sky in Godot 4 Compatibility (WebGL 2)](https://gamecrew.ai/techniques/godot/volumetric-clouds-sky-webgl)** ([Markdown](https://gamecrew.ai/techniques/godot/volumetric-clouds-sky-webgl.md)) [atmosphere] — Compatibility-safe sky shader in Godot 4.7 raymarching a height-bounded cloud slab with procedural 3D hash FBM, Beer-Powder silver lining, Henyey-Greenstein phase, and AT_CUBEMAP_PASS step budgeting. - **[Physical 6DoF VR Hand Interactions, Throw Windows & Spatial Comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics)** ([Markdown](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics.md)) [vr] — Physical 6DoF VR hand interactions in Godot 4 using GameXR and XRInteract: the kit's articulated hands (controller-posed and hand-tracked, pinch and grab with hysteresis, power/pinch/sphere grip poses), near-grab + distance-pull cones, 6-step sliding-window throws, snap holsters, 3D buttons, teleport + smooth + seated comfort, and flat+VR parity. - **[WebXR Hand Tracking & Controller Parity in Godot 4](https://gamecrew.ai/techniques/godot/webxr-hand-tracking-quest-browser)** ([Markdown](https://gamecrew.ai/techniques/godot/webxr-hand-tracking-quest-browser.md)) [vr] — Unified Quest bare-hand tracking and controller input in Godot 4 using GameXR pinch/grab hysteresis, fingertip poke, and button_3d. ### The AI crew on Godot 4: its prompts and set-up (18) - [How the AI crew builds a Godot 4 game: the set-up and the lead's prompt](https://gamecrew.ai/techniques/godot/ai-crew-lead.md) - [Project notes for a Godot 4 game: layout, conventions and checks the AI crew works to](https://gamecrew.ai/techniques/godot/ai-crew-project-notes.md) - [AI & encounter designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-ai-designer.md) - [Animator: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-animator.md) - [Asset artist: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-asset-artist.md) - [Critic: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-critic.md) - [Game feel & juice designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-feel-designer.md) - [Implementer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-implementer.md) - [Level designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-level-designer.md) - [Narrative designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-narrative-designer.md) - [Playtester & balance QA: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-playtester.md) - [Puzzle designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-puzzle-designer.md) - [Scout: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-scout.md) - [Sound designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-sound-designer.md) - [Storyboarder: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-storyboarder.md) - [Technique researcher: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-technique-researcher.md) - [UI designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-ui-designer.md) - [VR interaction designer: the AI crew's Godot 4 role prompt](https://gamecrew.ai/techniques/godot/ai-crew-vr-designer.md) ## Three.js (8) - **[Instanced Wind Foliage, Object-Pooled Particles & Spring Feel in Three.js](https://gamecrew.ai/techniques/three/instanced-foliage-springs)** ([Markdown](https://gamecrew.ai/techniques/three/instanced-foliage-springs.md)) [optimization] — Single-draw-call THREE.InstancedMesh wind foliage with player bend, zero-GC pooled burst particles, and dt-invariant second-order springs that keep 60 Hz steps under 2 ms. - **[Raymarched Volumetric Clouds & Atmospheric Sky Shaders in Three.js (WebGL 2)](https://gamecrew.ai/techniques/three/volumetric-clouds-sky-shaders)** ([Markdown](https://gamecrew.ai/techniques/three/volumetric-clouds-sky-shaders.md)) [atmosphere] — Self-contained THREE.ShaderMaterial sky dome in GLSL ES 3.0 raymarching a height-bounded cloud layer with 3D value-Worley FBM, Beer-Powder silver lining, interleaved gradient noise, and mobile step scaling. - **[BVH Mesh & Character Capsule Collision in Three.js](https://gamecrew.ai/techniques/three/bvh-character-capsule-collision)** ([Markdown](https://gamecrew.ai/techniques/three/bvh-character-capsule-collision.md)) [physics] — Fast capsule-vs-triangle pushout and slope resolution using three-mesh-bvh shapecasts, pre-allocated scratch vectors, and CollisionWorld. - **[Zero-Allocation Context Steering, Patrol Loops & Telegraphed AI in Three.js](https://gamecrew.ai/techniques/three/enemy-npc-ai-steering)** ([Markdown](https://gamecrew.ai/techniques/three/enemy-npc-ai-steering.md)) [ai] — Deterministic 60 Hz enemy and companion AI in Three.js using 8-slot context steering against CollisionWorld, level.json patrol loops, attack-token pacing, and telegraphed strikes. - **[Multiplayer Room State Sync & 60 Hz Avatars in Three.js](https://gamecrew.ai/techniques/three/multiplayer-room-state-interpolation)** ([Markdown](https://gamecrew.ai/techniques/three/multiplayer-room-state-interpolation.md)) [gameplay] — Solo-first multiplayer with smooth 60 Hz remote avatars, host-owned shared state, reliable host claims, and deterministic two-peer room tests. - **[Stylized Water, Cel-Shading Ramps & Outlines in Three.js (r183)](https://gamecrew.ai/techniques/three/stylized-water-toon-shaders)** ([Markdown](https://gamecrew.ai/techniques/three/stylized-water-toon-shaders.md)) [shaders] — Three.js r183 NearestFilter DataTexture cel-shading ramps, BackSide normal-extruded outlines, and analytical Gerstner wave water ShaderMaterial with cellular foam. - **[Physical 6DoF VR Hand Interactions, Throw Windows & Spatial Comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics)** ([Markdown](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics.md)) [vr] — Tactile 6DoF WebXR hand interactions in Three.js using game.xr: the kit's articulated hands (controller-posed and tracked, fingers closing on held things), near-grab + distance-pull cones, 6-step sliding-window throws, snap sockets, 3D world buttons, and flat+VR parity. - **[Quest WebXR Performance & Draw-Call Instancing in Three.js](https://gamecrew.ai/techniques/three/webxr-quest-performance-instancing)** ([Markdown](https://gamecrew.ai/techniques/three/webxr-quest-performance-instancing.md)) [vr] — Stay under 200 draw calls and 300k stereo triangles per frame in WebXR via InstancedMesh batches, zero-alloc updates, and WorldPanel HUDs. ### The AI crew on Three.js: its prompts and set-up (18) - [How the AI crew builds a Quick (three.js) game: the set-up and the lead's prompt](https://gamecrew.ai/techniques/three/ai-crew-lead.md) - [Project notes for a Quick (three.js) game: layout, conventions and checks the AI crew works to](https://gamecrew.ai/techniques/three/ai-crew-project-notes.md) - [AI & encounter designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-ai-designer.md) - [Animator: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-animator.md) - [Asset artist: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-asset-artist.md) - [Critic: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-critic.md) - [Game feel & juice designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-feel-designer.md) - [Implementer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-implementer.md) - [Level designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-level-designer.md) - [Narrative designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-narrative-designer.md) - [Playtester & balance QA: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-playtester.md) - [Puzzle designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-puzzle-designer.md) - [Scout: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-scout.md) - [Sound designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-sound-designer.md) - [Storyboarder: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-storyboarder.md) - [Technique researcher: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-technique-researcher.md) - [UI designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-ui-designer.md) - [VR interaction designer: the AI crew's Quick (three.js) role prompt](https://gamecrew.ai/techniques/three/ai-crew-vr-designer.md) ## Pulse (5) - **[Atmospheric Vistas, Volumetric Clouds & Deterministic Feel in Pulse](https://gamecrew.ai/techniques/pulse/atmosphere-vistas-springs)** ([Markdown](https://gamecrew.ai/techniques/pulse/atmosphere-vistas-springs.md)) [atmosphere] — Composing Pulse physical sky, volumetric clouds, volumetric fog, water/foliage, and pure component-backed spring feel without violating sandboxed tick determinism. - **[Deterministic Grid Push-Block & Tile Sweeps in Pulse](https://gamecrew.ai/techniques/pulse/deterministic-grid-puzzle-sweeps)** ([Markdown](https://gamecrew.ai/techniques/pulse/deterministic-grid-puzzle-sweeps.md)) [gameplay] — Deterministic grid-based puzzle sweeps in Pulse using integer cell components, per-entity occupancy scans, and smooth fixed-tick interpolation. - **[Deterministic ECS Enemy Brains, Encounter Directors & Telegraphed Bosses in Pulse](https://gamecrew.ai/techniques/pulse/enemy-npc-ai-directors)** ([Markdown](https://gamecrew.ai/techniques/pulse/enemy-npc-ai-directors.md)) [ai] — Data-oriented Pulse ECS enemy perception, orbit steering, attack-token encounter pacing, and multi-phase telegraphed boss state machines verified with headless pulse_run invariants. - **[Deterministic Telegraphed Boss Phases in Pulse](https://gamecrew.ai/techniques/pulse/fixed-tick-telegraphed-boss-encounters)** ([Markdown](https://gamecrew.ai/techniques/pulse/fixed-tick-telegraphed-boss-encounters.md)) [ai] — Deterministic multi-phase boss telegraphing in Pulse with integer phase state, ground ring vfx, rand() jitter, and fixed-tick shockwaves. - **[Procedural Gait, Chain Motion & Readable Impact VFX in Pulse](https://gamecrew.ai/techniques/pulse/procedural-motion-combat-vfx)** ([Markdown](https://gamecrew.ai/techniques/pulse/procedural-motion-combat-vfx.md)) [animation] — Expressive creature locomotion and impact readability in Pulse using ProceduralMotion, ProceduralGait, ProceduralChain, deterministic hit-flash/recoil components, and layered vfx bursts. ### The AI crew on Pulse: its prompts and set-up (18) - [How the AI crew builds a Pulse game: the set-up and the lead's prompt](https://gamecrew.ai/techniques/pulse/ai-crew-lead.md) - [Project notes for a Pulse game: layout, conventions and checks the AI crew works to](https://gamecrew.ai/techniques/pulse/ai-crew-project-notes.md) - [AI & encounter designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-ai-designer.md) - [Animator: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-animator.md) - [Asset artist: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-asset-artist.md) - [Critic: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-critic.md) - [Game feel & juice designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-feel-designer.md) - [Implementer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-implementer.md) - [Level designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-level-designer.md) - [Narrative designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-narrative-designer.md) - [Playtester & balance QA: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-playtester.md) - [Puzzle designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-puzzle-designer.md) - [Scout: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-scout.md) - [Sound designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-sound-designer.md) - [Storyboarder: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-storyboarder.md) - [Technique researcher: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-technique-researcher.md) - [UI designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-ui-designer.md) - [VR interaction designer: the AI crew's Pulse role prompt](https://gamecrew.ai/techniques/pulse/ai-crew-vr-designer.md) ## Technique commons FAQ ### What is the GameCrew engine technique library? It is a curated, searchable library of reusable gameplay, rendering, camera, physics, shader, multiplayer, and WebXR techniques across Unity 6, Godot 4, Three.js, and Pulse. Every entry pairs concrete API usage with grounded pitfalls and verified code patterns. ### How can coding assistants read and improve techniques over time? Through MCP tools (search_techniques, read_technique, and contribute_technique) or direct cloud-workspace builds, assistants look up proven engine solutions before guessing and contribute newly discovered, compile-verified patterns back for every future builder. ### Are the AI crew's own prompts published? Yes. For each engine the library holds how GameCrew AI's crew is set up (one lead, specialist roles, the task brief every hand-over opens with, tasks running side by side on their own files), the lead's full instructions, the notes every game starts with, and each specialist's role prompt. They are made from the code a build runs, so they are what runs today, and anyone may adapt them for an assistant of their own. ### How does GameCrew keep user-contributed techniques free of hallucinations or prompt injection? Only verified accounts can propose new entries, and submissions require compile-verified provenance plus automated checks against disallowed scripts, markup, or prompt-injection payloads. Web reads increment zero artificial popularity counters. ### Do exported games depend on a proprietary GameCrew runtime to use these techniques? No. Every pattern uses standard Unity 6 C#, Godot 4 GDScript, Three.js TypeScript, or Pulse source files inside your own repository — so exported projects work cleanly offline in your local editor. --- # Make a WebXR Game for Quest from a Brief: One Link, Flat or in a Headset (GameCrew AI) > GameCrew AI builds dual-mode WebXR VR games in Three.js, Godot 4 and Unity 6 from a plain-English brief. One share link plays flat on a computer or phone and offers `Enter VR` in a headset browser: no store, no sideloading, no cable. - **Canonical URL:** https://gamecrew.ai/vr - **Status:** early access. Every saved version of a VR game is checked in an emulated headset (a Quest 3 profile in headless Chrome) before it gets a link. The check proves the game enters VR, draws both eyes, follows the head and reads the controllers; it does not measure comfort or a real headset’s frame rate. Reports from real headsets are being collected now. - **Supported WebXR engines:** Three.js (TypeScript), Godot 4 (GDScript / `.tscn`), and Unity 6 URP (C#; the studio’s WebXR session drives Unity’s WebGL frames). Pulse (WebGPU) is flat-only today. ## Try it now: play it on your headset, then make one 1. **Play one in your headset:** open `gamecrew.ai/vr` in the headset’s browser and choose [Lumen Orchard](https://gamecrew.ai/games/lumen-orchard). Press Play, then Enter VR. The same link plays flat on a laptop or phone. 2. **Pitch your own, free:** describe a Quest browser game on [the home page](https://gamecrew.ai/?via=vr#pitch); the pitch, look and controls come back in about two minutes, no sign-up. 3. **Build it:** with a place in early access, GameCrew’s AI crew builds the pitch with the VR target on; or connect your own assistant (Claude, ChatGPT, Claude Code, Cursor) to `play.gamecrew.ai/mcp` on the [Contributor tier](https://gamecrew.ai/tiers), free in early access: it forks a VR showcase game and makes it yours. 4. **Open the link on the headset:** each saved version gets its own link; a version that fails the emulated-headset check is marked failed, with what went wrong. ## What works in each engine today | Engine | WebXR VR | Headset runtime | Hands & interaction | Checked without a headset | | --- | --- | --- | --- | --- | | Three.js (Quick) | Dual-mode `immersive-vr` | three.js’s own WebXR, driven by the studio’s `game.xr` kit | Grab, throw, sockets, 3D buttons, haptics; a bare hand’s pinch is the trigger | Play tests in a simulated headset + emulated-headset check on every save | | Godot 4 | Dual-mode `immersive-vr` | Godot 4’s `WebXRInterface`, run by the studio’s `GameXR` kit | Grab, throw, sockets, 3D buttons, haptics; world panels from any `Control` tree | GDScript play tests in a simulated headset + emulated-headset check on every save | | Unity 6 URP | Dual-mode `immersive-vr` | The studio’s page runs the session and drives Unity 6 WebGL; the `GameXR` kit does the rig, a camera per eye and the hands (no XR packages) | Grab, throw, sockets, 3D buttons, haptics; a bare hand’s pinch is the trigger | PlayMode smoke tests in a simulated headset + emulated-headset check on every save | | Pulse | Flat-only today | WebGPU, no WebXR path yet | None yet | Not a VR target | Unlike a VR game generator that hands back a single web page, each GameCrew game is a real engine project with its own tests and git history: download any saved version, or keep changing it with your own assistant. ## What every VR game gets from the kit - **A flat game already plays in VR:** with no VR code, the eyes go where the game’s camera is, the horizon stays level, the left stick moves, the right stick snap-turns, and the HUD and menus are drawn in the world. A VR-first game takes the rig, head and hands instead. - **Tracked head and two hands:** grip and aim poses, trigger, squeeze, stick, A/B/X/Y and haptics; the game’s actions map to controller inputs the way they map to keys. - **Physical hand interactions:** near grab and distance pull, throws from a 6-sample hand-velocity window, two-hand transfers, snap sockets and holsters, 3D buttons you poke or point at. - **Comfort locomotion:** teleport on an arc, snap turn, slow stick walking with a vignette, or none for seated and standing games. The view never moves or turns by itself. - **UI in the world:** HUD, prompts, pause menu and end screen on world panels, worked with a hand ray and the trigger. - **Budgets for a standalone headset:** 200 draw calls and 300k triangles a frame, no full-screen post effects in a session; over budget is a note, not a failure. ## What the emulated-headset check proves on every save Headless Chrome with an emulated headset (IWER, a Quest 3 profile, no network) clicks `Enter VR` and requires: the session starts and both eyes are drawn from two viewpoints; turning the head 120° changes the picture and turning back restores it; moving the head 0.4 m moves the viewer; the left stick reaches the game’s move input and the right trigger is read; leaving VR gives back the flat game; nothing logs an error. It does not measure comfort, a real headset’s frame rate, or how a game feels in the hand. ## Learn the techniques: VR hands, throws and comfort - [VR hand interactions, throw windows and comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics) - [VR hand interactions, throw windows and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) - [VR hand interactions, throw windows and comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics) ## Playable WebXR VR showcase games - **[Lumen Orchard](https://gamecrew.ai/games/lumen-orchard)** (Three.js) - **[Fernlight](https://gamecrew.ai/games/fernlight)** (Godot 4) — Raise a carved whistle to your lips in a fog-drowned forest, coax a glowing bird onto your open hand, and point to send it off to light the dark. ## Browser VR & WebXR FAQ ### Which VR headsets can play GameCrew WebXR games? Any headset whose browser can start a WebXR immersive-vr session: Meta Quest 2, Quest Pro and Quest 3/3S in Meta Quest Browser, Pico headsets in their browser, PC VR headsets through Chrome or Edge, and Apple Vision Pro in Safari (see below for its input). There is nothing to install: open the link and press Enter VR. GameCrew AI is in early access and checks every save in an emulated Quest 3; reports from real headsets are what we are collecting now. ### Can I make a Meta Quest game without Unity? Yes. A GameCrew VR game can be built in Three.js (TypeScript) or Godot 4 (GDScript) as well as Unity 6, and all three play in Meta Quest Browser from one link. You don’t install an engine, turn on developer mode, sideload an APK or go through a store review: the game is a web page that offers Enter VR. It is a browser game, not a Horizon Store app. ### Should I make a WebXR game or a native Quest app? A WebXR game is a link: anyone can play it in seconds, updates are live the moment you save, it plays flat for people without a headset, and nothing goes through a store. A native app gets more of the headset’s GPU, store discovery and payments, and features a browser session doesn’t offer. GameCrew’s VR games are WebXR: they stay inside a standalone headset’s budget (200 draw calls and 300k triangles a frame, no full-screen post effects) and use immersive VR, not passthrough mixed reality. They suit prototypes, jam games and small finished games you want people to try right away. ### Does it work on Apple Vision Pro? Safari on Vision Pro can start an immersive-vr session, so the Enter VR button appears there. Its input is usually your hands (look and pinch) rather than controllers. Three.js and Unity games read a bare hand’s pinch as the trigger, so aim-and-pinch games can work; a game that needs sticks or buttons won’t fully play with hands alone. We have not yet confirmed GameCrew games on a Vision Pro. ### Do I need a headset to make a VR game with GameCrew? No. Each engine’s VR kit has a simulated headset for the game’s own play tests, every save runs an emulated-headset check in headless Chrome, and a VR-first Three.js game plays flat with mouse look and W/A/S/D standing in for the head and hands. Put a headset on before you share it, though: the check proves the game enters VR, draws both eyes, follows the head and reads the controllers, not that it is comfortable or fast on a real device. ### Do players without a VR headset still get to play the same link? Yes. Every GameCrew VR build is dual-mode from a single share link: it plays flat with keyboard and mouse, gamepad or phone touch on regular screens, and offers an Enter VR button when opened in a WebXR headset browser. A browser without WebXR shows a quiet note that the link plays in VR in a headset’s browser. ### Which game engines in GameCrew support WebXR VR? Three.js (three.js’s own WebXR), Godot 4 (its WebXRInterface) and Unity 6 URP (the studio’s page runs the WebXR session and drives Unity’s WebGL frames; Unity’s XR packages are not used). Each has the studio’s VR kit: the rig, tracked head and hands, comfort locomotion, hand interactions and the HUD drawn in the world. Pulse, the studio’s WebGPU engine, plays flat only for now. ### How does GameCrew verify that a VR game actually works before I put on a headset? Every saved version of a VR game runs its browser build in headless Chrome with an emulated headset (IWER with a Quest 3 profile, no network). The check clicks Enter VR, requires both eyes to be drawn from two different viewpoints, turns the head 120° and back and moves it 0.4 m and requires the view to follow, pushes the left stick and holds the right trigger and requires the game to read them, leaves VR and requires the flat game to carry on, and fails on any logged error. It also reports draw calls and triangles against a standalone headset’s budget. ### What VR comfort options are built into GameCrew’s VR kits? Teleport on an arc, snap turn, slow thumbstick walking with a comfort vignette, or no locomotion at all for seated and standing games. The kits never move, shake or turn the view by themselves, keep the horizon level, and draw menus on panels in the world 1 to 2 m away, worked with a hand ray, so nothing is glued to the player’s face. ### Can a VR game also be multiplayer? Yes. Three.js, Godot 4 and Unity 6 games can have both the VR and the multiplayer targets: the link stays solo-first and offers a 4-letter room code for 2 to 8 players. Each save runs the multiplayer check (two browsers in a live room) and the VR check (an emulated headset) separately; a two-headset session has not been checked yet. ### Can I download and customize the WebXR VR source code? Yes. Every saved version is a git tag you can download as a full project: TypeScript for Three.js, .tscn scenes and GDScript for Godot 4, or C# for Unity 6, with the VR kit, the game’s tests and its assets. Or edit it live from your own assistant over MCP. ### What does it cost to make a VR game? The pitch on the home page is free, with no sign-up. Building with your own assistant (Claude, ChatGPT, Claude Code, Cursor) is the Contributor tier, free during early access: your assistant writes the code and GameCrew runs the engine. Having GameCrew’s AI crew build the game from your brief is the Platform tier, on a plan. Places in early access open a few at a time. --- # How GameCrew Compares: AI Game Studio vs Browser Generators, Coding Assistants & Asset Tools > GameCrew combines structured game design, bespoke 3D/rigging/PBR/audio generation, real Unity 6 / Godot 4 / Three.js / Pulse workspaces, automated playtest & WebXR verification, collaborative merge requests, clean git source export, and a 91-tool Streamable HTTP MCP server for Claude Code, Cursor, and VS Code. - **Canonical URL:** https://gamecrew.ai/compare ## Side-by-side workflow comparison | Dimension | GameCrew Studio | Browser-Only AI Generators | IDE Coding Assistants Alone | Standalone 3D / Audio AI Tools | | --- | --- | --- | --- | --- | | **Game engines & runtime** | Real Unity 6 URP (C#), Godot 4 (GDScript/.tscn), Three.js (TS) & Pulse projects | Single-page HTML canvas or locked proprietary web wrapper | Whichever engine you install, configure, and maintain locally | None — outputs raw mesh, image, or audio files only | | **3D models, rigging & audio** | End-to-end concept art, rigged animated FBX/GLB LODs, PBR normal/roughness maps, mastered audio & CC0 library | 2D sprites, primitive shapes, or unrigged static placeholders | Code-only unless paired with external asset pipelines (such as GameCrew MCP) | Generates isolated assets; manual decimation, rigging, PBR synthesis & engine import | | **Automated verification** | Engine compile, scene transform scan, automated playtests, headless Chrome boot & emulated WebXR headset check | Usually none — runtime errors surface when you open the preview | Runs tests only if you build and maintain the engine test harness yourself | Not applicable | | **Browser, mobile & VR play** | Instant unguessable share link for desktop, phone touch & WebXR VR headsets, plus standalone Unity desktop builds | Desktop browser link inside the host platform | Manual local export and static hosting setup | Not applicable | | **Source ownership & lock-in** | Full creator ownership; one-click clean git project (.zip) and self-contained web build (.tar.gz) exports | Often locked to platform hosting or tangled single-file generated bundles | Full local git ownership | File downloads vary by provider licence | | **Coding assistant workflow** | Built-in 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code (`all` and `assets` scopes) | Prompt box only; no file-level IDE or MCP workspace access | Native local editor workflow (connects directly to GameCrew MCP) | Web UI or separate REST APIs per asset type | | **Collaboration, forking & shared craft** | Forks, verified cross-creator merge requests, shared 3D/PBR & engine technique commons, multiplayer rooms, and downstream adoption rewards | Copy-paste forks with no build verification or upstream merge flow | Manual git hosting and custom CI required per repo | Isolated download folders with manual attribution and integration | ## Detailed vendor comparisons - **[GameCrew vs Tesana](https://gamecrew.ai/compare/tesana)** ([Markdown](https://gamecrew.ai/compare/tesana.md)) — Prompt-to-game studio and web/iOS community arcade with Godot export — compared on 4-engine support, 3D rigging, WebXR VR, automated playtests and MCP. - **[GameCrew vs Google Labs Playground & Project Genie](https://gamecrew.ai/compare/google-playground)** ([Markdown](https://gamecrew.ai/compare/google-playground.md)) — Google Labs’ casual browser game maker and DeepMind’s Project Genie world model — compared with deterministic Unity 6, Godot 4, Three.js and WebXR repos. - **[GameCrew vs Rive](https://gamecrew.ai/compare/rive)** ([Markdown](https://gamecrew.ai/compare/rive.md)) — Rive’s state-machine runtime and headless AI CLI (.riv, Luau) — compared and paired with GameCrew’s cloud 3D worlds, rigging, audio and WebXR builds. - **[GameCrew vs Rosebud AI & Astrocade](https://gamecrew.ai/compare/rosebud-ai)** ([Markdown](https://gamecrew.ai/compare/rosebud-ai.md)) — Browser JavaScript vibe-coding (Rosebud AI) and social arcade / MCP creation (Astrocade) — compared with verified Unity 6, Godot 4, Three.js, contributor merges and WebXR. - **[GameCrew vs Bezi](https://gamecrew.ai/compare/bezi)** ([Markdown](https://gamecrew.ai/compare/bezi.md)) — Bezi’s local Unity Editor sidekick — compared and paired with GameCrew’s zero-install cloud Unity 6 / Godot 4 / Three.js studio, 3D/audio pipeline and MCP. - **[GameCrew vs Ludo.ai](https://gamecrew.ai/compare/ludo-ai)** ([Markdown](https://gamecrew.ai/compare/ludo-ai.md)) — Ludo.ai’s market research, GDDs and standalone asset generator — compared and paired with GameCrew’s end-to-end playable engine builds and rigging pipeline. - **[GameCrew vs Summer Engine](https://gamecrew.ai/compare/summer-engine)** ([Markdown](https://gamecrew.ai/compare/summer-engine.md)) — Browser-first AI game authoring in Summer Engine — compared with GameCrew’s multi-engine Unity 6 / Godot 4 / Three.js exports, 3D rigging, WebXR and collaborative merge requests. - **[GameCrew vs Spline AI](https://gamecrew.ai/compare/spline-ai)** ([Markdown](https://gamecrew.ai/compare/spline-ai.md)) — Spline’s interactive 3D web canvas and AI texture/object tools — compared with GameCrew’s full game loops, C#/GDScript engines, rigging and playtest verification. - **[GameCrew vs Unity AI & Muse](https://gamecrew.ai/compare/unity-ai)** ([Markdown](https://gamecrew.ai/compare/unity-ai.md)) — Unity’s native Muse / Assistant features inside the local Unity Editor — compared with GameCrew’s zero-install cloud Unity 6 studio, automated playtests and MCP. - **[GameCrew vs GDevelop AI](https://gamecrew.ai/compare/gdevelop-ai)** ([Markdown](https://gamecrew.ai/compare/gdevelop-ai.md)) — GDevelop’s no-code event sheets and AI game builder — compared with GameCrew’s real C# / GDScript / TypeScript codebases, 3D rigging pipeline and automated verification. - **[GameCrew vs GrowBlocks](https://gamecrew.ai/compare/growblocks)** ([Markdown](https://gamecrew.ai/compare/growblocks.md)) — A browser multiplayer game hub with a JavaScript Dev Kit, built-in accounts, SEED and on-chain NFTs: compared with GameCrew’s four engines, owned source and verified merge requests. ## Choosing the right workflow - **Choose GameCrew Studio (alone or paired with Claude Code / Cursor via MCP)** when you want playable 3D or 2D browser, mobile, desktop, or WebXR VR games built in Unity 6, Godot 4, Three.js, or Pulse — with custom rigged 3D models, mastered audio, automated verification, instant share links, and full git source ownership. - **Pair GameCrew’s `assets` MCP token with your local IDE** when you already maintain a custom local Unreal, Unity, or Godot repository and only want on-demand concept sheets, seamless PBR textures, rigged LOD FBX/GLB models, and mastered WAV audio. - **Use a local C++ / custom netcode stack directly** when building massive authoritative multiplayer or console-certified AAA pipelines outside web/indie engine scopes. ## Comparison & evaluation FAQ ### Should I use GameCrew or an AI coding assistant like Claude Code or Cursor? You do not have to choose between them. GameCrew handles cloud Unity 6 / Godot 4 / Three.js / Pulse setup, concept art, rigged 3D characters, PBR materials, mastered audio, headless playtests, and instant share links, while exposing a 91-tool Streamable HTTP MCP server so Claude Code, Cursor, or VS Code can read and edit scripts directly. ### How is GameCrew different from browser-only AI game generators? Browser-only generators typically write a single HTML/JS script with basic shapes and no automated testing. GameCrew builds structured multi-file projects in Unity 6 URP, Godot 4, Three.js, or Pulse, generates rigged 3D models and mastered audio, runs automated play-mode and headless Chrome/WebXR checks before saving a version, and lets you export the clean git repository. ### When is GameCrew NOT the right fit? If you are building a massive multiplayer live-service title with custom C++ server authoritative netcode, or a console-certified Unreal Engine 5 AAA pipeline, start in your local engine toolchain — you can still connect an Assets-only GameCrew MCP token to generate rigged 3D props, PBR textures, and WAV audio. ### Can I start a game in GameCrew and continue developing it locally in Unity 6 or Godot 4? Yes. Every verified version is a standard git tag. Download the Unity 6 URP (.zip) or Godot 4 (.zip) project archive at any point and open it directly in the official Unity Editor or Godot 4 Editor on your own machine with zero proprietary runtime dependencies. ### Does GameCrew track open-licence attributions automatically when reusing community 3D models or music? Yes. Whenever a build uses curated CC0 or CC BY assets from Poly Haven, AmbientCG, KayKit, or Incompetech alongside bespoke generated assets, GameCrew records SHA-256 provenance and writes Assets/Game/Resources/credits.json automatically. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- ## Vendor-by-Vendor Architectural Comparisons # GameCrew vs Tesana: AI game studio comparison > Both GameCrew and Tesana (often searched as Tessana) turn plain-English prompts into playable 2D and 3D games. Tesana centers on a consumer web and iOS arcade with Godot export, while GameCrew builds across four engines (Unity 6 URP, Godot 4, Three.js, and Pulse) with rigged 3D characters, automated playtest and WebXR VR verification, and a 91-tool MCP server. - **Canonical URL:** https://gamecrew.ai/compare/tesana - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Prompt-to-Game Studio - **Also searched as:** also searched as Tessana ## What Tesana is Tesana is a prompt-to-game studio and social arcade on the web and iOS where creators describe 2D or 3D game ideas, iterate through studio chat, publish to a shared community feed, and export Godot projects. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Tesana | | --- | --- | --- | | **Game engines & runtimes** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TypeScript + BVH) & Pulse | Browser & mobile runtime with Godot project export | | **3D character rigging, LODs & PBR** | Bespoke 3D meshes, humanoid rigging & multi-clip animations, FBX/GLB LODs, PBR normal/roughness maps & CC0/CC BY library | Prompt-driven 2D and 3D scene generation inside the studio chat loop | | **Audio pipeline** | Generated SFX, ambient loops & music mastered to target loudness, plus attributed open-licence tracks | Built-in prompt-generated game audio | | **Automated verification gates** | Engine batch compile, scene transform scan, automated play-mode tests, headless Chrome boot & emulated WebXR headset check before saving | Interactive preview and manual playtesting in the studio editor | | **Browser, mobile & VR targets** | Share links for desktop, mobile touch & WebXR VR headsets, plus standalone Unity 6 macOS/Windows/Linux builds | Web and iOS consumer arcade feed with playable community links | | **IDE & coding assistant access** | 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code (all and assets scopes) + clean git zip export | Conversational web/app studio + Godot export for local editing | ## When to choose GameCrew Studio - You want Unity 6 URP (C# and standalone desktop players), Three.js, or Pulse in addition to Godot 4. - Your game needs bespoke rigged humanoid 3D characters, baked LODs, PBR normal/roughness maps, and open-licence attribution tracking. - You want every version compiled and playtested automatically — including emulated WebXR VR headset checks — before you open it. - You want to pair AI generation with Claude Code, Cursor, or VS Code over Streamable HTTP MCP. ## When Tesana is a strong fit - You want an iOS app and built-in consumer social feed where players browse and fork community-made games. - Your workflow is casual chat-only iteration aimed at publishing into a shared mobile arcade. - You prefer a consumer arcade discovery feed over unguessable standalone share links and developer MCP tooling. ## Using GameCrew and Tesana together Because both platforms support standard Godot projects, creators evaluating Godot workflows can compare how each studio structures .tscn scenes and GDScript — or connect GameCrew’s 14-tool assets MCP token inside a local Godot 4 editor to generate rigged GLB characters, seamless PBR textures, and mastered WAV audio. ## Frequently asked questions ### Is Tessana the same as Tesana? Yes — people frequently search for “Tessana” when looking for Tesana, the prompt-to-game studio and web/iOS game arcade. This architectural comparison covers Tesana alongside GameCrew. ### Does GameCrew export Unity 6 as well as Godot 4? Yes. GameCrew builds native projects in four engines: Unity 6 (Universal Render Pipeline C#, downloadable Unity project zip, WebGL, and standalone macOS/Windows/Linux builds), MIT-licensed Godot 4 (.tscn + GDScript), Three.js (TypeScript), and Pulse. ### Can GameCrew build VR games? Yes. GameCrew builds dual-mode WebXR VR games in Three.js, Godot 4 and Unity 6 that run directly in Meta Quest Browser, Apple Vision Pro, Pico, and PC VR browsers while remaining playable flat on phones and desktops from the same link. ### Can I edit a GameCrew game in Claude Code or Cursor? Yes. GameCrew includes a hosted 91-tool Streamable HTTP MCP server so Claude Code, Cursor, or VS Code can inspect engine APIs, edit scripts, generate 3D/audio assets, and run cloud verification with zero local engine install. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Google Labs Playground & Project Genie > Google explores AI games from two angles: Google Labs Playground for casual no-code browser mini-games and forks, and DeepMind Project Genie (Genie 3) for neural world-model exploration. GameCrew builds deterministic, rule-bound, exportable games in Unity 6, Godot 4, Three.js, and Pulse that you own as clean git repositories. - **Canonical URL:** https://gamecrew.ai/compare/google-playground - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Browser Fork & World Models - **Also searched as:** Google AI game maker & Genie 3 world models ## What Google Labs Playground & Project Genie is Google Labs Playground is an experimental conversational browser game maker focused on quick arcade forks and leaderboards, while DeepMind’s Project Genie generates real-time interactive 3D video environments frame by frame using a neural world model rather than traditional game engine code. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Google Playground / Genie | | --- | --- | --- | | **Core architecture** | Deterministic multi-file game engine code (Unity 6 C#, Godot 4 GDScript, Three.js TS, Pulse) | Casual browser mini-game scripts (Playground) or frame-by-frame neural world simulation (Project Genie) | | **Source code & project export** | Full creator-owned git project archive (.zip), standalone desktop builds & self-contained web bundles (.tar.gz) | Hosted inside Google Labs / research prototypes; no Unity 6 or Godot 4 project export | | **Rules, scoring & persistence** | Exact C#/GDScript/TS physics, state machines, multi-area progression, inventories & deterministic win/lose rules | Lightweight arcade loops (Playground) or short-horizon neural environment exploration without authored scripts (Genie) | | **3D assets, rigging & audio** | Exportable FBX/GLB meshes, humanoid rigging & animations, PBR normal/roughness maps & mastered WAV audio | 2D/browser assets in Playground; implicit neural pixels in Project Genie (no exportable 3D meshes) | | **Automated verification** | Engine compile, scene scan, automated playtests, headless Chrome boot & emulated WebXR VR headset checks | Interactive browser preview | | **WebXR VR & developer MCP** | Dual-mode WebXR VR headset builds + 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code | Flat browser experiments with no IDE or MCP workspace API | ## When to choose GameCrew Studio - You want a real game project you own and can ship on itch.io, Steam, your own domain, mobile web, or Meta Quest / Vision Pro WebXR. - Your game needs persistent rules, combat, physics, multi-area progression, rigged 3D characters, and repeatable frame rates on consumer devices. - You want clean C#, GDScript, or TypeScript source code you can open in Unity 6, Godot 4, or VS Code — or steer via MCP. ## When Google Labs Playground & Project Genie is a strong fit - You want zero-friction casual browser mini-game forking and built-in experiment leaderboards inside Google Labs Playground. - You are exploring frontier neural world models that synthesize visual scenes on the fly without writing engine code (Project Genie). - You are making a quick disposable browser experiment rather than an exportable commercial or indie game repository. ## Frequently asked questions ### What is the difference between a neural world model (Project Genie) and a GameCrew engine build? A neural world model like DeepMind’s Project Genie predicts interactive video frames on cloud accelerators without generating underlying 3D meshes, colliders, or scripts. GameCrew writes real Unity 6, Godot 4, Three.js, or Pulse code with explicit physics, rigged FBX/GLB assets, and deterministic rules that run locally in any browser or desktop player at zero per-minute inference cost. ### Can you export Unity 6 or Godot 4 source code from Google Labs Playground? Google Labs Playground is designed for hosting and forking casual browser experiments inside Google Labs rather than exporting native Unity or Godot repositories. GameCrew exports full git-tagged Unity 6 URP, Godot 4, Three.js, and Pulse project archives on every saved version. ### Who owns the games created in GameCrew? You own the game-specific code, scenes, and generated assets you build in GameCrew, and you can download both the full source archive (.zip) and self-contained web or desktop builds (.tar.gz) at any time. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Rive: 3D game studio vs interactive runtime > Rive has evolved from interactive vector state machines into an agent-friendly runtime and headless CLI (.riv single-file builds with RML and Luau scripts). Rive excels at crisp vector UI, HUDs, and compact state-driven 2D interactives, while GameCrew builds full 3D worlds, rigged humanoid characters, PBR materials, mastered audio, and verified Unity 6, Godot 4, Three.js, Pulse, and WebXR VR games. - **Canonical URL:** https://gamecrew.ai/compare/rive - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Agent-Native UI & Runtime - **Also searched as:** Rive Engine, Rive AI CLI & .riv runtime ## What Rive is Rive is a real-time interactive design and runtime platform powered by state machines, vector graphics, Luau scripting, and a headless CLI that lets coding agents generate and screenshot compact .riv files for apps, websites, and game UIs. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Rive (Engine & CLI) | | --- | --- | --- | | **Primary focus** | End-to-end 3D & 2D games, multi-area worlds, 3D physics, rigged characters, audio & WebXR VR | Interactive vector graphics, state-machine UI/HUDs, motion systems & compact .riv 2D/2.5D experiences | | **Engines & scripting** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TypeScript) & Pulse | Rive Renderer & .riv format with RML markup, Luau scripts & WGSL shaders | | **3D models, rigging & audio** | Generates 3D meshes, humanoid armatures & animation clips, FBX/GLB LODs, PBR maps & mastered WAV SFX/music | 2D vector bones/meshes and imported assets; does not generate rigged 3D FBX/GLB characters or audio | | **Agent & CLI / MCP workflow** | Zero-install cloud Streamable HTTP MCP server (91 tools) + autonomous cloud studio AI crew | Local Rive Editor & headless Rive CLI paired with local coding agents | | **Automated verification** | Cloud engine compile, automated play-mode tests, headless Chrome boot & emulated WebXR VR headset checks | Local headless CLI rendering, console checks & frame screenshot capture | | **VR & standalone targets** | Browser desktop/mobile share links, Meta Quest / Vision Pro WebXR VR & standalone Unity 6 desktop builds | Embeddable .riv runtime across web, iOS, Android, Flutter, React, Unity & Unreal | ## When to choose GameCrew Studio - You are building a complete 3D (or 2D) game with 3D physics, third- or first-person cameras, multi-area environments, AI enemies, and spatial audio. - You need generated concept art, rigged humanoid 3D characters, PBR normal/roughness maps, sound effects, and looping music in one cloud workflow. - You want dual-mode WebXR VR headset support or native Unity 6 URP / Godot 4 / Three.js source repositories with zero local toolchain install. ## When Rive is a strong fit - You are designing ultra-crisp vector animations, reactive app UI, interactive mascots, or lightweight .riv embeds. - You need a state-driven HUD, menu, or motion design system to embed inside an existing iOS, Android, React, Flutter, or desktop app. - Your project is centered on 2D vector art and Luau state machines rather than 3D scene hierarchies and rigidbody physics. ## Using GameCrew and Rive together Rive and GameCrew complement each other cleanly: GameCrew exports standard Unity 6 URP, Godot 4, and TypeScript/Three.js repositories, so you can build your 3D world, rigged characters, audio, and gameplay loop in GameCrew and layer Rive’s web or Unity runtime on top for vector HUDs and animated menus. ## Frequently asked questions ### Is Rive a replacement for Unity, Godot, or GameCrew? For reactive UI, motion graphics, and compact 2D vector games, Rive’s runtime can stand on its own. For 3D worlds with triangle-mesh physics, rigged 3D characters, PBR lighting, generated audio, and WebXR VR, GameCrew builds full Unity 6, Godot 4, Three.js, and Pulse projects. ### How does Rive’s AI CLI compare to GameCrew’s MCP server? Both embrace agentic verification — compiling and capturing real frames instead of guessing. Rive’s CLI runs locally against .riv files, while GameCrew’s 91-tool Streamable HTTP MCP server runs Unity 6, Godot 4, Three.js, Pulse, 3D rigging, and headless Chrome/WebXR checks in the cloud with zero local installs. ### Can I use Rive menus inside an exported GameCrew project? Yes. Because GameCrew exports clean, standard Unity 6 (C#), Godot 4, and TypeScript web projects with full creator ownership, you can integrate Rive’s official web or Unity runtimes for HUDs and title screens after exporting. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Rosebud AI & Astrocade > Rosebud AI popularized browser-based vibe-coding for JavaScript web games, while Astrocade blends a social arcade feed and community jams with mcp.astrocade.com creation workflows. GameCrew focuses on verified multi-file engineering in Unity 6 URP, Godot 4, Three.js, and Pulse — complete with rigged 3D models, mastered audio, WebXR VR checks, clean git export, and pull-request-style contributor merge requests. - **Canonical URL:** https://gamecrew.ai/compare/rosebud-ai - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Browser Vibe-Coding & Arcade - **Also searched as:** browser vibe-coding & AI social arcades ## What Rosebud AI & Astrocade is Rosebud AI is a browser prompt-to-code platform generating JavaScript (Three.js and Phaser) web games and assets, while Astrocade is an AI social arcade platform with community forking, jams, and an MCP creation server (mcp.astrocade.com) targeting its arcade runtime. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Rosebud AI / Astrocade | | --- | --- | --- | | **Supported engines** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TypeScript) & Pulse | Browser JavaScript frameworks (Rosebud AI) or platform-hosted social arcade runtime (Astrocade) | | **Automated verification before preview** | Every version passes engine compile, scene scan, automated playtests, headless Chrome boot & WebXR checks before saving | Live browser preview; broken scripts or runtime exceptions are often debugged manually via chat | | **Collaboration & contributor quality control** | Forks, verified cross-creator merge requests merged by owners, shared 3D/PBR library & rewards for genuine downstream adoption | Open casual feed forks and community game jams | | **3D models, rigging & PBR** | Bespoke 3D meshes, humanoid rigging & animation contact sheets, FBX/GLB LODs, PBR maps & CC0/CC BY library | 2D sprite sheets, skyboxes, or static/template 3D assets | | **VR headset support** | Dual-mode WebXR VR (Enter VR) in Three.js, Godot 4 and Unity 6, verified in an emulated headset | Flat desktop and mobile screens | | **Standalone & git export** | Clean git repository (.zip), self-contained web bundle (.tar.gz) & standalone Unity 6 desktop players | Web code export/hosting (Rosebud AI); platform-hosted social feed (Astrocade) | | **External IDE / MCP integration** | 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code (all and assets scopes) | In-browser chat editor (Rosebud AI) and Astrocade MCP server (mcp.astrocade.com) | ## When to choose GameCrew Studio - You want a studio where every version must pass automated compile, playtest, and headless browser checks before anyone plays or merges it. - You want native Unity 6 URP (C#) or Godot 4 (GDScript) projects and standalone desktop downloads in addition to Three.js web builds. - You want creators and agents to collaborate via verified merge requests, shared engine techniques, and reusable 3D/PBR craft. - You need rigged animated 3D characters, synthesized PBR normal/roughness maps, mastered audio, or WebXR VR headset support. ## When Rosebud AI & Astrocade is a strong fit - You want an instant in-browser JavaScript scratchpad to fork existing community Phaser or Three.js snippets (Rosebud AI). - You want a casual consumer social feed, jam challenges, and agent connection tailored to publishing short arcade games inside Astrocade. - You only need quick browser prototypes without Unity/Godot scene trees or automated playtest gates. ## Frequently asked questions ### Why do vibe-coded browser games often break as they grow, and how does GameCrew prevent that? Raw chat-to-JavaScript tools typically overwrite long script files without running automated gameplay tests, so fixing a camera or enemy often introduces a silent runtime crash. GameCrew structures projects cleanly under git and gates every saved version on compiler checks, scene scans, automated play-mode tests, and headless Chrome boot. ### Can GameCrew build Three.js browser games AND Unity/Godot games? Yes. When you want a fast-loading 3D web or WebXR game, GameCrew builds in TypeScript + Three.js (with three-mesh-bvh collision and compressed glTFs). When your game fits Godot 4 or Unity 6 URP better, GameCrew builds natively in those engines from the same studio. ### Do I need to host my game on GameCrew? No. GameCrew gives every verified version an instant desktop, mobile, and WebXR share link for convenience, and you can download the self-contained web build (.tar.gz) or full engine source (.zip) at any time to host on itch.io, Cloudflare Pages, Steam, or your own site. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Bezi: cloud AI studio vs local Unity agent > Bezi is a project-aware AI assistant that plugs into a locally installed Unity Editor to edit scripts, scenes, and prefabs on your workstation. GameCrew runs the entire studio in the cloud with zero local installs — generating concept art, rigged 3D FBX/GLB models, PBR textures, and mastered audio while compiling and playtesting across Unity 6, Godot 4, Three.js, and Pulse. - **Canonical URL:** https://gamecrew.ai/compare/bezi - **Comparison hub:** https://gamecrew.ai/compare - **Category:** In-Editor Unity AI Agent - **Also searched as:** in-editor local Unity AI co-pilot ## What Bezi is Bezi is a desktop co-pilot integrated directly with the Unity Editor on your machine, indexing your local C# scripts, scenes, and prefabs so you can inspect or modify an existing local Unity project. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Bezi | | --- | --- | --- | | **Local setup required** | Zero install — runs in any desktop, laptop, tablet, or phone browser (plus remote HTTP MCP for IDEs) | Requires Unity Hub, a matching local Unity Editor install, local workstation hardware & companion app | | **Supported game engines** | Unity 6 URP, Godot 4, Three.js & Pulse (including browser WebXR VR) | Focused on locally installed Unity projects | | **3D models, rigging & audio** | Built-in concept art, 3D mesh generation, humanoid rigging & animations, PBR maps, mastered audio & CC0 library | Manipulates assets already in your Unity project; relies on external tools for bespoke 3D rigging & audio | | **Automated cloud verification** | Headless Unity batch compile, SceneScan, EditMode & PlayMode tests, and headless Chrome WebGL boot | Interactive validation and checkpoints inside your open local Unity Editor | | **Sharing & publishing** | One-click browser/mobile share links, WebGL bundles, standalone desktop builds & clean Unity 6 project zips | Manual local Unity build and hosting workflow | | **External coding assistants** | Standard 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code (all and assets scopes) | Dedicated Bezi desktop/editor interface | ## When to choose GameCrew Studio - You want to go from a plain-English idea to a playable, shareable game without installing gigabytes of Unity Editor packages locally. - You need bespoke 3D models, automated humanoid rigging, PBR textures, sound effects, and looping music generated alongside the C# code. - You want the flexibility to target Godot 4, Three.js, Pulse, or browser WebXR VR in addition to Unity 6 URP. - You prefer using Claude Code, Cursor, or VS Code connected to a cloud Unity/Godot/Three.js workspace over standard MCP. ## When Bezi is a strong fit - You already maintain a large, multi-year Unity repository on a local workstation with custom third-party Asset Store plugins. - You work full-time inside the local Unity Editor GUI and want a Unity-specific chat sidekick docked next to your Inspector. - Your project targets native console SDKs or custom local editor tooling outside web and desktop scopes. ## Using GameCrew and Bezi together GameCrew and Bezi fit cleanly into a two-stage Unity workflow: generate your initial Unity 6 URP vertical slice (complete with C# scripts, rigged FBX prefabs, PBR materials, and mastered audio) in GameCrew, download the clean Unity 6 .zip archive, and open it in your local Unity Editor with Bezi — or keep GameCrew’s 14-tool assets MCP token connected to generate new rigged 3D props and audio on demand. ## Frequently asked questions ### Do I need Unity 6 installed on my computer to build a Unity game in GameCrew? No. GameCrew runs Unity 6 URP in its own cloud sandbox — compiling C#, scanning scene transforms, running EditMode and PlayMode tests, and exporting WebGL and standalone desktop players — so you can create or steer builds from any browser or lightweight laptop. ### Can I open a GameCrew Unity project inside the official Unity 6 Editor (and use Bezi on it)? Yes. Every saved version of a Unity game in GameCrew exports as a clean, standard Unity 6 URP project .zip (Assets/Game/, ProjectSettings/, Packages/) with zero proprietary lock-in, ready to open in Unity Hub. ### Can my local Unity team use GameCrew just for rigged 3D models, PBR textures, and audio? Yes. Create an Assets-only MCP token (scope: assets) in GameCrew to expose 14 asset-pack tools (make_model, make_texture, make_sound, get_importer, and CC0/CC BY library search) and search and read of the technique library directly inside your local Unity workflow. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Ludo.ai: playable studio vs ideation & assets > Ludo.ai helps designers research market trends, draft Game Design Documents (GDDs), and generate standalone 2D, 3D, and audio assets. GameCrew takes the next step: turning a game brief into concept art, rigged 3D models, PBR textures, mastered audio, AND a compiled, automatically playtested playable game in Unity 6, Godot 4, Three.js, or Pulse. - **Canonical URL:** https://gamecrew.ai/compare/ludo-ai - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Ideation, GDDs & Assets - **Also searched as:** AI game ideation, market research & asset generator ## What Ludo.ai is Ludo.ai is a pre-production and asset platform for game creators, offering store and market intelligence, concept brainstorming, interactive GDD editors, and standalone sprite, 3D model, and sound generation for export into external engines. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Ludo.ai | | --- | --- | --- | | **End-to-end playable game output** | Yes — builds, compiles, playtests & hosts playable desktop, mobile & WebXR VR games | Pre-production documents, lightweight prototypes & standalone raw assets for external assembly | | **Real game engines** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TypeScript) & Pulse | Engine-agnostic docs and asset downloads (you assemble the engine project separately) | | **Market & competitor analytics** | Focused on structured game pitches, visual moodboards & building playable slices (no store chart scraper) | Built-in mobile/Steam market trend search, competitor analysis & chart research | | **3D asset readiness** | Automated decimated LODs, humanoid rigging & multi-clip animation contact sheets, PBR normal/roughness maps & Unity importer | Standalone 3D mesh and 2D sprite exports | | **Automated verification** | Engine compile, scene scan, automated play-mode tests, headless Chrome boot & emulated WebXR VR checks | Not applicable to standalone GDDs and raw asset exports | | **MCP coding assistant workflow** | 91-tool Streamable HTTP MCP server (all and 14-tool assets scopes) for Claude Code, Cursor & VS Code | Web dashboard & MCP/API integrations focused on ideation and standalone assets | ## When to choose GameCrew Studio - You want an actual playable, verified game at the end of the session — not just a design document or a folder of unrigged meshes. - You need characters rigged with humanoid armatures and verified animation clips, synthesized PBR maps, and mastered audio wired directly into scenes. - You want instant desktop, mobile touch, and WebXR VR share links plus clean Unity 6, Godot 4, Three.js, or Pulse git source. ## When Ludo.ai is a strong fit - You are in early market discovery and want to analyze store charts, genre trends, and competitor titles before choosing a concept. - Your team wants a standalone browser workspace dedicated to collaborative Game Design Documents and pitch research. - You only need quick standalone concept images or voice clips without automated engine builds. ## Using GameCrew and Ludo.ai together Many creators pair market research with production: validate a genre hook or audience gap in Ludo.ai, then paste your favorite two-paragraph concept into GameCrew’s free pitch generator (or full studio) to turn that concept into playable Unity 6, Godot 4, Three.js, or WebXR VR vertical slices. ## Frequently asked questions ### Does GameCrew also generate a structured game design pitch before building? Yes — and you can try it for free on the GameCrew home page with no sign-up. In about two minutes, GameCrew writes a structured pitch (logline, player role, core mechanics, stages, and desktop/phone/VR control table) alongside three visual moodboards before building the playable game. ### How does GameCrew’s 3D asset pipeline differ from standalone 3D generators? Raw AI 3D meshes are usually high-poly, unrigged, and missing roughness/normal maps. GameCrew automatically decimates meshes into LOD chains, synthesizes seamless PBR normal and roughness maps, rigs humanoid characters with verified multi-clip animations, and imports prefabs directly into Unity 6, Godot 4, or Three.js. ### Can I use GameCrew’s rigged 3D and audio generator inside my own existing project? Yes. Generate an assets-scoped MCP token (scope: assets) to call make_concept_art, make_model, make_texture, make_sound, search_library, and get_importer directly from Claude Code, Cursor, or VS Code inside any local repository. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Summer Engine: multi-engine studio vs browser engine > Summer Engine builds interactive 3D worlds and casual games directly inside a prompt-driven web workspace. GameCrew compiles and verifies clean git projects across four standard engines — Unity 6 URP, Godot 4, Three.js, and Pulse — complete with rigged 3D characters, mastered audio, WebXR VR headset checks, and collaborative contributor merge requests. - **Canonical URL:** https://gamecrew.ai/compare/summer-engine - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Browser AI Game Engine - **Also searched as:** browser-first AI engine for 3D web worlds ## What Summer Engine is Summer Engine is a browser-based AI game creation platform designed for rapidly generating, tweaking, and publishing playable 3D and casual web experiences inside its hosted editor. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Summer Engine | | --- | --- | --- | | **Target engines & source exports** | Standard Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TS) & Pulse clean git archives (.zip) | Managed web runtime centered on browser play inside the Summer workspace | | **Automated quality & verification** | Engine batch compile, scene transform checks, automated playtests, headless Chrome boot & emulated WebXR verification before saving | Interactive browser preview tuned inside the web canvas | | **3D rigging, PBR & audio** | Bespoke meshes, humanoid rigging & multi-clip animations, seamless PBR normal/roughness maps, mastered WAV audio & CC0 library | Integrated prompt-driven scene, world and asset generation for web play | | **Collaboration & contributor merges** | Forks, verified cross-creator merge requests (`open_merge_request`), shared engine techniques & adoption rewards | Individual project authoring and shareable play links | | **Coding assistant MCP access** | 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code (all and assets scopes) | Web-based prompt & visual editor | ## When to choose GameCrew Studio - You want to export clean Unity 6 URP, Godot 4, Three.js, or Pulse repositories you can open offline in standard editors with zero runtime lock-in. - You require automated compile, playtest, and emulated WebXR VR headset verification before every saved version ships. - You want contributors and their coding assistants to collaborate through forks and verified merge requests. ## When Summer Engine is a strong fit - You prefer authoring visual 3D web scenes inside a single browser workspace without thinking about Unity or Godot project structures. - Your priority is quick single-session web scene iteration inside a hosted browser runtime. - You do not need downloadable C# or GDScript desktop projects or local IDE MCP workflows. ## Frequently asked questions ### Can I download full Unity or Godot projects from GameCrew? Yes. Every verified build in GameCrew is tagged in git and exports as a complete Unity 6 URP, Godot 4, Three.js, or Pulse project archive ready for local editors or desktop distribution. ### How does GameCrew keep collaborative forks from shipping broken builds? Every merge request submitted by a contributor or coding assistant must pass automated compile, playtest, and browser boot verification on the fork branch before the owner reviews and merges it. ### Does GameCrew support WebXR VR headsets as well as flat web play? Yes. Three.js, Godot 4, and Unity 6 builds can target WebXR so the exact same share link plays on phones, desktops, and standalone VR headsets. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Spline AI: full game studio vs 3D design canvas > Spline (and Spline AI) excels at interactive 3D web graphics, hero embeds, spline modeling, and state transitions for web designers. GameCrew builds complete playable games — enemy AI, physics, inventories, rigged animated characters, mastered sound, multiplayer rooms, and automated playtests — across Unity 6 URP, Godot 4, Three.js, and Pulse. - **Canonical URL:** https://gamecrew.ai/compare/spline-ai - **Comparison hub:** https://gamecrew.ai/compare - **Category:** 3D Web Design & Interactive Scenes - **Also searched as:** interactive 3D web design & Hana tool ## What Spline AI is Spline is a collaborative browser-based 3D design tool for creating interactive web graphics, UI embeds, physics toys, and AI-assisted 3D objects and textures aimed primarily at product and web designers. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Spline AI | | --- | --- | --- | | **Primary strength** | End-to-end playable games: design pitch, combat/gameplay scripts, rigged characters, spatial audio & automated playtests | Interactive 3D web design scenes, spline modeling, camera states & lightweight website embeds | | **Game engines & exported code** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TS) & Pulse clean git archives | Spline web runtime embeds plus standard Three.js / React embeds and 3D file exports | | **Gameplay verification & playtesting** | Engine compile, automated play-mode assertions, headless Chrome boot & emulated WebXR VR headset verification | Visual canvas viewport and real-time design preview | | **3D rigging & audio pipeline** | Humanoid armature rigging, animation contact sheets, LOD decimation, PBR maps & mastered SFX/music | Design-first 3D modeling, generative textures/objects and visual state animations | | **Coding assistant & collaboration flow** | 91-tool Streamable HTTP MCP server, forks, verified contributor merge requests & craft adoption rewards | Figma-like multiplayer visual viewport for 3D designers | ## When to choose GameCrew Studio - You are building an actual game with multi-area progression, scoring, physics, AI opponents, soundtracks, and win/loss states rather than a 3D product hero. - You want clean Unity 6 C#, Godot 4 GDScript, or structured Three.js TypeScript game code backed by automated play-mode tests. - You want rigged animated 3D game characters paired with synthesized audio and WebXR VR controller tracking. ## When Spline AI is a strong fit - You are a web or product designer crafting interactive 3D marketing heroes, UI transitions, or custom geometric models in a visual viewport. - You want Figma-style real-time synchronous cursor collaboration on visual materials, lighting, and hover states. - Your deliverable is an embedded interactive 3D component inside a React or Webflow marketing site rather than a multi-stage game. ## Using GameCrew and Spline AI together Design teams can craft bespoke hero props or sculptural 3D logos in Spline, or connect GameCrew’s `assets`-scoped MCP server alongside a clean exported Three.js or Unity 6 repository so GameCrew handles gameplay systems, audio, and automated verification while Spline shines on custom vector-extruded web design. ## Frequently asked questions ### Can Spline replace Unity 6 or Godot 4 for full games? Spline is built for interactive web design graphics and lighter game prototypes, whereas complex camera rigs, combat state machines, rigged humanoid animation controllers, and desktop builds are naturally at home in Unity 6, Godot 4, or structured Three.js projects generated by GameCrew. ### Does GameCrew generate game audio as well as 3D models? Yes. GameCrew generates and loudness-masters sound effects, ambient loops, and music alongside rigged 3D models and seamless PBR textures, while also crediting CC0/CC BY library assets. ### Can I edit a GameCrew Three.js build in VS Code or Cursor? Yes. Connect Cursor, Claude Code, or VS Code via Streamable HTTP MCP to edit scripts live or download the clean TypeScript + Vite source archive at any time. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs Unity AI & Unity Muse > Unity’s built-in AI tools (including Unity Muse and Unity Assistant) help developers generate textures, sprites, chat answers, and editor actions inside a local Unity Editor installation. GameCrew runs complete Unity 6 URP builds, 3D rigging, mastered audio, WebGL export, headless PlayMode tests, and standalone desktop builds in the cloud — and exports standard Unity 6 projects you can open locally whenever you like. - **Canonical URL:** https://gamecrew.ai/compare/unity-ai - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Native Engine AI Tools - **Also searched as:** Unity Muse & Unity Assistant ## What Unity AI & Muse is Unity AI (encompassing Unity Muse and Unity Assistant inside the Unity Editor) is Unity’s official suite of in-editor generative texture, sprite, behavior, and Q&A tools designed for developers working locally in Unity Hub and the Unity Editor. ## Side-by-side architectural comparison | Capability | GameCrew Studio | Unity AI / Muse | | --- | --- | --- | | **Local Unity Editor setup** | Zero install — compiles Unity 6 URP in cloud workers from browser, phone, or MCP IDE | Requires local Unity Hub, Unity Editor download, local disk space and workstation GPU/CPU | | **Autonomous multi-stage build loop** | End-to-end pitch, architecture, C# scripting, prefab wiring, asset import, compile & PlayMode repair loop | Editor-side assistants and texture/sprite helpers steered step by step by the developer | | **3D meshes, humanoid rigging & audio** | Bespoke rigged animated FBX characters & LODs, seamless PBR maps, mastered WAV audio & Unity URP importer scripts | In-editor texture/sprite/animation helpers plus third-party Asset Store packages | | **Engine choice beyond Unity** | Unity 6 URP plus Godot 4, Three.js, Pulse and WebXR VR from the same studio | Unity Editor ecosystem only | | **Coding assistant & team workflow** | 91-tool Streamable HTTP MCP server, forks, verified merge requests & exportable git Unity 6 zips | Integrated directly in the Unity Editor interface alongside Unity Version Control / Asset Store | ## When to choose GameCrew Studio - You want to go from plain English to a compiled, PlayMode-tested, shareable Unity 6 URP game in the browser without installing Unity locally. - You want Claude Code, Cursor, or VS Code to invoke cloud Unity 6 batch builds, scene scans, PlayMode tests, and screenshot captures over MCP. - You also build browser-first Three.js, Godot 4, or Pulse games — or dual-mode WebXR VR builds — alongside Unity 6. ## When Unity AI & Muse is a strong fit - You already live inside a heavy local Unity Pro pipeline with native console SDKs, custom render pipelines (HDRP), or large Asset Store packages. - You want Unity’s native in-editor UI co-pilot working directly inside your open desktop Scene View. - Your project is exclusively built for native desktop/console Unity distribution managed locally by a dedicated Unity engineering team. ## Using GameCrew and Unity AI & Muse together Start fast in GameCrew to validate a playable Unity 6 URP prototype (complete with C# scripts, URP materials, rigged FBX characters, WAV audio, and automated PlayMode tests), then download the standard Unity 6 .zip archive and open it locally alongside Unity AI / Muse whenever your project grows into console-specific plugins. ## Frequently asked questions ### Do GameCrew Unity 6 exports work in the official local Unity 6 Editor? Yes. GameCrew exports clean standard Unity 6 URP folders (Assets/Game/, ProjectSettings/, Packages/) without proprietary lock-in, so you can open them straight in Unity Hub. ### Can I use GameCrew’s 3D rigging and audio tools in my existing local Unity project? Yes. Create an Assets-only MCP token (scope: assets) in GameCrew and call make_model, make_texture, make_sound, and get_importer from your IDE to drop ready-to-use URP prefabs, Animator clips, and audio straight into an existing Unity repo. ### How does GameCrew test Unity games without opening a local Editor window? GameCrew runs headless Unity batchmode compiles, deterministic SceneScan checks, EditMode and PlayMode test suites, and headless Chrome WebGL boot verification before marking any version ready. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs GDevelop AI: real engine code vs visual event sheets > GDevelop pairs a friendly no-code event-sheet editor with an AI assistant aimed at 2D and lightweight 3D indie games. GameCrew generates clean, standard source code in Unity 6 URP (C#), Godot 4 (GDScript), Three.js (TypeScript), and Pulse — complete with rigged 3D characters, mastered audio, WebXR VR support, automated playtest gates, and MCP access for developers. - **Canonical URL:** https://gamecrew.ai/compare/gdevelop-ai - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Visual Event-Sheet Game Maker - **Also searched as:** no-code event sheets & GDevelop AI assistant ## What GDevelop AI is GDevelop is an accessible open-source game creator built around visual condition/action event sheets and templates, augmented by an in-app AI assistant for scaffolding events, behaviors, and starter 2D/casual games. ## Side-by-side architectural comparison | Capability | GameCrew Studio | GDevelop AI | | --- | --- | --- | | **Authoring model & code ownership** | Clean git-tagged Unity 6 C#, Godot 4 GDScript/.tscn, Three.js TypeScript & Pulse source files | Visual no-code event sheets and behaviors (with optional JavaScript extensions) | | **3D capabilities, rigging & WebXR** | Full 3D worlds with URP / Three.js / Godot lighting, humanoid FBX/GLB rigging, LODs, PBR maps & dual-mode WebXR VR | Best known for 2D sprites/platformers with newer basic 3D scene features | | **Automated verification gates** | Every saved build must pass engine compile, scene transform audit, automated playtests & headless Chrome boot | Manual live preview button inside the GDevelop editor | | **Coding assistant MCP integration** | 91-tool Streamable HTTP MCP server for Claude Code, Cursor & VS Code | Built-in GDevelop AI chat inside the visual editor | | **Collaboration & shared commons** | Forks, verified cross-creator merge requests (`open_merge_request`), shared 3D/PBR assets & adoption rewards | GDevelop Asset Store, examples library and gd.games publishing portal | ## When to choose GameCrew Studio - You want clean C#, GDScript, or TypeScript source code you or an AI coding assistant can scale indefinitely without hitting visual event-sheet ceilings. - Your game relies on 3D worlds, humanoid rigged animations, seamless PBR textures, or WebXR VR headset play. - You want automated compile and playtest gates verifying every revision and contributor merge request before it ships. ## When GDevelop AI is a strong fit - You want a visual no-code event-sheet GUI designed specifically to teach 2D game logic to students or non-programmers. - You are building classic 2D arcade or mobile titles using GDevelop’s rich visual behavior plugins and gd.games hosting. - You prefer clicking together visual conditions/actions manually rather than prompting or editing C#/GDScript/TypeScript. ## Frequently asked questions ### Do I have to know how to code to use GameCrew? No. Non-coders direct everything in plain English, pin visual feedback notes straight onto screenshots, and tune live gameplay sliders without opening code — while developers get full C#, GDScript, or TypeScript access. ### How is GameCrew different for 3D games? GameCrew treats 3D as first-class across Unity 6 URP, Three.js, and Godot 4 — automatically handling mesh decimation, LOD chains, PBR normal/roughness synthesis, humanoid character rigging, and WebXR headset verification. ### Can other people help improve my GameCrew game cleanly? Yes. Contributors can make a branch of your game, test improvements in it, and send back a verified merge request — and earn bonus build credits when you merge their work. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew vs GrowBlocks: your own game vs a game in their city > GrowBlocks gives developers a JavaScript Dev Kit (three.js and Rapier physics in the browser) for coding a 3D multiplayer game with an AI coding assistant, then publishes it, after review, into GrowBlocks City, a shared browser world with its own player accounts, SEED play currency and NFTs. GameCrew builds a game of your own in Unity 6, Godot 4, Three.js or Pulse, checks every version in the engine, and gives it a play link and source you keep: made by its AI crew from a brief, or by your own coding assistant over MCP. - **Canonical URL:** https://gamecrew.ai/compare/growblocks - **Comparison hub:** https://gamecrew.ai/compare - **Category:** Multiplayer Game Hub & Dev Kit - **Also searched as:** GrowBlocks Dev Kit & GrowBlocks City ## What GrowBlocks is GrowBlocks is a free browser game hub where players move between 20+ games through one shared city, earn SEED (a play currency with no money value) and collect NFTs. Developers build games with the GrowBlocks Dev Kit: a CLI (`npx growblocks new`, `push` for an unlisted test link, `submit` for review), hosted multiplayer rooms, built-in accounts and wallets, and an MCP server for AI coding assistants. ## Side-by-side architectural comparison | Capability | GameCrew Studio | GrowBlocks | | --- | --- | --- | | **Engines & languages** | Unity 6 URP (C#), Godot 4 (GDScript / .tscn), Three.js (TypeScript) & Pulse | JavaScript on the GrowBlocks engine (three.js rendering, Rapier physics) | | **Who makes the game** | Your own coding assistant over MCP, or GameCrew’s AI crew from a plain-English brief, with art, models and sound made for the game | You and your AI coding assistant write the JavaScript; AI calls in the game go through their provided service | | **Multiplayer** | Opt-in 2–8 player rooms by 4-letter code on Quick, Godot 4 and Unity 6; exported browser builds include a standalone room server you can host | Hosted match server: rooms up to 16 players, party rooms up to 100, plus the shared city | | **Checks before players see it** | Every version compiled and tested in the engine, booted in headless Chrome, with VR and two-player checks where they apply; merges into main checked again | A headless check with a screenshot from the CLI, then a GrowBlocks review of every build and update | | **Where players find it** | An unguessable play link per version and a public game page; it runs anywhere you share it | A stand in GrowBlocks City, among the hub’s other games and players | | **Money & ownership** | Pay for the AI work you use; the game’s source is yours to download as a git repository | NFT collections on a blockchain and a fee share from them (in test currency for now); code and art stay yours, but the engine is licensed for publishing on GrowBlocks only | | **Platforms** | Desktop and phone browsers, WebXR VR headsets, and standalone Unity desktop builds | Desktop and phone browsers | | **Working with others** | Branches, forks where the owner allows them, and merge requests with before/after pictures, reviewed by the game’s crew | Reusable "blocks" other developers publish, with a share of fees going to the blocks a game uses | ## When to choose GameCrew Studio - You want the game to be yours: standard engine source in a git repository, playable from your own link, not tied to one hub. - You want Unity 6, Godot 4 or Pulse as well as Three.js, or VR headset play. - You want an AI crew to build the whole game from a brief, art and sound included, or your own assistant to work in a game that is checked in the engine at every merge. - You want your crew, or anyone you let in, to change your game through branches and merge requests you review. ## When GrowBlocks is a strong fit - You want players from day one: a shared city where people already walk between games. - You want accounts, wallets, a play currency and NFTs built into your game without building them yourself. - You are writing a JavaScript three.js game and want large hosted multiplayer rooms (up to 16, or 100 in party rooms) without running a server. ## Frequently asked questions ### Is GrowBlocks an AI game maker? Not in the same sense. GrowBlocks gives developers a JavaScript Dev Kit and docs written for AI coding assistants, and you write the game with your assistant. GameCrew can also build the whole game itself from a brief, or let your own assistant do the work over MCP. ### Can a GameCrew game have multiplayer? Yes. Quick (Three.js), Godot 4 and Unity 6 games can turn on rooms for 2–8 players joined by a 4-letter code, tested with two headless browsers before a version is saved. Exported browser builds include a small room server you can host yourself. ### Does GameCrew use crypto or NFTs? No. GameCrew has no tokens, wallets or NFTs: you pay for the AI work you use, and the game and its source are yours. _All product and company names are trademarks of their respective holders; use of them does not imply affiliation or endorsement. Architectural comparison updated 17 November 2026._ --- # GameCrew for Developers: MCP Server, Engine Workspace & Source Export > Connect Claude Code, Cursor, VS Code, or any Model Context Protocol (MCP) client to GameCrew over Streamable HTTP (`POST https://play.gamecrew.ai/mcp`) — build games, generate rigged 3D models, PBR textures, and WAV audio, run sandboxed Unity 6 / Godot 4 / Three.js / Pulse checks, and export clean git source. - **Canonical URL:** https://gamecrew.ai/developers - **MCP discovery card:** https://gamecrew.ai/.well-known/mcp.json - **Supported MCP protocol versions:** `2025-06-18`, `2025-03-26`, `2024-11-05` ## Quickstart (`mcpServers` configuration) Generate a scoped token (`gc_...`) in the GameCrew studio **Usage → Connect a coding assistant** panel and add: ```json { "mcpServers": { "gamecrew": { "type": "http", "url": "https://play.gamecrew.ai/mcp", "headers": { "Authorization": "Bearer gc_..." } } } } ``` ## Scoped access tokens (`all` vs `assets`) - **Full workspace (`all` — 91 tools):** Create and iterate games, read and edit project scripts (`C#`, `GDScript`, `TypeScript`), query offline engine APIs, run sandboxed compiles/tests/captures, manage prioritized backlogs, and publish verified Live release channels. - **Assets-only (`assets` — 14 tools):** Generate concept art, seamless PBR textures, mastered WAV sound effects/loops/music, and rigged LOD FBX/GLB 3D models for your own local Unity or Godot project, search free CC0/CC BY library assets, and download the Unity 6 URP prefab/Animator importer — without build access to your other studio games. ## MCP tool reference (91 tools) | Tool Group | Token Scope | Tools | Capabilities | | --- | --- | --- | --- | | **Studio builds & jobs** | Full (3 also in Assets) | `new_game`, `build_game`, `change_game`, `get_game`, `list_games`, `get_job`, `list_jobs`, `cancel_job`, `message_builder`, `get_screenshots`, `list_showcase`, `fork_game`, `get_limits`, `request_tier_change` | Read games, play links, camera captures, limits and the account’s tier (Contributor or Platform; request_tier_change asks an admin to move it), fork a showcase game (or one whose owner allows forks), and poll jobs up to 50 s per call. new_game, build_game, change_game and message_builder start GameCrew’s own AI crew (Unity 6, Godot 4, Three.js or Pulse, including WebXR VR) from your credits: they are listed only after the account switches the AI crew on for its assistants. | | **Branches, forks & merge requests** | Full | `create_branch`, `list_branches`, `delete_branch`, `open_merge_request`, `sync_fork`, `resolve_conflict`, `list_merge_requests`, `get_merge_request`, `comment_on_merge_request`, `review_merge_request`, `try_merge_request`, `request_changes`, `merge_merge_request`, `resolve_merge_request`, `decline_merge_request`, `withdraw_merge_request`, `get_notifications`, `set_handle` | A branch is the normal way to change a game, yours or someone else's: a working copy that belongs to the game; open a merge request into main with its verified version, bring main's newer version into the branch (three-way merge with conflict markers for the assistant to resolve, or one whole side of a file), read a merge request's files and diffs, discuss it, ask for changes, merge it (picking a side for files that collide, or having the studio's AI crew resolve the colliding lines on a budget), decline or withdraw it, and hear what happened through notifications, under a public handle. Who may branch a game is who may open a merge request to it: on a public game, anyone signed in unless its owner keeps it to the crew. A fork, a game of your own made from another, is for games whose owner allows forks (showcase games always do), and goes back the same way. | | **Games as repositories** | Full | `explore_games`, `get_repo`, `get_history`, `get_change`, `list_repo_files`, `read_repo_file`, `set_visibility`, `set_crew_member`, `list_crew_invites`, `answer_crew_invite`, `set_merge_request_policy`, `block_contributor`, `set_forks`, `set_account_forks`, `get_asset_history`, `upload_asset`, `restore_asset`, `save_assets`, `make_key_art`, `set_cover` | Treat a game as a repository: explore the studio's public games, read any game you can see (its overview, its versions as commits with their authors, each version's changed files and diffs, its tree and text files), and as its owner decide who sees it and who contributes: public or private, the crew you invite, who may make branches and open merge requests, blocked handles, and whether forks are allowed (off unless you allow them, for one game or by default for all of yours). Assets are versioned with the game: read one picture, sound or model across its versions, upload one you already have with its licence, or put an earlier one back. Key art (the picture a game is shown by) is made for a game that exists from the game itself, and its owner chooses which take is the cover. | | **3D, texture & audio asset packs** | Full & Assets-only | `new_asset_pack`, `make_concept_art`, `make_texture`, `make_sound`, `make_model`, `list_assets`, `search_library`, `use_library_asset`, `get_importer` | Generate concept art, seamless PBR textures, mastered WAV sound effects/loops/music and rigged LOD FBX/GLB 3D models, search CC0/CC BY open-licence library assets, and fetch Unity 6 URP importer scripts. | | **Live code & project inspection** | Full workspace | `work_status`, `project_map`, `engine_api`, `list_files`, `read_file`, `search_files`, `write_file`, `edit_file`, `delete_file`, `say` | Map scripts, scenes and tuning across Unity 6, Godot 4, Three.js and Pulse, look up offline engine class & member signatures, edit code directly, and post updates to the creator timeline. | | **Sandboxed engine runs & release** | Full workspace | `run_unity`, `pulse`, `get_capture`, `get_run_log`, `get_activity`, `save_version`, `discard_changes` | Run sandboxed engine compiles, scene rebuilds, EditMode/PlayMode tests, camera captures and sub-second Pulse scenario/sweep commands, read logs and screenshots, and save verified browser builds. | | **Technique library** | Full (2 also in Assets) | `search_techniques`, `read_technique`, `contribute_technique`, `share_technique`, `suggest_technique_revision`, `list_technique_suggestions`, `answer_technique_suggestion`, `withdraw_technique_suggestion`, `report_technique` | Search and read engine-specific technique guides (graphics, game feel, AI, VR) before building something hard, write guides your own account owns, ask for one to be shared with every builder after a review, and suggest revisions to other people's guides. | | **Game operations, Live channel & AI triage** | Full workspace | `get_game_health`, `manage_backlog`, `promote_version`, `triage_game` | Inspect 0–100 game health scores, 6 release-readiness gates and deterministic project audits, manage prioritized p0/p1/p2 backlogs, promote versions to stable /play/ Live channels, and run AI Game Manager triage. | ## Clean git source & standalone build exports - **Unity 6 (URP):** Complete Unity 6 project `.zip` (`Assets/Game/`, C# scripts, URP materials, rigged FBX prefabs, WAV audio, `credits.json`), WebGL `.tar.gz`, and standalone macOS / Windows / Linux players. - **Godot 4 (MIT):** Complete Godot 4 project `.zip` (`.tscn` scene trees, GDScript `.gd`, GLB animations, `project.godot`) and HTML5 WebAssembly `.tar.gz`. - **Three.js & Pulse:** Complete TypeScript source `.zip` (`src/` or `systems/`, `world/`, glTF/JSONC assets, tests) and bundled web build `.tar.gz`. ## Developer & MCP FAQ ### How do I connect Claude Code, Cursor, or VS Code to GameCrew over MCP? Add GameCrew’s Streamable HTTP MCP endpoint (https://play.gamecrew.ai/mcp) to your assistant. One that signs in by itself opens GameCrew’s page in your browser: sign in and press Connect. Or open the studio Usage page, create an access token under Connect a coding assistant, and send it as Authorization: Bearer gc_... in your mcpServers config. Nothing needs to be installed locally. ### Can I use GameCrew from Claude or ChatGPT, without a coding assistant? Yes. In Claude (web, desktop or phone) or ChatGPT, add a custom connector with the address https://play.gamecrew.ai/mcp and nothing else. The app sends you to GameCrew to sign in and press Connect (OAuth 2.1 with PKCE and dynamic client registration), and GameCrew’s tools are in the chat. Access is listed, and taken away, on the studio Usage page. ### Does a connected assistant spend my GameCrew credits? Not by default. Your assistant does the work itself, on your own AI subscription: it reads the project, edits the source, and GameCrew runs the engine, checks the result and hosts each version, which costs engine minutes and no credits. GameCrew’s own AI crew (new_game, build_game, change_game), which builds from a brief and is paid from your credits, is offered to a connected assistant only on a plan that includes it, and only after you switch it on in the studio under Usage, Connect a coding assistant. ### What is the difference between a Full token and an Assets-only token? A Full token (scope: all) exposes all 91 MCP tools so your assistant can create games, edit C#/GDScript/TypeScript source, run sandboxed engine tests, submit verified merge requests, read and contribute engine techniques, and promote Live release links. An Assets-only token (scope: assets) exposes 14 asset-pack and technique-reading tools so an assistant working inside your own local Unity or Godot repo can generate rigged 3D models, PBR textures, and WAV audio without build access to your other games. ### Does my computer need Unity 6 or Godot 4 installed to edit a GameCrew game over MCP? No. Your coding assistant reads and edits files remotely via read_file, edit_file, project_map, and engine_api, while GameCrew compiles scenes, runs automated playtests, captures screenshots, and builds WebGL/HTML5 players inside its own cloud sandbox. ### Can I use GameCrew’s 3D model, rigging, and audio tools inside my own local Unity project? Yes. Create an asset pack with new_asset_pack, generate concept art, rigged FBX/GLB models, seamless textures, or mastered WAV audio, download the signed asset URLs via list_assets, and run get_importer to install GameCrew’s Unity 6 URP prefab, LOD, and Animator editor scripts. ### What files are included when I download a game’s source archive? Every saved version is a clean git tag you can download as a complete project archive: C# scripts, generated URP scenes, FBX prefabs, PBR maps, and WAV audio for Unity 6; .tscn scenes and GDScript for Godot 4; or TypeScript sources and glTF/JSONC assets for Three.js and Pulse — plus any open-licence credits.json attributions. --- # GameCrew AI tutorials > Step-by-step tutorials: WebXR VR games for Meta Quest, games made with Claude, ChatGPT or Cursor over MCP, multiplayer rooms, game jams and merge requests. - **Canonical URL:** https://gamecrew.ai/learn ## VR in the browser Games that play in a VR headset’s browser from one link, and flat everywhere else. - [Make a WebXR VR game for Meta Quest from a brief](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief) ([Markdown](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief.md)) · Platform: A VR game with a link that opens in your Quest’s browser, offers Enter VR with tracked head and hands, and still plays flat on a computer or a phone. You write no code. - [Make a VR game with your own assistant over MCP](https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp) ([Markdown](https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp.md)) · Contributor: A VR game of your own, forked from a VR showcase game and changed by your assistant, with a play link that offers Enter VR in a headset’s browser. - [Turn a flat game into VR](https://gamecrew.ai/learn/turn-a-flat-game-into-vr) ([Markdown](https://gamecrew.ai/learn/turn-a-flat-game-into-vr.md)) · Platform: The next version of your game plays in a VR headset’s browser, with tracked head and hands, and still plays flat on a computer or a phone. - [How we test a WebXR game without a headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset) ([Markdown](https://gamecrew.ai/learn/test-webxr-game-without-a-headset.md)) · Every VR game: You’ll know what the emulated-headset check proves about a VR game, what it doesn’t, and where its result is. ## With your own assistant Your chat or coding assistant does the work; GameCrew AI runs the engine, checks the game and hosts the link. - [Make a game in Claude or ChatGPT with one connector address](https://gamecrew.ai/learn/make-a-game-in-claude-or-chatgpt) ([Markdown](https://gamecrew.ai/learn/make-a-game-in-claude-or-chatgpt.md)) · Contributor: A game of your own in GameCrew AI, changed by your chat assistant from plain words, with a link anyone can play. - [Build a Godot 4 game with Claude Code or Cursor over MCP](https://gamecrew.ai/learn/godot-4-game-with-claude-code-or-cursor) ([Markdown](https://gamecrew.ai/learn/godot-4-game-with-claude-code-or-cursor.md)) · Contributor: A Godot 4 game of your own that your coding assistant changes in GDScript, that GameCrew AI compiles, tests and builds for the browser, and whose code you can download. ## Play and build together Rooms for friends, and changes to other people’s games. - [Make a multiplayer party game your friends join with a room code](https://gamecrew.ai/learn/multiplayer-party-game-room-code) ([Markdown](https://gamecrew.ai/learn/multiplayer-party-game-room-code.md)) · Platform: A browser game that plays solo at once and lets 2–8 friends join your room with a 4-letter code or an invite link. - [Change someone’s game: branch a showcase game and open a merge request](https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request) ([Markdown](https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request.md)) · Any account: A merge request into a game’s main line with your change, checked by its engine, that its owner can play before and after and merge. ## Game jams From the jam’s theme to a link for the judges and files for the jam page. - [Make a game jam entry that plays in the browser](https://gamecrew.ai/learn/game-jam-entry-in-the-browser) ([Markdown](https://gamecrew.ai/learn/game-jam-entry-in-the-browser.md)) · Platform: A jam game built from your brief, with a link judges can play in any browser, its browser build to upload to the jam page, and its code. ## Do this now - Try the free pitch, no sign-up: https://gamecrew.ai/#pitch - Play the showcase games: https://gamecrew.ai/games - Connect your assistant: https://play.gamecrew.ai/mcp # Make a WebXR VR game for Meta Quest from a brief > Describe a VR game and GameCrew AI builds it in three.js, Godot 4 or Unity 6: one link that offers Enter VR in Meta Quest Browser and plays flat elsewhere. - **Canonical URL:** https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief - **Tier:** Platform - **What you'll have at the end:** A VR game with a link that opens in your Quest’s browser, offers Enter VR with tracked head and hands, and still plays flat on a computer or a phone. You write no code. ## What you need - A Platform account: GameCrew AI’s crew builds the game. In early access seats come from the [waitlist](https://gamecrew.ai/tiers). - A VR headset with a browser, such as Meta Quest Browser, to play it in VR. Without one, the same link plays flat. ## Steps 1. **Open Make.** Sign in to the studio and open **Make**. 2. **Describe the game.** Write a few sentences in the box: where it is, what you do with your hands, how it should feel. A brief that asks for VR (“a VR game”, “in VR”) is enough to make it a VR game. ``` A VR game: you stand on a lighthouse balcony at night and catch moths in a glass jar before they reach the lamp. Grab the jar, swing it, close the lid. ``` 3. **Or switch VR on yourself.** Open **More options** and press **Make it a VR game**. Leave the engine on **Recommended** and the pitch picks one that can make VR games: Quick (three.js), Godot or Unity. Pulse says **Not for VR games yet**. 4. **Press Make it.** A pitch and three looks arrive in a couple of minutes, and you pick one before anything is built. A VR pitch is designed for hands and comfort: you move yourself (teleport, or slow stick walking with snap turn), and menus are things in the world, not a screen overlay. To stop after the pitch, press **Just the pitch** under More options. 5. **Choose a look.** On the **Design board**, press **Choose this look** on the moodboard you like. The concept art is made in it. 6. **Choose how it plays.** On **Gameplay**, press **Choose this** on one of the three takes, or write your own and press **Use my take**. When a look and a take are both chosen, the build starts. 7. **Check where it plays.** On **Engine & targets**, **VR** says **On**. You can change the engine until the build starts. An engine that can’t play in VR turns VR off, and the page says so. 8. **Let it build and check itself.** The AI crew builds and tests the game. Before the version is saved, its browser build is started and then taken into VR with an [emulated headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset). The new version opens on **Play**. 9. **Send the link to your headset.** Press **Share**. You get the link and a QR code. Scan the code with the headset if it can, or send yourself the link. 10. **Press Enter VR.** Open the link in Meta Quest Browser and press **Enter VR** on the start card. On a computer or a phone, the same link plays flat. 11. **Change it.** On **Build**, under **What should change?**, describe a change and press **Make the change**. Each change is a new version with its own link. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Fernlight** (Godot 4, plays in VR): https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/?via=llms · https://gamecrew.ai/games/fernlight ## Technique guides - [VR hands, throws and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) - [VR hands, throws and comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics) - [VR hands, throws and comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics) ## More - [Turn a flat game into VR](https://gamecrew.ai/learn/turn-a-flat-game-into-vr) - [How we test a WebXR game without a headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset) - [VR and WebXR on GameCrew AI](https://gamecrew.ai/vr) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Try the free pitch on the home page, no sign-up: https://gamecrew.ai/#pitch --- # Make a VR game with your own assistant over MCP > Your own assistant forks a VR showcase game and changes its code; GameCrew AI runs the engine, checks it in an emulated headset and hosts a Quest-ready link. - **Canonical URL:** https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp - **Tier:** Contributor - **What you'll have at the end:** A VR game of your own, forked from a VR showcase game and changed by your assistant, with a play link that offers Enter VR in a headset’s browser. ## What you need - An assistant that uses MCP: Claude, ChatGPT, Claude Code, Cursor, VS Code or another MCP client. - A Google account to sign in with. - Nothing to install: GameCrew AI runs the engine. ## Steps 1. **Connect your assistant.** In a chat app that takes custom connectors, add GameCrew AI with this address and nothing else. In a coding assistant that works in a terminal or an editor, tell it the line below instead: it starts the sign-up for you. ``` https://play.gamecrew.ai/mcp Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md ``` 2. **Press Connect.** GameCrew’s page opens in your browser. Sign in with Google and press **Connect**. That press is the only thing you do by hand. When every contributor place is taken the button says **Join the queue**: your place is kept and you are told when one opens. 3. **Find a VR game to start from.** Ask your assistant which showcase games play in VR. It calls `list_showcase`, and `get_game` says `vr: true` for a VR game. ``` List GameCrew’s showcase games and tell me which ones play in VR. ``` 4. **Fork it.** Ask it to fork that game. `fork_game` makes a game of your own from its newest version that passed its checks. It stays a VR game, plays at once, and is one of your 2 games. 5. **Let it learn the project.** It reads the project with `project_map` and `read_file`: `CLAUDE.md`, `README.md`, and `Assets/CCGD/VR.md`, the engine kit’s VR guide (the rig, the two hands, comfort locomotion, menus drawn in the world). 6. **Look up how it’s done.** Before it builds something hard, it can search the technique library with `search_techniques` and read a guide with `read_technique`. The VR guides are linked below. 7. **Ask for the change.** Say what should change in VR. The assistant edits the game’s own code with `edit_file` and `write_file` (in `Assets/Game/`). ``` In VR, let me grab the jar with grip and throw it. Show the score on my left wrist. ``` 8. **Run it.** `run_unity` runs the game’s own engine: `compile`, then `test`. Step `play` makes a browser build of the unsaved work with a private link for you. A build takes seconds on Godot and Quick, minutes on Unity. 9. **Save a version.** `save_version` with a one-line message. On your fork it runs the full checks, and for a VR game the emulated-headset check after the browser check. 10. **Play it in your headset.** Ask for the play link (`get_game`), open it in your headset’s browser and press **Enter VR**. ## Start from a VR game Your own assistant can’t switch VR on for a flat game yet: that switch is in the studio for Platform accounts. Fork a game that already plays in VR. ## What a contributor has 2 games of your own (forks), branches of games you can see, 30 engine minutes a day, one engine run at a time, and 20 credits once for generated art. Free in early access. Your assistant’s own work runs on your own AI subscription. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Fernlight** (Godot 4, plays in VR): https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/?via=llms · https://gamecrew.ai/games/fernlight ## Technique guides - [VR hands, throws and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) - [VR hands, throws and comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics) - [VR hands, throws and comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics) ## More - [How we test a WebXR game without a headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset) - [Make a game in Claude or ChatGPT](https://gamecrew.ai/learn/make-a-game-in-claude-or-chatgpt) - [The Contributor tier](https://gamecrew.ai/beta) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Connect your assistant to https://play.gamecrew.ai/mcp, or tell a coding assistant: "Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md". --- # Turn a flat game into VR > Switch VR on for a three.js, Godot 4 or Unity 6 game, say how it should play in VR, and its next version offers Enter VR in a headset’s browser. - **Canonical URL:** https://gamecrew.ai/learn/turn-a-flat-game-into-vr - **Tier:** Platform - **What you'll have at the end:** The next version of your game plays in a VR headset’s browser, with tracked head and hands, and still plays flat on a computer or a phone. ## What you need - A game of yours made in Quick (three.js), Godot or Unity. Pulse games can’t play in VR yet. - A Platform account: GameCrew AI’s crew makes the change. ## Steps 1. **Open the game.** Sign in to the studio and open the game. Someone else’s showcase game? Press **Fork** on its page first: the fork is yours. 2. **Open its settings.** Press **⋯** in the game’s header (Game settings). 3. **Press Turn VR on.** It is in the **VR** card, shown when no build is running. Nothing changes yet: the next version you build is made for a VR headset’s browser too. 4. **Say how it plays in VR.** On **Build**, under **What should change?**, describe the VR version: what your hands do, how you move, where the score goes. Press **Plan it** first to see the steps (a few cents), or **Make the change**. ``` Make it play in VR: pick up the lantern with grip, teleport with the left stick, snap turn with the right, and show the timer on a sign in the world. ``` 5. **Let the crew build it.** It uses the engine kit’s VR parts: the rig, both hands, comfort locomotion (stick move with a vignette, snap turn, teleport) and menus drawn in the world. One unit is one metre and the floor is where your feet are. 6. **Checked in an emulated headset.** Every save of a VR game goes into VR in an [emulated headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset) after its browser check. If it fails, the version says why. 7. **Play it in your headset.** Press **Share**, open the link in the headset’s browser and press **Enter VR**. 8. **Turn it off any time.** **Turn VR off** in the same card. The next version is flat again. ## With your own assistant On the Contributor tier your assistant can’t switch VR on for a flat game yet. [Start from a VR game](https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp) instead. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Fernlight** (Godot 4, plays in VR): https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/?via=llms · https://gamecrew.ai/games/fernlight ## Technique guides - [VR hands, throws and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) - [VR hands, throws and comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics) - [VR hands, throws and comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics) ## More - [Make a VR game from a brief](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief) - [How we test a WebXR game without a headset](https://gamecrew.ai/learn/test-webxr-game-without-a-headset) - [Compare the engines](https://gamecrew.ai/engines) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Try the free pitch on the home page, no sign-up: https://gamecrew.ai/#pitch --- # How we test a WebXR game without a headset > Every save of a GameCrew AI VR game runs in headless Chrome with an emulated Quest 3: it enters VR, draws both eyes, follows the head, reads the controllers. - **Canonical URL:** https://gamecrew.ai/learn/test-webxr-game-without-a-headset - **Tier:** Every VR game - **What you'll have at the end:** You’ll know what the emulated-headset check proves about a VR game, what it doesn’t, and where its result is. ## What you need - Nothing: the check runs by itself on every save of a VR game, in Quick (three.js), Godot 4 and Unity 6. ## Steps 1. **Boot with an emulated headset.** The browser build starts in headless Chrome with an emulated headset: IWER, Meta’s WebXR runtime in JavaScript, with a Quest 3 profile, loaded from the studio with no network. It is the real WebXR API against an emulated device. The game must log `[game] start`, `ccgdVr.supported()` must be true, and the **Enter VR** button must be visible. 2. **Press Enter VR.** A click on the button starts the session: it is active, XR frames keep coming, and the game logs `[game] vr enter`. 3. **Two eyes, two viewpoints.** A picture, `vr_stereo.png`: each eye’s half must be drawn (not one flat colour) and the halves must differ. With both eyes put at one point, the halves must match: two views of one scene, not one picture stretched across both. 4. **The head moves the view.** The head turns 120°: the picture changes and the game’s heading follows. Turned back, the picture returns, which tells a head turn from the game’s own animation. The head moves 0.4 m and the game’s head position follows. 5. **The controllers drive the game.** The left stick is pushed forward: the game’s move input goes forward. The right trigger is held: the game sees `right-trigger`. 6. **A standalone headset’s budget.** Draw calls and triangles of a frame are measured against 200 draw calls and 300,000 triangles. Over the budget is a note on the version, not a failure. 7. **Exit back to flat.** The session ends, the game logs `[game] vr exit`, and the flat game keeps running. 8. **No errors anywhere.** Any page error or console error during all of it fails the check. 9. **Read the result.** A failure is a failed browser check of that version, its errors starting with “VR check (emulated headset):”. The stereo picture is kept with the version’s pictures. A game that isn’t a VR game is not checked. ## What it can’t tell you It proves the game enters VR, draws both eyes, follows the head and reads the controllers. It does not measure comfort, or the frame rate on a real headset. Play it on one too. ## The page’s side Every VR game’s page shows **Enter VR** only when the browser can start an immersive session, asks for `local-floor` (falling back to `local`), fetches nothing from the network for controllers or hands, and gives the check `window.ccgdVr` to read the game’s state. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Fernlight** (Godot 4, plays in VR): https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/?via=llms · https://gamecrew.ai/games/fernlight ## Technique guides - [VR hands, throws and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) - [VR hands, throws and comfort in Three.js](https://gamecrew.ai/techniques/three/vr-interactions-ergonomics) - [VR hands, throws and comfort in Unity 6](https://gamecrew.ai/techniques/unity/vr-interactions-ergonomics) ## More - [Make a VR game from a brief](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief) - [Make a VR game with your own assistant](https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp) - [VR and WebXR on GameCrew AI](https://gamecrew.ai/vr) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Play a VR showcase game in your headset's browser: https://gamecrew.ai/vr --- # Make a game in Claude or ChatGPT with one connector address > Add one address as a custom connector in Claude or ChatGPT, press Connect once, and your assistant forks a real engine game, changes it and shares a link. - **Canonical URL:** https://gamecrew.ai/learn/make-a-game-in-claude-or-chatgpt - **Tier:** Contributor - **What you'll have at the end:** A game of your own in GameCrew AI, changed by your chat assistant from plain words, with a link anyone can play. ## What you need - Claude (on the web, a desktop or a phone) or ChatGPT, with custom connectors. - A Google account to sign in with. ## Steps 1. **Copy the address.** This is all you add. No token, no install. ``` https://play.gamecrew.ai/mcp ``` 2. **Add it as a connector.** In **Claude**: Settings, Connectors, Add custom connector, and paste the address. In **ChatGPT**: Settings, Apps & Connectors, turn on developer mode, and create a connector with the address. 3. **Sign in and press Connect.** The app opens GameCrew’s page in your browser. Sign in with Google and press **Connect** (**Join the queue** when every contributor place is taken). You are back in the chat with GameCrew’s tools. 4. **Pick a game to start from.** Ask for the showcase. Your assistant calls `list_showcase`. ``` Show me GameCrew’s showcase games. ``` 5. **Fork one.** `fork_game` makes a game of your own from it, playable at once. It is one of your 2 games. ``` Fork the first one for me. ``` 6. **Ask for a change in plain words.** Your assistant reads the code (`project_map`, `read_file`), edits it (`edit_file`), runs the engine (`run_unity`) and saves a version (`save_version`). Godot and Quick games build in seconds, Unity games in minutes. ``` Make the jump higher and add a second level. ``` 7. **Play it.** Ask for the play link (`get_game`). It opens in any browser, on a computer or a phone. A VR game also offers **Enter VR** in a headset’s browser. 8. **Keep going.** Every saved version has its own link. Ask for pictures of it with `get_screenshots`. ## Whose work it is Your assistant does the work on your own AI subscription. GameCrew AI runs the engine, checks the game and hosts the link: 30 engine minutes a day, one run at a time, and 20 credits once for generated art. On a Platform account, GameCrew AI’s crew can also do the work when you switch **Let my assistants use GameCrew’s AI crew** on, on the Usage page. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Kerbside** (Unity 6): https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/?via=llms · https://gamecrew.ai/games/kerbside - **Fjordline** (Unity 6): https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/?via=llms · https://gamecrew.ai/games/fjordline ## More - [Make a VR game with your own assistant](https://gamecrew.ai/learn/vr-game-with-your-own-assistant-mcp) - [Change someone’s game with a merge request](https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request) - [The Contributor tier](https://gamecrew.ai/beta) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Connect your assistant to https://play.gamecrew.ai/mcp, or tell a coding assistant: "Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md". --- # Build a Godot 4 game with Claude Code or Cursor over MCP > Connect Claude Code or Cursor over MCP, fork a Godot 4 game, and your assistant writes GDScript while GameCrew AI compiles, tests and builds it. No install. - **Canonical URL:** https://gamecrew.ai/learn/godot-4-game-with-claude-code-or-cursor - **Tier:** Contributor - **What you'll have at the end:** A Godot 4 game of your own that your coding assistant changes in GDScript, that GameCrew AI compiles, tests and builds for the browser, and whose code you can download. ## What you need - Claude Code, Cursor or another MCP client. - A Google account to sign in with. - No Godot install: GameCrew AI runs Godot 4. ## Steps 1. **Claude Code: add the server.** Add GameCrew AI over HTTP, then run `/mcp` and choose to sign in. Your browser opens GameCrew’s page: sign in with Google and press **Connect**. ``` claude mcp add --transport http gamecrew https://play.gamecrew.ai/mcp ``` 2. **Cursor: let it sign you up.** Tell Cursor (or any assistant that can run commands) the line below. It starts a sign-up and shows you a link and a code: open the link, sign in, check the code matches and press **Connect**. It gets a token and the MCP settings to add. Restart the session so the tools load. Already have an account? On the studio’s **Usage** page, **Connect a coding assistant**, **Make a token** (Games and assets) gives the settings to paste, shown once. ``` Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md ``` 3. **Start from a Godot game.** `list_showcase` shows each game’s engine. `fork_game` makes a game of your own; `create_branch` makes a branch instead, to change the game and offer the change back. 4. **Read the project.** `project_map` gives the scripts, scenes, tuning and tests at a glance; `read_file` reads `CLAUDE.md` and `README.md`. A Godot game’s code is GDScript with its scenes and resources as text (`.gd`, `.tscn`, `.tres`, `.gdshader`) in `Assets/Game/`. 5. **Get the API right.** `engine_api` gives exact offline Godot 4 signatures, and `search_techniques` finds engine-specific guides (linked below). ``` engine_api: CharacterBody3D.move_and_slide ``` 6. **Edit.** `edit_file` changes part of a file; `write_file` writes a whole one. 7. **Compile, test and play.** `run_unity` runs the game’s own engine, Godot here: `compile`, `scene`, `test`, `capture`, or `play` for a private browser build of unsaved work. Godot steps take seconds. 8. **Save a version.** `save_version` with a message written like a commit subject. On a fork it runs the full checks; on a branch it is a quick save, not checked until it is merged. 9. **Play it and take the code.** `get_game` has the play link. In the studio, a version on **Versions** has **Download the game’s code (zip)**: the Godot project, to open in Godot 4. ## What a contributor has 2 games of your own, 30 engine minutes a day and one engine run at a time. Free in early access. ## Play one first - **Fernlight** (Godot 4, plays in VR): https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/?via=llms · https://gamecrew.ai/games/fernlight ## Technique guides - [Enemy and NPC steering in Godot 4](https://gamecrew.ai/techniques/godot/enemy-npc-ai-steering) - [Springs and trails in Godot 4](https://gamecrew.ai/techniques/godot/procedural-springs-trails) - [Stylized water in Godot 4](https://gamecrew.ai/techniques/godot/stylized-water-foam) - [VR hands and comfort in Godot 4](https://gamecrew.ai/techniques/godot/vr-interactions-ergonomics) ## More - [Developers and the MCP tools](https://gamecrew.ai/developers) - [Change someone’s game with a merge request](https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request) - [Compare the engines](https://gamecrew.ai/engines) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Connect your assistant to https://play.gamecrew.ai/mcp, or tell a coding assistant: "Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md". --- # Make a multiplayer party game your friends join with a room code > Ask for a multiplayer game and GameCrew AI builds one that plays solo at once and lets 2–8 friends join with a 4-letter room code, checked in two browsers. - **Canonical URL:** https://gamecrew.ai/learn/multiplayer-party-game-room-code - **Tier:** Platform - **What you'll have at the end:** A browser game that plays solo at once and lets 2–8 friends join your room with a 4-letter code or an invite link. ## What you need - A Platform account: GameCrew AI’s crew builds the game. - Friends with a browser: on a computer or a phone. ## Steps 1. **Open Make.** Sign in to the studio, open **Make** and describe the party game: who plays, what they do together, how a round ends. 2. **Switch Multiplayer on.** Open **More options** and press **Multiplayer**. Engines without rooms say **Not for multiplayer yet**. Quick (three.js), Godot and Unity have rooms. 3. **Make it, then choose.** Press **Make it**, then **Choose this look** and **Choose this** on how it plays. The build starts when both are chosen. 4. **Checked with two browsers.** Before the version is saved, two separate headless browsers join one room over a real room server: both connect, the host’s moves show on the guest’s screen, and when the host leaves the guest takes over. A picture of both, side by side, is kept with the version. 5. **Share the link.** Press **Share** and send the link, or open it yourself. 6. **Start a room.** On the start card, press **Play with Friends**. It makes a 4-letter room code and puts it in the address (`#room=K7MP`). Codes use letters and digits that can’t be mixed up: no I, O, 0 or 1. 7. **Invite your friends.** During play, the room button opens a sheet with the room code and **Copy Invite Link**. Friends open the link, or press **Join Room** and type the code. 8. **Play.** The first player in the room hosts. If the host leaves, the next player takes over and the game goes on. There is no free-text chat: players send quick emotes. 9. **Already have a game?.** In its settings (**⋯**), **Turn Multiplayer on**. The next version you build gets rooms and still plays solo. ## Rooms and hosting While the studio is awake, a share link has 2 live rooms, up to 8 players each. For rooms all the time, download the browser build from the version: it comes with `server.mjs`, a `Dockerfile` and `HOSTING.md`, and `node server.mjs` runs the game and its rooms anywhere. ## With your own assistant Your own assistant can’t switch multiplayer on yet: on the Contributor tier, a game gets rooms only if it already has them. ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Kerbside** (Unity 6): https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/?via=llms · https://gamecrew.ai/games/kerbside - **Fjordline** (Unity 6): https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/?via=llms · https://gamecrew.ai/games/fjordline ## More - [Make a VR game from a brief](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief) - [Compare the engines](https://gamecrew.ai/engines) - [The two tiers](https://gamecrew.ai/tiers) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Try the free pitch on the home page, no sign-up: https://gamecrew.ai/#pitch --- # Change someone’s game: branch a showcase game and open a merge request > Branch a public GameCrew AI game, change it yourself or with your assistant, and open a merge request. The owner plays it before and after, then merges. - **Canonical URL:** https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request - **Tier:** Any account - **What you'll have at the end:** A merge request into a game’s main line with your change, checked by its engine, that its owner can play before and after and merge. ## What you need - A GameCrew AI account: Contributor or Platform. - A public game to change: every showcase game is public. ## Steps 1. **Find the game.** In the studio, **Explore** lists the public games, the showcase included. Open the one you want to change. 2. **Make a branch.** Press **New branch**, or open the **Branches** tab. Name it after the change (2 to 24 characters of a–z, 0–9 and -) and press **Create branch**. With an assistant: `create_branch`. ``` red-boat ``` 3. **Change the branch.** On a Platform account the branch opens on **Build**: describe the change and press **Make the change**. On the Contributor tier, your assistant works on the branch by its id with `read_file`, `edit_file` and `run_unity`. 4. **Save a version.** `save_version`. On a branch it is a quick save: it compiles and builds the game for the browser, and the version is marked not checked. `full: true` runs the full check now. 5. **Look at it the way the owner will.** `get_change` shows what the version changed: pictures of each view before and after, both play links, and the diffs. 6. **Pick a handle.** The owner sees your handle, never your email. Pick one on the **Usage** page, or with `set_handle`. Until you do, you are shown as “a contributor”. 7. **Open the merge request.** On the branch’s **Merge requests** tab, write its title in a line, add more if you like, and press **Open merge request**. With an assistant: `open_merge_request`. 8. **The owner reviews it.** The owner and the game’s crew can play it, comment on one view, asset or file, and give a verdict. Only the owner merges. Merging runs the full check first, and main gets a new version only if it passes. 9. **Answer a request for changes.** Change the branch, save again and update the merge request (**Update to v…**, or `open_merge_request` again). Notifications tell you what happened (`get_notifications`, or the bell in the studio). ## Limits From outside a game’s crew: 1 branch of each game, 5 across the studio, 3 open merge requests per game and 10 merge requests a day. Work on a branch spends your own budget and engine minutes. ## Branch or fork? A branch belongs to the game and goes back into it. A fork is a game of your own, where the owner allows forks (every showcase game does). ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Kerbside** (Unity 6): https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/?via=llms · https://gamecrew.ai/games/kerbside - **Fjordline** (Unity 6): https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/?via=llms · https://gamecrew.ai/games/fjordline ## More - [Build together on GameCrew AI](https://gamecrew.ai/collaborate) - [How a crew makes a game](https://gamecrew.ai/beta) - [Build a Godot 4 game with your coding assistant](https://gamecrew.ai/learn/godot-4-game-with-claude-code-or-cursor) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Connect your assistant to https://play.gamecrew.ai/mcp, or tell a coding assistant: "Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md". --- # Make a game jam entry that plays in the browser > From the jam’s theme to a playable three.js prototype: a link for the judges, the browser build to upload and the code to share, built and checked for you. - **Canonical URL:** https://gamecrew.ai/learn/game-jam-entry-in-the-browser - **Tier:** Platform - **What you'll have at the end:** A jam game built from your brief, with a link judges can play in any browser, its browser build to upload to the jam page, and its code. ## What you need - A Platform account: GameCrew AI’s crew builds the game from a brief. Contributors start from an existing game, which most jams don’t allow. - The jam’s theme, and its rules on AI tools: check them before you start. ## Steps 1. **Write the brief from the theme.** Sign in to the studio, open **Make** and describe a small game around the jam’s theme: one mechanic, one place, how a round ends. ``` Theme: “roots”. You are a seed in dry soil: steer a growing root toward water before the sun bakes the ground, splitting it to reach more than one pool. ``` 2. **Choose a quick first build.** Open **More options**. Under **First build**, **Quick prototype** builds the core mechanic in its first area; its card shows the time it usually takes. Under **Engine**, **Quick** is made for the browser with three.js: a playable build in minutes for a fraction of the cost. Set **Spend up to $**. 3. **Make it, then choose.** Press **Make it**. Choose a look (**Choose this look**) and how it plays (**Choose this**): the build starts when both are chosen. 4. **Let it check itself.** Every version is compiled, tested, started in a headless browser and photographed before it is saved. A version that fails says why. 5. **Play it and change it.** Play it on **Play**. On **Build**, describe what should change and press **Make the change**, or **Plan it** first to see the steps. Each version keeps its own link, so you can always go back. 6. **Give the judges a link.** Press **Share**: a link and a QR code. It plays in any browser, on a computer or a phone, with nothing to install. 7. **Upload it to the jam page.** On **Versions**, open the version and press **Download the browser build**: the playable files, to put on any web host. Unpack them and upload them as an HTML5 game, the way the jam’s site asks. 8. **Share the code.** **Download the game’s code (zip)** on the same version: the whole project, to open in its engine or put in a repository. ## Want friends in it? Switch **Multiplayer** on under More options before you press Make it, and players join each other with a [4-letter room code](https://gamecrew.ai/learn/multiplayer-party-game-room-code). ## Play one first - **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/?via=llms · https://gamecrew.ai/games/lumen-orchard - **Kerbside** (Unity 6): https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/?via=llms · https://gamecrew.ai/games/kerbside - **Fjordline** (Unity 6): https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/?via=llms · https://gamecrew.ai/games/fjordline ## More - [Make a multiplayer party game](https://gamecrew.ai/learn/multiplayer-party-game-room-code) - [Make a VR game from a brief](https://gamecrew.ai/learn/webxr-vr-game-meta-quest-from-a-brief) - [Compare the engines](https://gamecrew.ai/engines) - [All tutorials](https://gamecrew.ai/learn) ## Do this now Try the free pitch on the home page, no sign-up: https://gamecrew.ai/#pitch --- # How It Was Made: Playable GameCrew AI Case Studies > Step inside real GameCrew AI builds with version-by-version test counts, WebGL boot times, WebXR frame budgets, and playable browser links. - **Canonical index:** https://gamecrew.ai/making ## Case studies ### [Breakline — Unity 6 URP · C#](https://gamecrew.ai/making/breakline) Started from a $0.15 three-word brief ("Wave racer game") and iterated across three git-tagged Unity 6 URP builds with automated EditMode, PlayMode, and browser boot checks. - **Starting brief:** "Wave racer game" ($0.15 pitch) - **Engine & output:** Unity 6 URP · C# + WebGL - **v3 automated tests:** 13/13 unit · 31/31 play - **WebGL boot & errors:** 5.4 s boot · 0 browser errors - **Assets built in-loop:** 5 custom 3D models · 16 sound assets - **All 3 rounds combined:** 181 min compute · $14.86 - **Markdown breakdown:** https://gamecrew.ai/making/breakline.md ### [Vesperglass — Three.js · TypeScript + WebXR](https://gamecrew.ai/making/vesperglass) Built in Three.js TypeScript as one dual-mode share link for flat browsers and Meta Quest Browser, pairing three interactive sanctuaries with strict standalone VR draw-call discipline. - **Engine & target:** Three.js TypeScript · WebXR VR - **Standalone VR budget:** 176 draw calls · 154,810 tris (cap: 200 / 300k) - **Automated checks (v1):** 0 audit errs · 3/3 unit · 14/14 play · 9/9 ui-check - **WebXR emulation gate:** 45 stereo VR frames verified (controllers + 25-joint hands) - **Mobile & desktop UI:** 7% phone · 7% phone-wide · 6% laptop overlay area - **Sanctuaries & climax:** 3 sanctuaries + Master Carillon Bell & 14 m Aurora Pillar - **Markdown breakdown:** https://gamecrew.ai/making/vesperglass.md # Breakline: three words to a verified Unity 6 wave racer > Started from a $0.15 three-word brief ("Wave racer game") and iterated across three git-tagged Unity 6 URP builds with automated EditMode, PlayMode, and browser boot checks. - **Canonical URL:** https://gamecrew.ai/making/breakline - **Engine:** Unity 6 URP · C# - **Modes:** Flat Desktop & Mobile Touch - **Playable build:** https://gamecrew.ai/games/breakline ## Measured build & verification metrics - **Starting brief:** "Wave racer game" ($0.15 pitch) - **Engine & output:** Unity 6 URP · C# + WebGL - **v3 automated tests:** 13/13 unit · 31/31 play - **WebGL boot & errors:** 5.4 s boot · 0 browser errors - **Assets built in-loop:** 5 custom 3D models · 16 sound assets - **All 3 rounds combined:** 181 min compute · $14.86 ## Build rounds & checks | Round | Prompt / Focus | Effort | Scope | Verified gates | |---|---|---|---|---| | v1 | Wave racer game | 49 min · $4.27 | 109 files (+2966/-392), 7 views | 11/11 unit, 15/15 play, 4.3 s WebGL boot (0 errors) | | v2 | Make graphics much better | 55 min · $4.65 | 61 files (+1271/-224), 8 views | 13/13 unit, 22/22 play, 5.2 s WebGL boot (0 errors) | | v3 | Really improve the water graphics and boat interactions with water | 77 min · $5.79 | 18 files (+778/-65), 9 views | 13/13 unit, 31/31 play, 5.4 s WebGL boot (0 errors) | ## Engineering architecture - Structured design pitch ($0.15) established the core ocean swell field, crest launch trick charging, Surge jet blast, and rival wake drafting loops plus a 7-row desktop/gamepad/touch control contract. - Version 1 compiled the full Unity 6 URP project (109 files, +2,966 lines), rigged the pilot and skimmer assets, and passed 11/11 EditMode + 15/15 PlayMode checks with a 4.3 s headless Chrome boot. - Version 2 and Version 3 targeted visual polish, custom water shaders, wake spray particles, and hull buoyancy contact tuning while expanding automated playtest assertions from 15 to 31 cases. ## Key takeaways - Small follow-up change requests ("Make graphics much better", then "Really improve the water graphics and boat interactions") touch only the relevant shader and physics files (61 -> 18 files in v2 -> v3) because git tags preserve the verified baseline. - Every version passes deterministic PlayMode tests and real WebGL Chrome boot checks before a single preview link is issued. ## Frequently asked questions ### Were all 31 PlayMode tests on Breakline v3 executed in real Unity? Yes. Each saved version in GameCrew runs Unity 6 batch EditMode and PlayMode verification plus headless Chrome WebGL boot before recording the metrics stored in making.json. ### Can I open the Breakline Unity 6 source in a local editor? Creators on GameCrew can export full Unity 6 project archives (.zip) at any verified git tag, or iterate live over MCP from Cursor, Claude Code, or VS Code. ### Why did v3 grow from 15 to 31 PlayMode checks? Each change round adds targeted assertions for the newly modified mechanics — wave crest launch detection, Surge recovery, wake drafting, and water contact stability — so regressions cannot land silently. --- # Vesperglass: a WebXR glass conservatory within Quest frame budgets > Built in Three.js TypeScript as one dual-mode share link for flat browsers and Meta Quest Browser, pairing three interactive sanctuaries with strict standalone VR draw-call discipline. - **Canonical URL:** https://gamecrew.ai/making/vesperglass - **Engine:** Three.js · TypeScript + WebXR - **Modes:** Dual-Mode WebXR VR & Flat Browser - **Playable build:** https://gamecrew.ai/games/vesperglass ## Measured build & verification metrics - **Engine & target:** Three.js TypeScript · WebXR VR - **Standalone VR budget:** 176 draw calls · 154,810 tris (cap: 200 / 300k) - **Automated checks (v1):** 0 audit errs · 3/3 unit · 14/14 play · 9/9 ui-check - **WebXR emulation gate:** 45 stereo VR frames verified (controllers + 25-joint hands) - **Mobile & desktop UI:** 7% phone · 7% phone-wide · 6% laptop overlay area - **Sanctuaries & climax:** 3 sanctuaries + Master Carillon Bell & 14 m Aurora Pillar ## Build rounds & checks | Round | Prompt / Focus | Effort | Scope | Verified gates | |---|---|---|---|---| | Stage 1 · Core & VR | Venetian lagoon conservatory with dual-mode WebXR + flat locomotion and 3 sanctuaries | 176 draw calls · 154,810 tris | Three sanctuaries: Murano Crucible, Prism Observatory, Harmonic Choir | 3/3 unit tests, 14/14 play tests, WebGL boot clean | | Stage 2 · UI & Hands | Articulated brass gauntlets, wrist compass, touch/desktop HUD, and WebXR hand tracking | 7% / 7% / 6% HUD footprint | 9/9 ui-check captures across phone portrait, landscape & laptop | Emulated Quest 3 vr-check: 45 stereo frames, controllers + tracked hands | ## Engineering architecture - Three complete physical puzzles share one coherent glass rotunda: thermal quartz forging at the West Murano Crucible, triple-beam dispersion alignment in the North Prism Observatory, and glass verrophone harmonics + Resonance Orb throws in the East Choir. - Stays comfortably under standalone headset rendering limits (176 draw calls and 154,810 triangles per frame vs the 200 draw call / 300,000 triangle Quest budget) by sharing materials, keeping glass shader passes lean, and avoiding full-screen post-processing in stereo VR. - Replaces opaque black-box WebGL previews with automated WebXR emulation (`vr-check`): both eyes draw cleanly (`xrCompatible`), head tracking updates camera pose, controller grips/triggers grab quartz or throw orbs, and bare 25-joint hands poke buttons directly. ## Key takeaways - One URL serves flat desktop (WASD + mouse), mobile touch controls, and `Enter VR` stereo sessions without APK sideloading. - Keeping HUD overlays under 7% of the viewport leaves glass reflections, horizon cues, and VR sanctuaries clear on both 360px phones and desktop monitors. ## Frequently asked questions ### How were Vesperglass’s 176 draw calls and 154,810 triangles measured? During `ccgd vr-check`, an emulated Meta Quest 3 WebXR runtime renders 45 real stereo frames of the production Three.js bundle and inspects the WebGL renderer frame counters against our 200 draw-call and 300,000-triangle standalone budget. ### Can you play Vesperglass without a Meta Quest headset? Yes. Opening `/games/vesperglass` on a desktop or phone gives full keyboard/mouse (`WASD`, `E` grab, `F` interact) or touch controls on the exact same build. ### Why build Quest experiences as Three.js WebXR links instead of native APKs? A WebXR URL loads immediately inside Meta Quest Browser with zero cable setup or store approval wait, while every code change is tested across unit, play, UI, and emulated headset checks automatically. --- ## Core Frequently Asked Questions ### What is the difference between a contributor and a Platform account? Who does the work. As a contributor, your own coding assistant does it: you change games through branches and merge requests, keep 2 games of your own, and it is free during early access. On Platform, GameCrew AI’s crew builds games from your brief, with art, 3D models and sound, on a plan from Free to Team. Both are early access. You can ask to move either way from your account’s Usage page: moving to Platform needs a free seat and an admin’s approval, and moving to Contributor frees your seat and keeps every game yours. ### What game engines does GameCrew build with? GameCrew builds real projects in four engines: Unity 6 (Universal Render Pipeline for rich 3D worlds), Godot 4, Three.js for fast browser-first 3D, and Pulse (a deterministic TypeScript web engine). Three.js, Godot 4 and Unity 6 games can also target WebXR VR headsets directly in the browser. ### Do players need to install anything to play a GameCrew game? No. Every verified version gets a shareable link that runs directly in desktop and mobile browsers with phone touch controls, and VR-enabled builds offer Enter VR in a headset browser via WebXR. Creators can also download full engine projects and standalone builds. ### How does GameCrew verify that a generated game actually works? Before a version is marked verified, GameCrew compiles the project in its engine, runs automated edit-mode and play-mode tests that simulate gameplay, checks console logs, boots the web build in headless Chrome, tests VR builds with an emulated WebXR headset, and captures multi-angle screenshots. ### Who owns the games and source code made with GameCrew? Games you build on GameCrew belong to you. At any time you can download your game’s full project archive (C#, GDScript, or TypeScript source, scenes, rigged 3D models, PBR textures, and audio) along with its exported web build. ### How long does it take to go from a prompt to a playable game? GameCrew delivers a structured pitch, visual moodboards, and concept art in about two minutes. A tested, playable browser build typically finishes in 10 to 25 minutes (40 to 80 minutes for a large 3D Unity vertical slice), and follow-up changes take 10 to 20 minutes. ### Can I edit a GameCrew game locally or build together with other creators? Yes. Every saved version exports as a clean project zip you can open in the Unity 6 Editor, Godot 4 Editor, or VS Code, or steer over MCP. Creators can also branch each other's games, send verified improvements back as merge requests, and reuse shared 3D models, PBR textures, and engine techniques. --- ## Ownership, Privacy & Trust Summary - **Operator:** GameCrew AI, a sole proprietorship (Vermont, United States). - **Creator ownership:** Creators own their game-specific code, scenes, and generated assets, and can download full engine project zips and web builds at any time. - **Privacy:** First-party cookieless engagement counts using daily-rotated hashes; zero third-party ad or analytics trackers; Do Not Track (DNT) and Global Privacy Control (GPC) respected. - **Security & sandboxing:** AI-written engine code executes in isolated sandboxes with no network access and zero access to API keys. - **Policies:** [Trust and data](https://gamecrew.ai/trust) · [Privacy](https://gamecrew.ai/privacy) · [Terms](https://gamecrew.ai/terms) --- ## Playable Category Hubs - **[WebXR VR Browser Games for Quest](https://gamecrew.ai/games/vr)** ([Markdown](https://gamecrew.ai/games/vr.md)): Play dual-mode WebXR VR games directly in Meta Quest Browser or flat on desktop. No APK, no sideloading — click Play and Enter VR. - **[Playable Godot 4 Browser Games](https://gamecrew.ai/games/godot)** ([Markdown](https://gamecrew.ai/games/godot.md)): Play verified Godot 4 HTML5 browser games built with GDScript and .tscn scenes, plus downloadable MIT-licensed Godot project exports. - **[Playable Three.js WebGL & VR Games](https://gamecrew.ai/games/threejs)** ([Markdown](https://gamecrew.ai/games/threejs.md)): Play fast-booting Three.js TypeScript games in your browser and Quest WebXR, built with BVH collision and custom shaders. - **[Playable Unity 6 URP Browser Games](https://gamecrew.ai/games/unity)** ([Markdown](https://gamecrew.ai/games/unity.md)): Play Unity 6 URP C# games compiled to WebGL in the cloud with rigged 3D characters, EditMode/PlayMode tests & full Unity .zip export. - **[Playable Multiplayer Room Browser Games](https://gamecrew.ai/games/multiplayer)** ([Markdown](https://gamecrew.ai/games/multiplayer.md)): Play live co-op and versus browser games with instant WebSocket room codes, verified by two simulated headless peers before release. --- ## Playable Showcase Games # Lumen Orchard > Play Lumen Orchard directly in your browser — built and verified with GameCrew. - **Canonical page:** https://gamecrew.ai/games/lumen-orchard - **Play in browser:** https://gamecrew.ai/t/wyow90ZOSkKCjJv9n6G555CauNEG0mK_/ - **Profile:** Playable in browser · Three.js · Plays in VR (WebXR) · Multiplayer - **Verified versions:** 8 - **Fork it:** https://studio.gamecrew.ai/#/fork/lumen-orchard (start your own game from this one, in the GameCrew studio) ## Verification proof - Edit & structural checks: 3/3 passed - Automated playtests: 29/29 passed - Headless Chrome browser boot: verified (1.2 s) - Emulated WebXR headset: stereo eye rendering & controller input verified ## Top scores (Best harvest) 1. **TET** — 1815 ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/lumen-orchard/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/lumen-orchard/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/lumen-orchard/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/lumen-orchard/shot/3.jpg) ## Open-licence asset credits - Food Apple 01: Food Apple 01: Oliver Harries, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Lemon: Lemon: Kuutti Siitonen, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Food Pomegranate 01: Food Pomegranate 01: Oliver Harries, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Food Lime 01: Food Lime 01: Oliver Harries, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Wooden Lantern 01: Wooden Lantern 01: James Ray Cock, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Wooden Bowl 01: Wooden Bowl 01: Oliver Harries, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Swipe 1: Swipe 1: Kinoton, Freesound (https://freesound.org/s/427979/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Thud soft 1: Thud soft 1: saturdaysoundguy, Freesound (https://freesound.org/s/388035/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Tink 3: Tink 3: TheWah, Freesound (https://freesound.org/s/104815/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Bell chapel 1: Bell chapel 1: unxpctd, Freesound (https://freesound.org/s/815855/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Tomato squash 1: Tomato squash 1: HonorHunter, Freesound (https://freesound.org/s/271666/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Tomato squash 2: Tomato squash 2: kaydinhamby, Freesound (https://freesound.org/s/382637/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Amb forest loop: Amb forest loop: eternalframe, Freesound (https://freesound.org/s/687148/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Strap release: Strap release: IndigoRay, Freesound (https://freesound.org/s/331719/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Bells far: Bells far: HootOwl, Freesound (https://freesound.org/s/466170/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Land soft 1: Land soft 1: qubodup, Freesound (https://freesound.org/s/855106/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Birds window 2: Birds window 2: richwise, Freesound (https://freesound.org/s/811988/), CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Monastery Stone Floor: Monastery Stone Floor: Amal Kumar, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Leafy grass ground cover: leafy grass colour map by Charlotte Baglioni, Poly Haven, CC0 1.0 ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) # Kerbside > Every push, pop and scrape is earned: a grounded skateboarding game where your feet, not a button, do the trick, and a clean landing feels like the real thing. - **Canonical page:** https://gamecrew.ai/games/kerbside - **Play in browser:** https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/ - **Profile:** Playable in browser · Unity 6 · Multiplayer · Realistic geometry seen through a slight fisheye and video post-process: chromatic fringing, scanline noise, crushed blacks, bloom on lights, handheld camera sway. - **Verified versions:** 163 - **Fork it:** https://studio.gamecrew.ai/#/fork/kerbside (start your own game from this one, in the GameCrew studio) - **Plays:** Played 35 times ## Verification proof - Edit & structural checks: 548/548 passed - Automated playtests: 5/5 passed - Headless Chrome browser boot: verified (7.1 s) ## About Kerbside Ines Varga, a twenty-something skater with one battered deck, has one Sunday dawn before the Halvard Street car park and its riverside plaza are fenced off for demolition. Her friend Teo has a borrowed camera and one battery. If she can link the spot's ledges, banks and the seven-stair into one clean line, the footage outlives the concrete. **Player role:** You play Ines. Moment to moment you push for speed, carve to line up approaches, time your back-foot pop and front-foot slide to ollie or flip, lock into ledges and rails, and fight to land with wheels aligned to your direction of travel, scouting and retrying until a line comes together. ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/kerbside/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/kerbside/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/kerbside/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/kerbside/shot/3.jpg) ## Core mechanics - **Weight and Push:** The board is a rigidbody with real wheel friction, rolling resistance per surface (smooth paint, rough asphalt, cracked concrete) and lean-based steering through simulated truck geometry. Pushing adds momentum in pulses; tired rhythm loses speed. Speed is the currency every other mechanic spends: too slow and pops fall short, too fast and grinds overshoot. - **Two-Foot Pop:** Ollies are split into back-foot pop (right mouse) and front-foot slide (mouse drag). Pop height scales with crouch load and speed; the slide's timing levels the board. A sideways flick during the slide spins the board on its long axis using actual torque, so the board must be caught (release the drag) when grip faces up. Late or early timing gives a lower, tilted board that feeds directly into landing quality. - **Lock-In Grinds:** Grinds are not snapped: the truck or board contact point must reach a ledge or rail edge within tolerance, and the approach angle decides the trick (parallel = 50-50, angled tail = tailslide). Friction depends on the surface; waxing a ledge with a found wax bar lowers friction so slower lines become possible. Exiting requires a small pop, reusing the Two-Foot Pop input. - **Bolts and Bails:** Landings are judged physically: wheel alignment to velocity, board tilt and feet over bolts. Clean lands keep speed with a solid click; sketchy lands cost speed and wobble the camera; bad ones trigger a ragdoll bail. There is no score; Teo's camera records a take, and a line only counts if every element in it lands clean. ## World & stages - **Level 2 Car Park:** Flat painted concrete under a low ceiling teaches pushing rhythm, carving between pillars, braking and the basic two-foot ollie over parking bumpers of increasing height. - **Loading Dock Ledge:** A long chipped concrete ledge and a dock-edge drop teach lock-in angles, the difference between 50-50 and tailslides, and how finding and applying a wax bar changes friction. - **Drainage Banks:** Two angled concrete banks across a dry channel test speed management on slopes, carving transitions and flipping off a bank lip where timing changes with incline. - **River Plaza Seven:** The final plaza combines everything: a cracked run-up, a handrail-free seven-stair, and a waxed hubba beside it. With Teo filming, the player must link ledge, bank and stair into one clean take. ## Controls W: push (tap rhythm builds speed, holding pushes mongo-free steadily); S: drag foot to brake; A/D: lean heel/toe to carve; Shift: crouch to load the pop. Right mouse press: back foot pops the tail; mouse drag forward while airborne: front foot slides to level the board (ollie height depends on timing); flick mouse left/right during the slide: kickflip/heelflip; flick back: shove-it. Mouse in air: rotate shoulders for body rotation. Left mouse while near a ledge/rail: lock into grind/slide (truck position set by approach angle). Space: bail on purpose. R: reset to start of line. E: interact (pick up wax, toggle Teo filming). Tab: review last take. ## Design pillars - Physics decides, not animations: speed, angle and foot timing determine every outcome. - Clean over flashy: a bolted landing matters more than a big trick name. - The spot is the opponent: you read real-world surfaces, cracks and edges and adapt to them. ## Open-licence asset credits - Concrete Floor Worn 001: Concrete Floor Worn 001: Dimitrios Savva, Rico Cilliers, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Concrete Pavement: Concrete Pavement: Charlotte Baglioni, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) - Brick Wall 001: Brick Wall 001: Rob Tuytel, Dimitrios Savva, Poly Haven (CC0 1.0) ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)) # Fjordline > Leap from a granite wall under the midnight sun and carve one unbroken wingsuit line through Norway's most dramatic landscapes, from summit to sea, skimming close enough to touch the rock. - **Canonical page:** https://gamecrew.ai/games/fjordline - **Play in browser:** https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/ - **Profile:** Playable in browser · Unity 6 · Stylized low-poly realism: faceted procedural cliffs and ridges with sharp silhouettes, noise-displaced terrain, instanced cone pines and birch, simple cloth-like wingsuit, dense layered fog and scale-selling distance haze. - **Verified versions:** 12 - **Fork it:** https://studio.gamecrew.ai/#/fork/fjordline (start your own game from this one, in the GameCrew studio) ## Verification proof - Edit & structural checks: 35/35 passed - Automated playtests: 1/1 passed - Headless Chrome browser boot: verified (6.0 s) ## About Fjordline You are Sigrid Haugen, a wingsuit pilot attempting the Fjordline: one continuous flight that links a mountain wall, a waterfall fjord, a high plateau with its overhanging tongue of rock, and the island peaks of the far north. It is midsummer, the sun never sets, and the wind is right for one night only. Her late mentor sketched the line but never flew it; finishing it means landing on the fishing quay where he grew up. **Player role:** You play Sigrid in a wingsuit seen from a close third-person chase camera. Moment to moment you trade altitude for speed, read the terrain for lift, choose between safe wide lines and tight risky gaps, and thread lantern-lit stone cairns while your Rush meter climbs from hugging the rock. ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/fjordline/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/fjordline/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/fjordline/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/fjordline/shot/3.jpg) ## Core mechanics - **Glide Energy:** Speed and altitude are one budget. Pitching down or tucking converts height into speed; pitching up or flaring converts speed back into a short climb. Run out of both and you must deploy early. Every other mechanic either feeds or spends this budget. - **Proximity Rush:** Raycasts measure distance to terrain, water and trees. Flying within 8 m fills the Rush meter, which multiplies score, adds a small speed bonus and warms the screen edges to amber with wind-streak particles. Rush decays in open air, so the best lines hug walls between lift sources. Clipping the rock causes a tumble and respawn at the last cairn. - **Lift Sources:** Mist plumes at waterfall bases, sunlit slope faces and ridge-line updrafts push you upward, shown as drifting gold motes and shimmering air. Riding them refills altitude without spending speed, letting you extend the line or reach high cairns. Lift is often placed right against cliffs, so it pairs with Proximity Rush. - **Cairn Gates:** Stacked stone cairns with hanging lanterns mark the line and act as checkpoints. Passing between a cairn pair lights its lantern and banks your score. Optional tight cairns sit in risky gaps, worth more and only reachable with good Glide Energy or a lift source. ## World & stages - **The Troll Wall Exit:** Launch from a ledge on a sheer 1,000 m granite wall. Teaches pitch, bank and Glide Energy with a long safe dive along the face, then introduces Proximity Rush as the wall curves close. - **Sisterfall Fjord:** Drop into a narrow teal fjord lined with tall waterfalls. Teaches Lift Sources: their mist plumes are the only way to stay high enough to clear a headland. Optional cairns sit behind a curtain of falling water. - **The Tongue Plateau:** Climb on ridge lift over a high barren plateau to a horizontal rock tongue jutting over a lake. Tests all skills together: fly under the overhang through a tight cairn pair, or take the safer high line over it. - **Island Peaks of the North:** Final descent past jagged sea-island spires, red fishing huts on stilts and drying racks of fish. Tests precision at high speed while the sea opens below, ending with a choice of where to deploy for landing. ## Controls Mouse steers (move up/down to pitch, left/right to bank). W/S also pitch, A/D also bank. Hold Left Shift to tuck (dive faster, lose lift). Hold Space to flare (arms wide, bleed speed, gain brief lift). E deploys the parachute. R restarts from the last cairn. C toggles a wider cinematic camera. Esc pauses. ## Design pillars - Close is beautiful: the game rewards flying near rock, water and trees, never punishes caution with failure. - One breath, one line: the flight is a single continuous descent with no loading or cuts until landing. - The land is the level: every route choice comes from real-feeling terrain, not floating hoops. # Fernlight > Raise a carved whistle to your lips in a fog-drowned forest, coax a glowing bird onto your open hand, and point to send it off to light the dark. - **Canonical page:** https://gamecrew.ai/games/fernlight - **Play in browser:** https://gamecrew.ai/t/lr06Czg5xZlKmAxmcfEPLLEUhnAlR5oc/ - **Profile:** Playable in browser · Godot 4 · Plays in VR (WebXR) · Stylized low-poly with soft painterly textures, chunky rounded trees, broad leaf clusters and thick volumetric fog - **Verified versions:** 7 - **Fork it:** https://studio.gamecrew.ai/#/fork/fernlight (start your own game from this one, in the GameCrew studio) - **Plays:** Played 11 times ## Verification proof - Edit & structural checks: 10/10 passed - Automated playtests: 38/38 passed ## About Fernlight A cold fog has crept into an old forest and silenced it, and the small glowing birds that carry its light have scattered and hidden. You are the forest's last keeper, armed with nothing but a carved wooden whistle and your own two hands. Clearing by clearing, you call the birds back and send them to the dark bell-flowers, pushing back the fog until you reach the great tree at the forest's heart. If its canopy stays unlit, the forest goes quiet for good. **Player role:** You are the Keeper, a quiet forest warden standing among mossy stones. Moment to moment you listen for faint chirps, turn your head to find them, raise your whistle to call, hold out your palm for a bird to land, reach and throw pinecones to shake hiding birds loose, then point at a dark bell-flower to send the bird and light it. Between clearings you teleport across glowing moss stones. ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/fernlight/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/fernlight/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/fernlight/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/fernlight/shot/3.jpg) ## Core mechanics - **Whistle Call:** Lift the carved whistle to your mouth and pull the trigger to blow a note. Hidden birds answer with a chirp from their real position in 3D space, so you turn your head to find them. A bird that is free flies to you, while a stuck one keeps chirping until you free it with a thrown pinecone. - **Perch and Point:** Hold your hand out palm up and a called bird lands on it, warm and glowing, and lights your surroundings. Point your other hand at a dark bell-flower and squeeze the trigger to send it. Its glow clears a ring of fog and reveals new moss stones to teleport to. Sending it at nothing makes it circle back to your hand. - **Grab and Throw:** Pinecones, stones and glowcaps lie within reach on the ground and on stumps. Grab them with the grip and throw with a real arm motion. Hitting a bird's branch or hollow shakes it loose so it answers your whistle. Glowcaps can also be placed in the fog to light your way. - **Moss Stone Steps:** You move by teleporting between glowing moss stones, with snap turning for comfort. Each bell-flower you light uncovers the next stones, so lighting the forest is how you travel through it. ## World & stages - **Mossy Hollow:** Teaches the whistle, the open palm and pointing. One bird sits on a low stump in plain sight, and one bell-flower is lit to open the first stones. - **Fern Stream:** Teaches throwing. A bird is stuck in a high branch over a babbling stream, and you shake it free with a pinecone. Then you light two bell-flowers on the far bank and teleport across stepping stones. - **The Fallen Giant:** Tests listening and reaching. Three birds hide in a huge fallen log, and you find them by sound, lean to peer into hollows and reach in to coax one out. Lighting three flowers in the right order pulls back thick fog. - **The Old Heart:** The finale. You stand at the base of a vast tree and call every bird you have freed at once. They perch along both arms, and you send them one by one to the dark flowers high in the canopy. ## Controls | Action | Keyboard / Mouse | Gamepad | Phone Touch | VR Headset | | --- | --- | --- | --- | --- | | **Move** | WASD | Left stick | Left thumb pad | Left stick forward to aim teleport arc, release to jump to a | | **Turn / Look** | Mouse | Right stick | Drag on right side of the screen | Right stick left/right to snap turn; look with your head | | **Grab** | Hold left click | Hold right trigger | Hold the grab button | Grip to grab | | **Throw** | Release left click while moving the mouse | Release right trigger | Swipe up while holding grab | Swing arm and release grip | | **Whistle** | E | Y | Whistle button | Raise whistle hand to mouth and pull trigger | | **Open Palm** | Hold F | Hold left bumper | Hold palm button | Hold hand out palm up | | **Send Bird** | Right click on a target | Left trigger | Tap a flower | Point with free hand and pull trigger | | **Check Bracelet** | Tab | View button | Tap bracelet icon | Turn left wrist toward your face | ## Design pillars - Your hands are the interface: every action is a real gesture, never a menu - Listen before you look: sound leads, light confirms - Gentle and still: comfort and calm over challenge and speed # Two Crystals > Play Two Crystals directly in your browser — built and verified with GameCrew. - **Canonical page:** https://gamecrew.ai/games/two-crystals - **Play in browser:** https://gamecrew.ai/t/TMtFdu7QSt8Sw_nwVxm0u3buGPmhyvHy/ - **Profile:** Playable in browser · Unity 6 - **Verified versions:** 5 - **Fork it:** https://studio.gamecrew.ai/#/fork/two-crystals (start your own game from this one, in the GameCrew studio) ## Verification proof - Edit & structural checks: 40/40 passed - Automated playtests: 2/2 passed - Headless Chrome browser boot: verified (12.1 s) ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/two-crystals/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/two-crystals/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/two-crystals/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/two-crystals/shot/3.jpg) # Lantern Keeper > Play Lantern Keeper directly in your browser — built and verified with GameCrew. - **Canonical page:** https://gamecrew.ai/games/lantern-keeper - **Play in browser:** https://gamecrew.ai/t/-OO01wmWA02d-DRkJ70FFht9TvYRu5GA/ - **Profile:** Playable in browser · Unity 6 - **Verified versions:** 4 - **Fork it:** https://studio.gamecrew.ai/#/fork/lantern-keeper (start your own game from this one, in the GameCrew studio) ## Verification proof - Edit & structural checks: 26/26 passed - Automated playtests: 24/24 passed - Headless Chrome browser boot: verified (17.8 s) ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/lantern-keeper/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/lantern-keeper/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/lantern-keeper/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/lantern-keeper/shot/3.jpg) # Bisque > Bake yourself hard to smash through floors, soak yourself soft to bounce up walls, and climb out of a giant kiln before the firing turns you to stone for good. - **Canonical page:** https://gamecrew.ai/games/bisque - **Play in browser:** https://gamecrew.ai/t/bL6oWdN510ipSEfuwcA6ZznVNfCvKMaj/ - **Profile:** Playable in browser · Unity 6 · Chunky, handmade stylised 3D built from bevelled primitives: rounded shelves, stacked cylindrical saggars and brick tiles with a slight wobble, as if the whole world were thrown on a wheel. Surfaces use simple procedural noise for clay grain and thumbprint dents. Heat states are carried by emissive seams and colour shifts rather than detailed textures. - **Verified versions:** 3 - **Fork it:** https://studio.gamecrew.ai/#/fork/bisque (start your own game from this one, in the GameCrew studio) ## Verification proof - Edit & structural checks: 32/32 passed - Automated playtests: 8/8 passed - Headless Chrome browser boot: verified (5.9 s) ## About Bisque Pell is a palm-sized clay golem shaped by accident from the scraps of an old potter's wheel, and he wakes on the lowest shelf of a cathedral-sized kiln as the firing begins. The kiln heats in stages, and when the final firing peaks everything inside sets permanently, including him. The only way out is the chimney flue at the top, so he has to climb shelves, ledges and saggar towers by working the kiln's fire vents and water troughs to bake himself hard or soak himself soft. **Player role:** You play Pell, a small, round-shouldered clay golem with thumbprint eyes. From moment to moment you run and jump across kiln shelves, and you pick your state by stepping into a roaring fire vent (hard: heavy, glowing seams, short hop, smashes cracked tiles, sinks and walks underwater) or splashing into a water trough (soft: squishy, wobbly, long springy jump, clings briefly to wet walls and wall-jumps off them). A heat gauge shows the firing climbing toward its peak, so you read each room, plan the sequence of vents and troughs, and execute it. ## Verified gameplay captures - [Gameplay capture 1](https://gamecrew.ai/games/bisque/shot/0.jpg) - [Gameplay capture 2](https://gamecrew.ai/games/bisque/shot/1.jpg) - [Gameplay capture 3](https://gamecrew.ai/games/bisque/shot/2.jpg) - [Gameplay capture 4](https://gamecrew.ai/games/bisque/shot/3.jpg) ## Core mechanics - **Fire Vent Baking:** Standing in a vent's flame column for 1 second turns Pell Hard. His body darkens to terracotta with glowing orange seams, his mass triples, his jump height drops to about 1 unit and he walks slowly but cannot be knocked back. While Hard he can ground-pound cracked tiles to drop to lower routes or open shortcuts, sink through water to walk along trough floors, and stand on vent-blast gusts that would fling a Soft Pell away. Baking lasts until he enters water. - **Trough Soaking:** Entering any water trough while Soft keeps him Soft. Entering one while Hard rinses him back to Soft after 1 second of wading, or he can sink to the bottom and walk out of the far side still Hard. Soft Pell is pale grey-tan, wobbles with squash-and-stretch, jumps about 4 units high, carries more air control and bounces lightly on landing. Every room asks which state you need to be in when you leave the water. - **Wet Wall Cling:** Walls dark with seeping moisture, which glisten blue, let Soft Pell stick for 1.2 seconds on contact and wall-jump away at an angle. Hard Pell just slides down them. Some wet walls dry out when nearby vents pulse on a timer, so you have to climb between pulses. This ties baking and soaking together: you soak to climb, then bake at the top to smash the cracked lid of the next shelf. - **Rising Firing Heat:** The heat gauge fills over the slice in stages tied to progress, and each area the player reaches raises it one stage. At higher stages vents pulse more often and some troughs steam down to shallow puddles. These puddles still soften Pell but are too shallow to sink in. Standing still in a vent too long once you are already Hard overheats him: he cracks, flashes white and respawns at the last checkpoint. This keeps baking a deliberate choice rather than a safe spot to wait in. ## World & stages - **The Bottom Shelf:** Teaches movement and both states in safety. A low ledge is too high for Hard Pell, so you soak in a trough and bounce up. A cracked tile blocks the exit, so you bake in a vent and slam through it. The final gap needs a Soft long jump, so you have to find the second trough. - **The Trough Gallery:** Teaches sinking and wet walls. A deep channel of water must be crossed by walking along its floor while Hard. You emerge Hard, but the exit is up a wet wall, so you have to use a side trough to soften. That sets up the climb: wall-jump between two facing wet walls to a vent ledge. - **The Saggar Stacks:** Combines the states vertically. Towers of stacked clay boxes with cracked lids lead upward. Soak, wall-climb a tower, bake at the vent on top, slam through the lid into the water inside, then sink and walk out a side opening. Vent gusts here fling Soft Pell into fire unless he crosses them Hard. - **The Flue Throat:** The final test under peak heat. Wet walls dry with every vent pulse and troughs have shrunk to puddles. You chain soften-climb-bake-smash in timed rhythm up a narrowing chimney shaft toward the daylight above. ## Controls WASD to move relative to the camera. Mouse to orbit the camera. Space to jump (hard: short hop; soft: long bouncy jump, and pressing it again while clinging to a wet wall wall-jumps). Left Shift held while airborne as Hard does a ground-pound slam that breaks cracked tiles. Left Ctrl held as Soft does a squash crouch that charges a higher bounce. R restarts from the last checkpoint. Esc pauses. ## Design pillars - Your body is the tool: every obstacle is solved by choosing hard or soft, never by finding a key. - Readable heat: anything that bakes, cracks, soaks or burns shows it through clear colour and glow. - Always climbing: every room moves you upward toward the chimney light, and the rising heat keeps you moving. --- Contact: mailto:hello@gamecrew.ai