Plan and test game mechanics

A mechanic needs an observable rule: an action, a change in state and feedback to the player. Before adding more systems, test whether the first action, win condition and restart work together. The existing guides below provide the starting workflow and debugging checks.

Open Mechanics collection ↗

Prepare a game for publishing

Publishing starts with a game that can be tested, understood and maintained. Check the available creator controls, audience settings and safety requirements before a release. Use the publishing guide for the sequence, and the troubleshooting guide for an actual blocked step.

Open Publish collection ↗

BC-0208 · TROUBLESHOOTING

Editorial review 2026-09-26

Roblox Build Prompt Has Conflicting Instructions

Conflicting instructions require incompatible outcomes in the same situation. Compare the target, condition and time boundary of each rule before deleting either one. Some apparent conflicts are valid rules for different phases; an actual contradiction needs a chosen precedence or a changed condition.

Symptom

The brief asks for incompatible results or appears to do so because its conditions are implicit.

Immediate action

Write each disputed rule as a target, condition and required outcome.

Diagnostic branches

The instructions concern different state lifetimes or targets.: Name that distinction instead of removing a valid rule.
The outcomes apply in mutually exclusive phases.: State the phase boundaries clearly and preserve both behaviors.
Incompatible outcomes apply to the same target under the same condition.: Choose precedence or revise a condition explicitly.
The corrected condition also changes an earlier valid state.: Restore the unaffected boundary before adding further rules.

Least-destructive change

Resolve the actual incompatible pair while preserving valid phase-specific behavior.

Retest

No single described state requires the same target to have incompatible outcomes.
The intended before-and-after boundary is explicit.
The nearby unaffected state remains part of the check.

Escalation

Keep unresolved design choices visible rather than asking the generator to infer a secret priority. This analysis cannot prove all possible conditions are conflict-free.

Working notes

Convert each disputed sentence into condition, target and required result. Clear the key on retry and preserve the key on retry conflict if they describe the same key and retry. Clear the carried key but preserve access already unlocked may be compatible because the states are different. Do not resolve every apparent contradiction by dropping preservation rules.

Test whether the conditions can occur together. An exit locked before the goal and open after it is an ordinary state transition. An exit required to remain locked and open after the same goal is not. Writing both conditions explicitly avoids treating necessary phase-specific behavior as redundant text.

If both rules really apply together, decide which intention governs or narrow one condition. An optional visual flourish should not override an essential safe route unless that is an intentional redesign. A precedence statement must name the conflicting outcomes; adding prioritize gameplay does not explain which action the game should take.

Inspect the boundary just outside the chosen condition as well as within it. Fixing the completed state can accidentally open the exit before qualification. This is a proposed contrast test, not a claim that a formal proof or every game state has been checked.

Examples

Compatible pair: hide the instruction once delivery is complete; show it while the delivery objective remains unfinished. Their conditions differ, so deleting either instruction may remove needed behavior.
True conflict: after failure, keep all attempt objects consumed and also restore every attempt object for the next run. Choose the intended fresh-attempt inventory instead of leaving both outcomes in the prompt.
Resolution row: disputed clauses / same target or different state / overlapping condition / chosen outcome / contrasting state to retain. This makes the correction inspectable without claiming a hidden instruction-priority algorithm.