Roblox Publish Checklist
When to Load
Load before publishing a new experience or updating a live one. Test the surfaces that exist and the risks introduced by the change.
Quick Reference
1. Define the release
Record the changed places, scripts, assets, configuration, schemas, products, supported devices, and rollback path. Classify each gate as required, conditional, or not applicable before testing.
2. Block on high-consequence failures
- Persistence changed: load, save, migration, duplicate-session, disconnect, and shutdown behavior. Load
roblox-data or roblox-server-data.
- Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load
roblox-networking and roblox-security.
- Purchases changed: test durable, idempotent receipt grants and retries. Load
roblox-monetization.
- Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication. Load
roblox-cloud.
A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.
3. Exercise the shipped surface
- Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
- Test every supported input mode and representative viewport/device tier.
- Inspect runtime errors, memory growth, frame/network hot spots, and streaming behavior from measurements, not fixed object-count rules.
- Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
- Confirm experience metadata, visibility, places, thumbnails/icons, permissions, and policy declarations in the Creator Dashboard.
4. Require evidence
Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.
Output
READY, NOT READY, or READY WITH ACCEPTED RISK; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.
Full gate design and conditional matrix: references/full.md
1---2name: roblox-publish-checklist3description: Use before publishing or updating a Roblox experience to run evidence-backed release gates for the surfaces that changed.4---56# Roblox Publish Checklist78## When to Load910Load before publishing a new experience or updating a live one. Test the surfaces that exist and the risks introduced by the change.1112## Quick Reference1314### 1. Define the release1516Record the changed places, scripts, assets, configuration, schemas, products, supported devices, and rollback path. Classify each gate as required, conditional, or not applicable before testing.1718### 2. Block on high-consequence failures1920- **Persistence changed:** load, save, migration, duplicate-session, disconnect, and shutdown behavior. Load `roblox-data` or `roblox-server-data`.21- **Remotes or authority changed:** validate types, bounds, state, ownership, replay, and abusive frequency. Load `roblox-networking` and `roblox-security`.22- **Purchases changed:** test durable, idempotent receipt grants and retries. Load `roblox-monetization`.23- **Cloud auth or webhooks changed:** verify secrets, scopes, callback state, retries, signatures, and deduplication. Load `roblox-cloud`.2425A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.2627### 3. Exercise the shipped surface2829- Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.30- Test every supported input mode and representative viewport/device tier.31- Inspect runtime errors, memory growth, frame/network hot spots, and streaming behavior from measurements, not fixed object-count rules.32- Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.33- Confirm experience metadata, visibility, places, thumbnails/icons, permissions, and policy declarations in the Creator Dashboard.3435### 4. Require evidence3637Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.3839### Output4041`READY`, `NOT READY`, or `READY WITH ACCEPTED RISK`; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.4243> Full gate design and conditional matrix: [references/full.md](references/full.md)
tabooharmony