BC-0204 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Misunderstood My Prompt
When an instruction has multiple reasonable meanings, make the target, comparison and condition explicit before retrying. Replace ambiguous pronouns and relative words with the intended relationship. Do not diagnose a hidden reasoning process; compare interpretations that the actual wording permits.
Symptom
The output follows a plausible interpretation other than the one intended by the creator.
Immediate action
Name the ambiguous target, relative comparison or condition in the original wording.
Diagnostic branches
- A pronoun could refer to several visible elements.
- Replace it with the intended role and a unique observable landmark.
- A relative change could alter different behaviors.
- Specify which relationship changes and which timing or movement stays the same.
- The desired improvement is visual but the wording implies geometry changes.
- State the recognition goal and preserve the playable route.
- The wording has a clear interpretation but the result contradicts it.
- Use a demonstrated behavior repair instead of inventing further ambiguity.
Least-destructive change
Resolve the ambiguous relationship without rewriting the entire game concept.
Retest
- A reader can identify the intended target and condition without relying on the author's memory.
- The observed result is compared with the clarified relationship.
- Preserved behaviors are checked separately from the requested change.
Escalation
Keep the interpretation comparison if the correction fails. This is an editorial language diagnosis, not proof of how the generation system processed the prompt.
Working notes
Underline references such as it, that gate, faster or after completion. Ask what each refers to in the current scene and which event defines the condition. If several gates or completion events exist, the instruction may not identify the intended one even when the intended change feels obvious to its author.
Write plausible interpretations side by side using only the existing design. Make the enemy slower could mean slower travel, slower attacks or a longer wait before activation. These are different behaviors; adding more decorative detail does not tell the request which relationship you meant.
Clarify relative comparisons by naming the baseline. A larger object might mean visually easier to spot without changing the route, or a physically wider obstacle that narrows the path. State the desired player-visible consequence and what must not change. Do not invent an internal scale property when the actual need is readable identification.
Preserve the original and clarified text in a local note so the correction is traceable. Then inspect the specific interpretation boundary if you choose to send it. A clarified request can still produce an incorrect result; better wording resolves the brief's ambiguity, not the platform's reliability.
Examples
- Ambiguous: Slow it down after the gate. Clarified: After the player passes the marked entrance gate, reduce the pursuing enemy's travel speed; keep the countdown and player's movement unchanged. This assumes those existing elements are actually present.
- Visual-versus-physical distinction: Make the collectible easier to identify from the route while preserving the passable corridor and its collection rule. Do not request a bigger collision obstacle when the only problem is recognizing the item.