BC-0205 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Prompt Is Too Vague
A vague prompt leaves important design decisions unset, rather than merely using too few words. Identify the missing player action, qualifying result or failure rule and decide it explicitly. You do not need to specify every decoration to make the next playable test meaningful.
Symptom
The requested concept leaves no clear test for whether the intended interaction was produced.
Immediate action
Identify the missing design decision instead of adding unrelated descriptive length.
Diagnostic branches
- The player action is named but its goal is absent.
- Choose the observable outcome that makes the action meaningful.
- Completion depends on a rule that was never written.
- State that qualification and a contrasting nonqualifying state.
- The disputed detail is only an optional aesthetic preference.
- Label it as a preference rather than redefining gameplay success.
- A complete rule exists but is phrased ambiguously.
- Use target-and-condition clarification instead of inventing new design requirements.
Least-destructive change
Fill the missing acceptance decision while preserving deliberate creative freedom.
Retest
- The brief names a visible successful outcome and relevant boundary.
- The example does not silently require unwritten rules.
- Optional details remain distinct from the immediate playable requirement.
Escalation
If the design decision is still undecided, keep it open rather than claiming a prompt repair. Use the prompt-specificity guide to review the complete brief; this checklist does not establish a universal minimum prompt length.
Working notes
Separate a missing decision from an ambiguous sentence. An instruction to make a fun explorer game does not say what exploration accomplishes; there may be no intended goal for the generator to misunderstand. Choose the required action and result before treating an unexpected result as disobedience.
Use a completion question to expose the omission: what can a tester do that demonstrates the requested loop works? If every possible outcome would be accepted, the brief lacks an acceptance boundary. If none would be accepted without an unwritten preference, make that preference explicit and decide whether it is a rule or style choice.
Set only the decisions needed for the immediate prototype. A marked destination and clear arrival feedback can establish a navigation task without specifying a full economy or world history. Where failure or retry is relevant, say what interrupts the attempt and what starting state returns; do not add those systems to a design that intentionally has no such attempt structure.
Leave genuine creative freedom visible. Background decoration can remain flexible when it does not communicate hazards or objectives. The aim is to stop accidental design decisions from determining success, not to disguise a complete implementation specification as a short prompt.
Examples
- Unset decision: explore a garden. Bounded choice: find a marked water source, carry water to the dry planter and show the planted result. The useful addition is the action-to-outcome relationship, not a larger list of garden decorations.
- Acceptance question: can the tester distinguish arrival without the required item from a completed delivery? If the brief never chose whether delivery is required, decide that rule before asking for a fix.