Players' feedback arrives on a studio game's Feedback tab, each piece as New. This recipe works through it in one sitting: new bug reports first, then the rest, each set to Seen, Planned, Done or Ignored, with the assistant to summarise and to mark pieces for you.
Before you start
You are an organization owner, or on the game's crew (a developer on its project, or its lead). Nobody else can read a game's feedback.
The game sends feedback: its servers post it with the game's key, through the Template's Feedback window or POST /developer/v1/feedback. Nothing arrives until they do.
Steps
Open the Feedback tab
Open the game from Studio's Games page, then Feedback (
/studio/<universe id>/feedback).Show new bugs first
Set Category to Bug and Status to New. The counts beside each option are for the days chosen. The filters are kept in the address, so you can share the filtered view.
Narrow to this week, if you like
Set From and To (UTC days, inclusive), for example the days since the last update. Place and version on each piece says which server version it came from.
Set each piece's status
Change the Status dropdown beside it: Planned for a bug you will fix, Ignored for one you will not, Seen when nothing is decided. It saves at once; there is no Save button.
Do the other categories
Set Category back and work through Suggestion, Balance, Praise and Other the same way. Clear removes every filter.
Close out after a release
When an update ships, filter Status to Planned and set what it fixed to Done.
Let the assistant read and mark feedback
On the Feedback tab, open the assistant (i) and ask it to read, or to mark:
"What new bug reports came in this week?"
"Summarise this game's balance feedback from the last 30 days."
"How much feedback is still new?"
It reads the game's feedback by category and status over up to 365 days, without player ids.
Read feedback from outside the panel
The panel's own routes, GET /v1/studio/games/:id/feedback and the PUT that sets a status, take a member's session, not a game's key; they are described on A game's Feedback tab.
A game's servers read the same page with the game's key: GET /developer/v1/game/feedback answers the key's own game's feedback, with the same filters, and the Template's PlatformService.feedbackList and its staff Feedback tab in the admin panel use it. Player reports from a game on a Template before v1.0.0 arrived here as Other: see player reports. Setting a status stays in the panel: a key can read feedback, never triage it.
Send a test piece
To check the pipe end to end, send one piece with curl and mark it Ignored on the tab:
curl -s -X POST https://studio.blockoutgames.com/developer/v1/feedback \ -H "Authorization: Bearer $BLOCKOUT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"idempotencyKey":"test-0001-feedback","category":"other","text":"Testing the feedback route","placeId":98765}'202 with a receipt means it is stored; it is on the tab the next time it is opened or reloaded.
What you get
A Feedback tab where New means not yet looked at, Planned is the crew's list of what to do, and Done records what shipped, each with who changed it and when.
Every field, filter and status.
How a game's servers send feedback.
The Template's platform service
The in-game Feedback window and its limits.
More questions the assistant answers.
Updated