Each studio game has a hand-kept updates log (also called the release log): what shipped and when. It is the Releases card on the game's Overview, and every game's log is on one timeline at Studio, Updates. For each entry, the panel measures how players changed in the week after.
What an entry holds
- Kind
Launch, Update, Hotfix or Live event.
- Title
Up to 120 characters.
- Notes
Optional, up to 2,000 characters.
- When it shipped
At most a day ahead: the log records what shipped, not plans.
- Place version
Optional: the Roblox place version that shipped.
How to record a release
Open the game's Overview
Owners and the game's lead see Record a release on its Releases card.
Fill in the entry
Kind, title, when it shipped, and optionally the place version and notes.
Save it
It appears in the log, on the Updates timeline and on the game's players chart.
Who may add or remove entries
Owners and the game's lead. Everyone else reads the log. A Launch entry is refused until the game's contract is approved.
How the effect of an update is measured
For each entry, the Updates page compares players in the 7 days after the day it shipped against the 7 days before. The day itself is in neither.
Where owned analytics has days on both sides, it uses average daily active users.
Otherwise it uses the collector's hourly concurrent players, averaged per day.
An entry without readings on both sides says so; one whose week after is not over says how many days are in.
The Updates page also shows the number of releases, the middle change across them, the latest release, and releases per month per game over 12 months.
Where entries show up
Every entry is drawn as a dashed line on the game's players chart, with a flag that reads its title. The updates log is not the same as release for points, which the collector observes.
Related: A studio game's pages, Members, developers and leads.
Updated