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.
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 each tool is the right fit
End-to-end verified engine builds
- 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.
Where GrowBlocks shines
- 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.
More AI game tool comparisons
GameCrew vs Tesana →
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 →
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 →
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 →
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 →
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 →
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 →
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 →
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 →
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 →
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.
Test GameCrew on your own game idea
Generate a free structured game pitch with three visual directions in two minutes, or join the alpha waitlist.