GameCrew AIEarly access
Sign in
CASE STUDY · UNITY 6 URPFlat Desktop & Mobile Touch

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.

Starting brief"Wave racer game" ($0.15 pitch)
Engine & outputUnity 6 URP · C# + WebGL
v3 automated tests13/13 unit · 31/31 play
WebGL boot & errors5.4 s boot · 0 browser errors
Assets built in-loop5 custom 3D models · 16 sound assets
All 3 rounds combined181 min compute · $14.86

Round-by-round builds & verified gates

RoundPrompt / FocusEffort / BudgetScopeVerified 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 & verification 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.

Related references

Questions about Breakline

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.

More case studies

CASE STUDY · THREE.JS + WEBXR VR

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.