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