Place the Keycaps Launch Snapshot

Launch Snapshot: direct answer

The verified launch identity is universe 10388509406, root place 103060898621269, creator KEYBOARDS!!!!!, created June 24, 2026 UTC, with a 25-player server maximum.

Sources reviewed: Roblox Games API and Place the Keycaps - Roblox.

Launch Snapshot: verified facts

Launch Snapshot: player workflow

Stable identity fields

Use the universe ID, root place ID, and creator group to distinguish this experience from similarly named games. The API creation date is historical, while the description and title can change throughout beta. Server size is currently reported as 25.

Snapshot-only fields

Playing, visits, favorites, and updated time are moving counters. In the July 14, 2026 Shanghai-time review, the API returned roughly 4,658 playing, 1,393,377 visits, and 17,572 favorites; those values are evidence of one request, not permanent page copy. Any chart should store the fetch timestamp and raw value so later growth comparisons use the same metric rather than manually rounded homepage numbers.

Launch Snapshot: verification checklist

• Preserve universe, root place, creator, and created time as identity/history fields.
• Store title, description, updated time, playing, visits, and favorites with each fetch timestamp.
• Do not overwrite an earlier snapshot when collecting the next data point.
• Use the current maxPlayers value as configuration, not proof of a full server.
• Compare daily values only after normalizing UTC and Shanghai reporting dates.
• Keep Roblox engagement separate from wiki analytics and advertising metrics.
• For trend analysis, collect the same endpoint on a stable schedule and flag failed requests rather than interpolating values.
• Retain exact integers in storage even when a public summary rounds them for readability.
• Document HTTP failures and retry time so a missing value is not silently treated as zero activity.

A launch snapshot is strongest when it preserves exact identifiers. Place ID, universe ID, creator group, server size and checked date let later editors compare a new API response without replacing player guidance with speculation.

This snapshot should remain comparable. If a later worker refreshes the API, keep the old request in reports and add the new request beside it. Replacing historical numbers without a date removes the evidence trail players need for update-sensitive claims.