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