Short definitions of the words used across the studio, the panel, the market data and the developer API. Each links to the page that explains it, where there is one.
Studio words
Approved
A contract every signer has signed; it is locked, and nothing changes it, not even an owner. See Contracts.
Basis point
1/100 of a percent. A whole game is 10,000 basis points; a share is 1,000. See How a game is split.
Bonus point
One extra point each developer of a game earns when the third member buys a share of it, once per game. It lasts a week longer than release points. See Points.
Contract
The one agreement every project has: who made the game, each developer's part and the pool of shares. It goes through three steps:
- Draft
Generated at registration; developers and owners correct it freely.
- Submitted
Terms frozen in a PDF to sign; any change makes a new version.
- Approved
Every signer signed; locked for good.
See Contracts.
Crew
A game's crew is its developers and its lead. With owners, they manage the game's API key on its Developer tab and triage player feedback on its Feedback tab. This is not the retired "crews", the groups of members earlier versions of the studio had. See Getting a game's API key.
Developer
A member named on a project, with a part of the game. A game has 1 to 10 developers, each holding at least 10%. See Members, developers and leads.
Draft
A contract's first step: generated at registration with the developers' part shared equally, and corrected freely by the project's developers and owners. Nobody signs a draft. See Contracts.
Expired point
A point not spent by Monday 00:00 UTC of the third studio week after the week it was earned. It can no longer buy a share. See Points.
Game state
Where a studio game stands and what the public website shows. An owner sets it.
- Development
Hidden. Every new game starts here.
- Coming soon
A preview card with no Play button.
- Released
A card with a Play link; needs an approved contract.
- Paused
Hidden.
- Archived
Hidden; kept in the studio's records.
See Games and releases.
Lead
The member who looks after a game's details and updates log, set in its Manage game sheet. See Members, developers and leads.
Leaver
A developer removed from a project by someone else, who must sign the contract to leave. See Contracts.
Member
Someone the BlockoutGames GitHub organization admitted, who signs in to the panel with GitHub. See Sign-in and access.
Owner
The panel's admin role, from ownership of the BlockoutGames GitHub organization. Only owners open the Admin pages. It is a permission, not a statement about who owns the business. See Roles.
Points
What members spend to buy shares. When a game is released, each developer earns one point for every studio member who did not work on it. One point buys one 10% share. A point lasts its studio week and the two after. See Points.
Pool
The part of a game sold to the rest of the studio as 10% shares: 4 shares for one developer, 3 for two, 2 for three. See How a game is split.
Project
A studio game with its developers and contract. A project can exist before it has a Roblox game. See Projects.
Release week
The studio week in which a game was first read public on Roblox after its contract was approved. Points and the share sale count from it. See Games and releases.
Released
Two things, related but not the same:
- The Released state
Set by an owner; shows the game on the website with a Play link.
- Released for points
Recorded by the worker when the contract is approved and the collector first reads the game public. It earns the points and opens the share sale.
See Games and releases.
Scrywave
The platform's working name in its code and older documents; the panel is called Blockout Games Studio.
Share
10% of a game, bought with one point by a member who did not work on it, one per member per game. See Shares and the share sale.
Share sale
The weeks a game's pool is on sale: its release week and the two after, closing Monday 00:00 UTC three weeks after the release week. Unsold shares return to the developers. See Shares and the share sale.
Signed contract
The PDF made when the last signer signs: every signature in its block, a signature certificate with the audit trail, and a digital seal. See Signing a contract.
Studio game
A game in the studio's catalog, with its project, contract and hub at /studio/<universe id>. Games the studio does not own are market games. See A studio game's pages.
Studio week
Monday 00:00 UTC to the next Monday 00:00 UTC, named by its Monday. Contracts, releases, points and the share sale run on studio weeks. See Studio weeks.
Submitted
For a contract, submitted means its terms are frozen with their SHA-256 hash in a PDF that every signer signs. It is the second step, after draft. A change after submission makes a new version and clears every signature. See Contracts.
Universe
Roblox's name for a game; its id is the game's id in the panel and in the developer API. A universe holds one or more places.
Updates log
The hand-kept list of what shipped for a game. See The updates log.
Market and metrics words
ARPDAU
Average revenue per daily active user: Robux earned per player who played that day, as Roblox reports it (AverageRevenuePerUser). Studio games only, read once a day. See Studio game stats.
ARPPU
Average revenue per paying user: Robux earned per paying player, as Roblox reports it. Studio games only. See Studio game stats.
Breakout score
0 to 100: how strongly a game's players are rising right now, recomputed every 5 minutes from its hourly player counts. Called breakout in the developer API. See Growth and momentum.
CCU
Concurrent users: how many people are playing a game right now, at its last reading. Called ccu in the developer API; also "players now" or "players online". See Players and CCU.
Collector
The studio's worker that reads Roblox, Rolimon's and GitHub on schedules and stores what it reads. See Collector and data freshness.
Creator
A Roblox user or group that publishes games.
D1
Day-1 retention: the share of players who come back a day later, as Roblox reports it (ForwardD1Retention), as a ratio. Studio games only, read once a day. See Studio game stats.
D7 and D30
Retention after 7 and after 30 days, as Roblox reports it (ForwardD7Retention, ForwardD30Retention). Studio games only. See Studio game stats.
DAU
Daily active users: how many players played a game in a day, as Roblox reports it. Studio games only, read once a day. See Studio game stats.
Discovery
The panel page (/market/discovery) showing Roblox's sorts: where the studio's games rank in them and what is in each now. See Radar and Discovery.
Favorites
How many Roblox users have favorited a game, a running total at each reading. See Visits, favorites and likes.
Genre
Roblox's own filing of a game: a first-level genre (genreL1, such as Simulation) and a subgenre (genreL2). See Tiers and genres.
Growth
The change in a game's players as a ratio: 0.5 is +50%. Read against 1 hour, 6 hours, 24 hours and 7 days ago, and day on day for the daily mean. Empty means not enough history yet, not zero. See Growth and momentum.
Like ratio
Upvotes as a share of all votes, 0 to 1. See Visits, favorites and likes.
MAU
Monthly active users of a studio game, as Roblox reports it. See Studio game stats.
Observed peak
The most players seen in a game since the platform began tracking it, not its all-time peak. See Players and CCU.
Owned analytics
The daily numbers Roblox reports only to a game's owner (active users, retention, playtime, revenue and more), read for the studio's own games with group keys. See Studio game stats.
Payer rate
The share of a studio game's players who paid, as Roblox reports it. See Studio game stats.
Radar
The panel page (/radar) that ranks rising games by breakout score, in four lists. See Radar and Discovery.
Rolimon's
An outside site that lists Roblox games' player counts. The collector reads its list every 10 minutes and tracks every game on it. See Discovery, sorts and recommendations.
Snapshot
A snapshot is one reading of a game's public numbers (players, visits, favorites, votes) at one moment. See Freshness and empty numbers.
Sort
A row on Roblox's discovery page, such as Up-and-Coming or Top Trending. Being in either puts a game in the hot tier. See Discovery, sorts and recommendations.
Sponsored
A paid placement in a Roblox sort, flagged isSponsored in the developer API. It is recorded but not treated as a sign a game is rising. Sponsored recommendations are not stored. See Discovery, sorts and recommendations.
Stickiness
Daily active users over monthly active users, for a studio game. See Studio game stats.
Tier
How often the collector reads a game:
- Hotevery 5 minutes
Surging, or in Up-and-Coming or Top Trending.
- Activeevery 15 minutes
1,000 players or more.
- Warmevery hour
25 players or more, or 5 or more if under 30 days old.
- Coldevery day
Below warm.
- Deadevery week
No data three reads in a row.
See Tiers and genres.
Velocity
Players a game gained per hour over the last three complete hours. Acceleration is how that changed against the three hours before. See Growth and momentum.
Visits
Roblox's running total of a game's visits at each reading. See Visits, favorites and likes.
Panel words
Assistant
The chat that opens from the round button at the bottom right, or with i. It reads the studio's data and this handbook, and changes nothing. See The assistant.
Handbook
This documentation, public at docs.blockoutgames.com, written for members, developers and the assistant. Docs in the panel's account menu opens it.
Quick jump
The panel's search, opened with Ctrl+K or ⌘K, / or the Search button: any page, studio game or tracked market game by name. See Keyboard shortcuts.
Session
Your signed-in state in one browser, after signing in with GitHub: it lasts 30 days from its last extension and never more than 90 days from sign-in. You see and end yours on Settings, Sessions. See Sign-in and access.
Watchlist
Your own list of games to keep an eye on, on the Watching page, with notifications about them. See Watching games.
Widget
A card placed on your home page. See Your home page.
Developer API words
Game API key
The key a studio game's Roblox servers send to the developer API: bk_live_ and 43 characters, one in use per game, shown once. See Getting a game's API key.
Fingerprint
How the panel shows a game's key after it is made: bk_live_… and its last four characters.
Group key
The one Roblox Open Cloud key registered for a Roblox group, used for registration and owned analytics. Not the game API key. See Roblox groups and keys.
Idempotency key
The id a game's server gives each piece of feedback, sent again with every retry, so the platform stores it once. See POST /developer/v1/feedback.
PlatformService
The Blockout Roblox Template's service that calls the developer API through a shared cache and sends feedback. See The Template's platform service.
Rate limit
How many requests the developer API accepts, in fixed one-minute windows:
- Per keya minute
120, for every server of the game together.
- Every key togethera minute
1,200.
- Posts from one addressa minute
Over it, 429 and Retry-After. See Errors, limits and polling.
Rotate
Replace a game's key with a new one; the old one stops at once. Revoke stops a key with no replacement. See Getting a game's API key.
Stale answer
In the Template's platform service, an older cached answer (up to an hour old) served with stale = true while the platform cannot be reached.
Retired words
These belonged to earlier versions of the studio and are no longer used. Their old rows are kept until a founder decides to delete them.
- Release cycles
Periods an owner opened by hand; replaced by studio weeks.
- Teams and the old crews
Groups of members; members now attach to a game as its developers.
- The finance ledger
Money owed and paid; the panel now records ownership only.
- Personal Roblox keys
Keys in Settings; replaced by one group key per Roblox group.
- Roblox login
The old sign-in; replaced by GitHub.
A game's crew today means its developers and lead.
Updated