The studio's rules say who may do what, how a game is registered and split, when it counts as released, and how members who did not make it come to own part of it. Every rule is enforced by the panel and the API, not by hand. For the story from idea to release, start at How the studio works.
The rules in numbers
- Developers per game
1 to 10, each holding at least 10%.
- A shareof a game
10%, or 1,000 basis points. One point buys one.
- The poolshares
4 for one developer, 3 for two, 2 for three.
- Points at releaseper developer
One for every member who did not work on the game.
- The bonus point
One per developer when the third member buys a share.
- The share saleweeks
The release week and the two after.
- A point's lifeweeks
The week it was earned and the two after.
- A studio week
Monday 00:00 UTC to the next Monday 00:00 UTC.
- Release checkminutes
The worker looks for newly released games every 5.
Who and what
Owner and member, from the GitHub organization, and who can do what.
The hats people wear on a game.
One Open Cloud key per group, and what it reads.
Registering a game, with or without a Roblox game yet.
From contract to release
Developers' parts and the pool, by the number of developers.
Draft, submitted, approved: what locks when.
The PDF, the electronic signature and the sealed contract.
Game states, the release gate and release for points.
What shipped, and how each update moved players.
Points, shares and weeks
Monday 00:00 UTC, and everything that counts from it.
Earned at release, spent on shares, expired after three weeks.
Who can buy, when, and what happens to unsold shares.
Updated