Change someone’s game: branch a showcase game and open a merge request
Branch a public GameCrew AI game, change it yourself or with your assistant, and open a merge request. The owner plays it before and after, then merges.
What you’ll have at the endA merge request into a game’s main line with your change, checked by its engine, that its owner can play before and after and merge.
What you need
- A GameCrew AI account: Contributor or Platform.
- A public game to change: every showcase game is public.
Steps
Find the game
In the studio, Explore lists the public games, the showcase included. Open the one you want to change.
Make a branch
Press New branch, or open the Branches tab. Name it after the change (2 to 24 characters of a–z, 0–9 and -) and press Create branch. With an assistant:
create_branch.red-boatChange the branch
On a Platform account the branch opens on Build: describe the change and press Make the change. On the Contributor tier, your assistant works on the branch by its id with
read_file,edit_fileandrun_unity.Save a version
save_version. On a branch it is a quick save: it compiles and builds the game for the browser, and the version is marked not checked.full: trueruns the full check now.Look at it the way the owner will
get_changeshows what the version changed: pictures of each view before and after, both play links, and the diffs.Pick a handle
The owner sees your handle, never your email. Pick one on the Usage page, or with
set_handle. Until you do, you are shown as “a contributor”.Open the merge request
On the branch’s Merge requests tab, write its title in a line, add more if you like, and press Open merge request. With an assistant:
open_merge_request.The owner reviews it
The owner and the game’s crew can play it, comment on one view, asset or file, and give a verdict. Only the owner merges. Merging runs the full check first, and main gets a new version only if it passes.
Answer a request for changes
Change the branch, save again and update the merge request (Update to v…, or
open_merge_requestagain). Notifications tell you what happened (get_notifications, or the bell in the studio).
Limits
From outside a game’s crew: 1 branch of each game, 5 across the studio, 3 open merge requests per game and 10 merge requests a day. Work on a branch spends your own budget and engine minutes.
Branch or fork?
A branch belongs to the game and goes back into it. A fork is a game of your own, where the owner allows forks (every showcase game does).
Play one first
More
Connect your assistant now
Add this address as a connector, or tell a coding assistant “Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md”.
https://play.gamecrew.ai/mcp