Forking
Let other people build on your published game — and make your own copy of someone else's.
A fork is an independent copy of a published game: its code, its assets, its own workspace and its own history. The person who forks it owns their copy outright; nothing is shared back.
It is off by default. A game can only be forked if its owner deliberately turns it on.
Making your game forkable
In Game Settings, switch on Forkable. Two conditions:
- The game has to be published. A draft cannot be forked.
- The platform checks every asset in the game first.
That check is the interesting part, and it is about rights, not code:
| What it finds | What happens |
|---|---|
| Everything is AI-generated by you, or under a clearly permissive licence (CC0, CC-BY, public domain) | Forkable turns on. |
| Anything carries a licence that isn't permissive | Refused, naming the asset that blocks it. Replace it or leave the game unforkable. |
| Assets with no licence recorded — which is most assets | You have to confirm explicitly that you have the right to let others copy them. Your confirmation is recorded. |
That confirmation is a real statement about rights you hold, and it is recorded with your account. If your game contains art you bought under a licence that doesn't allow redistribution — a pack whose terms cover your game only — do not make it forkable.
The check runs when you switch the toggle on. If you add a restrictively licensed asset later, the toggle does not re-check itself — turn it off if your game's contents change in a way that matters.
What forking your game means
- Anyone signed in, who doesn't already own it, gets a Fork button on your game's page.
- They get a complete, independent copy — code and every asset, not links back to yours. Your originals are untouched and your game keeps running.
- You are not notified, and you cannot see their copy. A fork starts as their private draft, and stays private unless they publish it.
- If they do publish, their game shows Forked from your game, and your game's page grows a Forks section listing games made from it.
Forking someone else's game
Click Fork on a game's page. You get a confirmation dialog first, which spells out what the operation actually does — a real, immediate copy that uses real storage, not a bookmark.
Confirm, and the copy is made while a full-page overlay blocks the page (don't navigate away; it takes a couple of seconds). You then land in the new project's editor, with the game already running.
From there it is an ordinary project of yours: chat with the agent, edit it, publish it under your own name.
Things to know:
- The copy comes from the published version, not the original's latest work in progress.
- The assets are yours now, so they count against your storage quota.
- It starts as a draft. Nothing is public until you publish it.
- There is no upstream. You cannot pull later changes from the original, and the original cannot pull yours. If you want to collaborate on one game instead of two, be a collaborator.
When to fork rather than collaborate
| Use | |
|---|---|
| Learning how a game was made, taking it somewhere else | Fork |
| Building a variant or a remix, under your own name | Fork |
| Working with someone on their game | Collaborator |
| Two people, one released game | Collaborator |