BC-0116 · CORE GUIDE
Editorial review 2026-09-26
Roblox Build and Creator Hub
Use Creator Hub to find the documentation for a task, then distinguish that reference from the place where you perform the action. Build chat, Creator Dashboard, Studio and account settings are different surfaces. A general creator guide does not establish that its controls exist inside Build.
Objective
Route a creator task to the correct reference and working surface with a concrete completion condition.
Before you start
- State the task's intended output.
- Identify the project or game where an action would apply.
- Distinguish reading a guide from changing a setting or version.
Steps
- Write a task card with the intended output.
- Find the current official reference for that task.
- Check the guide's prerequisites and assumed working surface.
- Confirm the selected target before any state-changing action.
- Record the observed result or the unresolved requirement and return to the original task.
Verification
- The card distinguishes a documentation URL from an action surface.
- The target identity remains consistent across the handoff.
- The completion condition can be observed rather than inferred from navigation.
- General creator capabilities are not labelled as controls inside Build chat.
Limitations
- This routing guide cannot inspect account permissions.
- A general creator tutorial may describe capabilities outside the current Build workflow.
- The version consequences of actual Studio editing remain a separate decision.
Working notes
Route the task by its output. A prompt revision changes a design request; a documentation lookup explains a requirement; a management action changes a selected game's configuration; a Studio edit changes a working version. Writing that output first prevents wandering through similarly named pages without knowing which state should change.
Keep identity attached to every handoff. Record the account context, game or project and the intended action, without copying private credentials. A dashboard showing a familiar title is not enough to establish that it is the same destination referenced by a published link.
Read prerequisites before following a general guide. A Studio tutorial may assume direct access to scripts or objects, and an analytics page may have account or data requirements. Those assumptions need to be checked in the intended workflow rather than imported into a Build prompt as a feature promise.
Return with an observable result. After a documentation lookup, the result can be a clarified requirement. After a management action, it should be the actual saved or pending state shown. After an editing handoff, keep the version and status consequences explicit. A visited page alone is not completion of any of those jobs.
Examples
- Task card: question = why does the intended audience differ from the creator's age? First destination = current audience documentation; output = the relevant rule and unresolved account question. No game configuration needs to change merely to read the answer.
- Management card: action = inspect a video submission; target = a named game and place; output = the displayed submission state. The source guide and the management screen are recorded separately.
- Editing card: the next behavior needs direct object inspection. Read the Studio handoff consequences before editing, then record the working version rather than treating documentation access as a reversible mode switch.