The Feedback tab (/studio/<universe id>/feedback) lists what players sent through the game's servers, newest first, and lets the game's crew triage each piece. Feedback arrives once the game's servers send it with the key from the Developer tab, usually through the Luau module.
Who can see the Feedback tab
Only owners and the game's crew (the developers on its project and its lead) read and triage a game's feedback. It holds Roblox player ids and players' own words.
The list, its filters and counts, and a Status dropdown on every piece.
What a piece of feedback shows
- Category
Bug, Suggestion, Balance, Praise or Other, as the game sent it.
- Received
When it arrived; hover for the exact time.
- Player
The Roblox user id it came from, when the game named one.
- Place and version
The place it was sent from, and the version of the server that sent it, when given.
- Textcharacters
The player's words, up to 2,000. A game key pasted into the text is replaced with
bk_live_[removed]before it is stored, so it never reaches the crew or the assistant.- Last change
Who last changed its status and when ("Planned by Sam, 2 hours ago").
Player reports
A game built on the Template before v1.0.0 also sent its players' reports of other players here, as feedback of category Other whose text starts "Player report". The game's servers batched them, so one piece can hold several reports. Each report names the reason, both players and their user ids, the server's job id, the reporter's filtered note and the reported player's last five chat lines exactly as typed. A piece holding one reporter's reports shows that reporter as its Player; a piece from several reporters shows none.
The Template removed its player report in v1.0.0: Roblox's own report in the Roblox menu covers it, so a game on the current Template sends none. Roblox's moderation stays the authority; a report changes nothing for the reported player. Reports already received stay like any other feedback.
Feedback statuses
Every piece starts as New. The crew moves it with the Status dropdown on its right:
- New
Nobody has looked at it yet.
- Seen
Read, nothing decided.
- Planned
The crew means to act on it.
- Done
Acted on.
- Ignored
Not acted on.
There is no fixed order: any status can be set from any other, New included, and the last change wins. Each change records who made it and when; earlier changes are not kept.
How to triage feedback
Open the Feedback tab
Open the game's hub, then Feedback.
Show what needs looking at
Choose Status, then New.
Set each piece's status
Change the Status dropdown beside a piece. It saves at once; there is no Save button.
If the change is refused or the studio cannot be reached, the dropdown goes back and says "The status was not changed."
Filtering feedback
The filters above the list are kept in the address, so a filtered view can be shared:
- Category
Every category, or one. Each option shows how many pieces it has.
- Status
Every status, or one, each with its count.
- From and To
Days, inclusive, in UTC (
?from=2026-10-01&to=2026-10-24).
The counts beside each category and status are for the days chosen, whatever the other filters say. Clear removes every filter. With nothing matching, the list says "Nothing matches these filters".
Pages of feedback
The card's title line says how many pieces match, newest first. The list shows 50 at a time; the pager at the bottom moves to the previous and next 50 ("Feedback 51 to 100").
How fresh the Feedback tab is
Feedback is stored the moment the game's server sends it and is on the tab the next time it is opened or reloaded. The tab does not refresh itself.
How long feedback is kept
What the Feedback tab asks the API
The tab reads and changes feedback through the panel's own API, with your session; these routes are not part of the developer API a game's servers call. Nothing here is cached: a status changes under the person looking at it.
GET/v1/studio/games/:id/feedback
One page of a game's feedback, newest first, with the counts per category and status for the days chosen.
Query
categorystringbug,suggestion,balance,praiseorother.statusstringnew,seen,planned,doneorignored.fromstring- First day,
YYYY-MM-DD, UTC, inclusive. tostring- Last day,
YYYY-MM-DD, UTC, inclusive. offsetnumber- Pieces to skip, 0 to 100,000; 0 by default.
limitnumber- Pieces per page, 1 to 50; 50 by default.
PUT/v1/studio/games/:id/feedback/:feedbackId/status
Sets one piece's status and answers with the piece as it now stands.
Body
statusstringRequirednew,seen,planned,doneorignored.
Both answer 403 to anyone but owners and the game's crew, and 404 for a game that is not in the studio or a piece that is not the game's. A change also needs the panel's x-requested-with header, or it is refused (403).
The Feedback tab on a phone
The filters stack full width. Each piece's status dropdown sits under its text on a phone and to its right from 640 px.
Related: A studio game's pages, Feedback API, POST /developer/v1/feedback, Getting a game's API key, Errors, limits and polling.
Updated