experience profile
description and links
select an experience to view its description.
administration
sign in to manage experiences, players, servers, configuration, and access.
experience access
choose the experience you want to administer.
experience administration
add or select an experience to begin.
overview
experience profile
select an experience to view its description.
readiness
activity
game contract
declared surface
build the game-facing contract with normal controls. imports, downloads, and raw json remain available for source-controlled workflows, but the cli is optional.
start from a game shape
pick a recipe, or select only the capabilities your scripts will use. this adds a clean starting contract; it never removes existing entries.
this is the exact API manifest generated by the controls above. project imports flatten their modules here automatically.
next steps
the contract declares what the control plane may validate and operate. values and releases have their own workspaces so schema edits never accidentally become production changes.
per-game catalog
define the data shapes your game owns here, independently from the game factory. types are reusable schemas; objects are named instances such as currency.coins or enemy.normalZombie. saving the catalog creates a contract draft only; it does not publish a place or push production.
reusable schemas
create a type once, then use it for any number of named objects. nested objects and typed lists are supported.
named game objects
an object references a type and gets a stable namespaced key. object values can be overridden by experience, place, server, or player scope.
draft values
edit the selected object's experience baseline or add scoped overrides. these values travel through the live-configuration draft and remain independent from place publishing.
live service releases
stage validated baselines and resource values, target deterministic player cohorts, then publish now or schedule activation. this updates connected servers without publishing the Roblox place.
universal baseline
deterministic overlays
a user-aware SDK read receives the candidate when the user is allowlisted or inside the stable percentage cohort. ordinary config reads always keep the baseline.
release controls
release history
player administration
live profile
standard character adapter
game integrations
saved destinations
live locations
persistent data
contract-bound data controls
analytics
conversion explorer
behavior debugger
per-experience commerce
follow each declared offer from presentation to an authoritative grant. source and reason are developer-recorded friction context, not inferred user intent. developer-product gross comes from processed receipts; game-pass value is an observed-price estimate.
selected experience · all offerings and developer-recorded contexts
declared catalog
volume
debug stream
player safety
enforced on join
player record
live presence
active window
player search
command center
compose
durable history
sdk access
credentials
accountability
durable log
access control
team access
root administration
experience lifecycle
these actions remove the experience records themselves, not just analytics. the root key stays outside the database and remains usable.
selected confirmation: delete-experience · all confirmation: purge-all-experiences
current selection
select individual rows from the events, commands, or audit views, then return here to remove only those records.
purge records