BC-0024 · CORE GUIDE
Editorial review 2026-09-26
Your First Roblox Build Prompt
Write the first prompt around an observable player action, its feedback and a way to retry. Describe the smallest loop you want to inspect; leave shops, campaign progression and unrelated systems for later decisions.
Objective
Produce a first instruction whose success and failure can be checked without adding another system.
Before you start
- Access to the actual creation workflow is already working; resolve a missing Build entry separately.
- Keep a copy of the intended brief outside the chat so you can compare it with the generated result.
- Choose the player's immediate action and the visible outcome that would make this attempt complete.
Steps
- Write the player action as a verb and a target, such as guide the courier to the delivery dock.
- Describe the feedback that confirms the action and the condition that ends an attempt.
- Specify what retry clears and where it places the player; do not leave reset behavior implicit.
- Add only presentation details needed to read the route, target and hazards.
- Name excluded systems so the first output has a clear scope boundary.
- Send the brief, inspect the result and save the first concrete mismatch before requesting a revision.
Verification
- From the opening scene, identify the objective without relying on an explanation outside the game.
- Reach the target and confirm that the attempt enters its intended completed state.
- Trigger failure deliberately and check that retry is understandable and usable.
- Retry after both outcomes and verify that stale success or failure state does not carry over.
- Compare the generated systems with the cut list; record any unrelated addition before expanding the brief.
Limitations
- This prompt is an original editorial example, not official syntax or a guarantee of generated behavior.
- A working prototype does not establish sharing availability, publishing eligibility or audience approval.
- Preserve a description of the working state before revisions; a prompt asking to keep it unchanged is not a verified rollback mechanism.
Working notes
Begin with what the player does, not with a genre label. 'A space game' could mean aiming, racing, collecting or trading. 'Guide a courier to a marked dock while avoiding drifting debris' identifies an interaction that you can inspect after generation.
State what should happen when that interaction succeeds or fails. Arrival needs visible confirmation; a collision needs a deliberate consequence. Without those conditions, an attractive scene may still leave the player unsure whether anything happened.
Keep presentation subordinate to the test. A setting and a readable visual style can help describe the scene, but a long list of effects makes it harder to identify which part of the initial loop is missing. Save decorative requests in a separate note.
After sending the prompt, compare the result with the requested behavior. Record a concrete mismatch such as 'restarting keeps the completed objective' instead of 'the game is bad.' That observation becomes the next bounded instruction. These are proposed editorial tests, not a claim that we ran this game in Roblox Build.
Examples
- Original starter brief: Create a small courier course. The player moves from a clearly marked start to a highlighted delivery dock while avoiding drifting debris. Reaching the dock ends the attempt with visible delivery confirmation. Contact with debris ends the attempt with a clear retry action. Retrying returns the courier to the start and clears the previous attempt's outcome. Make the route and obstacles easy to distinguish. Leave out shops, accounts, upgrades and additional levels from this first version.
- Why this is bounded: the delivery dock defines success, debris defines failure, and retry defines the reset. A shop is not necessary to test any of those behaviors. If the initial result adds an unrelated progression system, ask to remove that addition while preserving movement, the dock and the retry behavior.
- A useful follow-up after an observed failure: Restart currently leaves the delivery confirmation on screen. Change only the attempt-reset behavior so that confirmation clears before the courier returns to the start. Preserve the current route, obstacle movement and movement controls. Then repeat both a failed attempt and a completed delivery.
Common questions
- Should I put every feature in the first prompt?
- Include what is needed to understand and test the initial interaction. Put optional systems in a cut list so you can decide on them after the basic loop behaves coherently. A shorter brief is not automatically better if it omits the goal or retry behavior.
- What should I send when the first result is wrong?
- Describe the observed mismatch, name the requested change and identify working behavior that should remain. Retest the same scenario afterward. A preservation instruction is a request to the generator, not a backup or a guarantee against regression.