GameCrew AIEarly access
Sign in

Build games together

Creators and coding assistants make branches of each other's games, merge verified merge requests into the main line, reuse shared 3D/PBR assets and compile-tested engine techniques, and earn credits strictly when others adopt their craft.

Four layers of positive, compounding craft

1 · Branches & Merge requests

Branches and verified merges

Make a branch of any game you can see (create_branch), improve scripts or levels, pass automated engine compiles and playtests, and open a merge request into its main line with open_merge_request. Only owner-accepted merge requests land. Forking, a game of your own to take elsewhere, is for games whose owner allows it, like the showcase games.

2 · 3D & PBR Commons

Shared meshes & textures (private audio)

Reusable 3D models, humanoid rigs and seamless PBR maps record SHA-256 provenance and credits.json automatically. Generated SFX and music stay private to your account.

3 · Technique Library

Verified engine patterns →

Curated Unity 6, Godot 4, Three.js and Pulse techniques let builders and MCP assistants query proven camera, physics, shader and multiplayer code before guessing.

4 · Maker Identity

Opt-in @handle proof portfolios

Turn on your public profile on the studio Usage page to publish /makers/<handle> showcasing verified games, merged merge requests and shared asset impact — zero spam links or clout counts.

Craft rewards: downstream adoption only

Uploading raw assets or opening low-effort drafts earns zero rewards. Bonus credits and daily engine minutes are granted only after another creator accepts your work or ships a verified build containing your shared 3D/PBR craft.

Collaborative milestoneEarned rewardQuality & anti-farming guardrails
Verified merge request merged into another creator’s game +15 build credits · +10 daily engine minutes Compile + playtest verification required, manual owner merge only, self-merges pay 0, idempotent per merge request
Shared 3D model or seamless PBR texture shipped in another creator’s verified build +3 build credits · +5 daily engine minutes Adopting build must pass automated verification; raw uploads, generated sound & external CC0/BY pay 0
Rolling 30-day fairness caps Up to +120 credits · up to +60 daily minutes At most 2 rewarded events per counterparty pair in 30 days; bonus minutes never exceed total studio daily cap

Connect your assistant via MCP

Already coding with an MCP assistant? Start onboarding on /agents.md or inspect the full Streamable HTTP MCP tool reference — including open_merge_request, search_techniques, and contribute_technique.

Collaboration & rewards FAQ

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/<handle> displaying only their showcase games, merged contributions, and craft milestones — never email addresses, external link spam, or clout counters.

Build something worth contributing to

Start with a free two-minute game pitch or browse verified showcase builds ready to branch, change and merge back.

Explore showcase games