Before opening Studio

Playtest the Build version and record:

  • the current player goal;
  • the core loop and win or fail state;
  • controls and interface behavior;
  • known issues; and
  • the specific reason Studio is needed.

This baseline makes it possible to tell whether a manual edit breaks generated behavior.

Make the handoff deliberately

  1. Open the Build project in Roblox Studio using the available project workflow.
  2. Confirm the correct project and current playable state.
  3. Make one focused manual change.
  4. Test the complete loop, not only the changed element.
  5. Repeat for additional edits.
  6. Review the publishing and maturity-label flow before release.

Roblox’s current documentation confirms the handoff but does not provide a universal minimum device specification or approval time for the resulting project.

Automatic Moderate rating

Build can provide an automatic Moderate rating while the project remains in the prompt-based workflow. Roblox says changes beyond prompting, including custom code, can remove it.

After that change, complete the content and maturity questionnaire before publishing. Do not assume that the previous automatic rating describes the manually edited version.

Publishing after Studio edits

Run a fresh safety and content review of the actual Studio version. Check all generated and manually added content, then follow the rating and publishing steps shown by Roblox.

The publishing guide explains the initial 16+ audience, while Build vs Studio helps choose the right transition point.

Common problems

  • The wrong version is edited: verify the playable baseline before changing it.
  • A custom edit breaks the loop: test start, progress, fail and restart paths.
  • The old rating is assumed to persist: complete the questionnaire when required.
  • Publishing expectations changed: follow the current Studio-side flow for the edited project.