Studio data
Everything Ravensight holds for your studio, and how fresh it is.
Open Studio > Studio data in the dashboard, or ask
from your own agent with describe_studio_data over
MCP.
What it shows
One row for each kind of data in
what data Ravensight holds, grouped the
same way: player data, commercial, development, studio memory and
operations. Each row gives how many records of that kind your studio
has, when something was last added, how long it is kept, and a link to
the page that holds it. Events are one total across the games in view
over the last 30 days; the per game counts are in the
games list that describe_studio_data returns.
A row with nothing in it reads Nothing yet.
It reads counts and dates only, never the records themselves: no event properties, sale amounts, post text or document bodies. It reads your own studio only, through the same membership checks as every other studio read. The retention text comes from the same generated list as the table above, so the two cannot disagree.
All games or one game
With one game picked in the switcher, this page counts that title's
games. Under All games it counts the whole studio, with a filter to
narrow it to one title. Some counts are only made for the whole studio
rather than for one title: sales, Pulse, brainstorms, marketing
touchpoints and similar records. A one-game view leaves those uncounted
instead of guessing which share is the game's, so choose All games in
the switcher to see them.
Every member sees every project in the studio. Only an MCP token can
be limited to some projects, and such a token is refused by
describe_studio_data, because it reads the whole studio.
A count that could not be read, for example because a store was briefly unavailable, is shown as not counted, never as zero. Results are cached for up to five minutes, so a record you just added may take that long to appear.
Needs attention
Above the rows, Studio data lists what needs your attention, each with a link to the place that fixes it. Nothing here charges you or starts a payment.
- A connection that needs attention: repeated failed syncs or a key to re-enter. One failed sync is retried and does not show here, and this hint appears only in the whole studio view. Open Connections in Settings to see why and, for a refused key, paste a new one.
- Events about to start aging out. A game whose oldest events reach its retention limit (90, 180 or 400 days) within the next 30 days. The hint shows only in that window: once removal has started it is the normal state for a game older than its retention, so there is no hint. Lifetime totals survive; extended retention keeps the events themselves.
- An unfunded account. MCP reads need a studio that has funded a prepaid balance at least once, so your own agents are refused until it has. See usage, billing and limits.
What it costs
The dashboard page is included, with no charge. Over MCP,
describe_studio_data is one metered read: 100,000 weighted
events on the shared event meter, drawn from the included monthly
events first and then the prepaid balance, and it needs a studio that
has funded a prepaid balance. It reads the whole studio, so a token
limited to some projects is refused, and a refused call is not
charged. Huginn, the AI analyst, can use it inside the one AI unit a
question already costs.