Pinned metrics: track how far playtesters get

A pinned metric answers "how far do testers get?": how many reached level 3, and after how much play time. It reads a number from testers' saved state, so the game has to keep it in localStorage as JSON (see Game state).

Pin one#

On the game's dashboard in the studio, find Pin a metric. Give it a label (say, "Level") and pick the number from the list: it shows every number Betacade has seen in testers' saves, with an example. The list fills in once a tester has played a build that saves to localStorage.

Only JSON numbers count; strings and missing values are ignored. A game can have 5 pinned metrics. Pinning one also counts the saves already synced, so earlier plays aren't lost.

Read it#

Each metric gets a card on the dashboard: how many testers reached each value, the median play time it took them, and where testers are now.

Keys and paths#

A metric points at a key and a path inside its JSON value. With save holding {"level": 3, "stats": {"deaths": 12}}, the paths are level and stats.deaths. Keys starting with secret: are never synced, so they can't be pinned.