BC-0193 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Rewards Are Broken
A broken reward should be traced through qualification, grant acknowledgement, ownership and actual use. Decide whether it is a repeatable round result or an entitlement with a defined lifetime. Use non-paid prototype observations; never purchase or claim repeatedly just to investigate a suspected delivery problem.
Symptom
A qualified reward is absent, unusable, duplicated or retained for the wrong lifetime.
Immediate action
Define the actual reward promise and trace qualification through delivery to use.
Diagnostic branches
- Qualification is not established.
- Verify the objective before assuming a grant failed.
- Reward feedback appears but the promised benefit cannot be found.
- Record the feedback-to-delivery gap without another paid claim.
- Ownership is visible but the benefit cannot be used.
- Repair the benefit's action separately from qualification.
- Opening a panel repeats a grant or lifetime differs from the declared rule.
- Stop repeat activation and request the proper eligibility/lifetime guard.
Least-destructive change
Use the existing non-paid qualification record and avoid duplicate claims or live transaction experiments.
Retest
- The promised non-paid reward is both visible and usable after qualification.
- Ordinary panel navigation does not become another grant event.
- Its observed lifetime matches the authored attempt or session boundary.
Escalation
Use the appropriate official assistance for a real paid delivery issue, with existing receipts/status. This editorial sequence does not verify an account entitlement, promise reimbursement or certify persistent reward storage.
Working notes
Write the reward promise in observable terms. A congratulatory message, an unlocked action and an inventory item are different outcomes. If the design only promises a result message, the absence of a permanent item is not necessarily a failed grant.
Record the qualifying event and the first evidence of delivery. An ownership label is not the same as using the benefit, and a visible reward animation does not establish that anything was added to inventory. If a real transaction is involved, preserve existing official status and stop repeat diagnostic spending.
Specify repeat eligibility before testing ordinary re-entry. A terminal-round reward may grant per completed attempt; a session unlock may be owned already. Reopening a result panel should not create a new qualifying event by accident. Do not exploit or repeatedly activate a suspected duplicate grant to demonstrate it.
Inspect the defined lifetime through an already safe boundary. A benefit meant for the active attempt can disappear on retry correctly; a session benefit needs a different expectation. Keep cross-session ownership unverified unless it has its own documented implementation and observation.
Examples
- Delivery chain: objective acknowledged → reward message shown → intended item visible → its declared action usable. A failure between the message and item is reported separately from an item that exists but has no working action.
- Proposed non-paid reward repair: After the existing qualifying objective, grant the intended session unlock and show that it is owned. Reopening the result panel must not grant it again. Preserve the objective rule and the benefit's stated session lifetime.
- Lifetime distinction: a temporary round bonus ends when the attempt ends, while a session unlock remains usable for the next attempt. Neither observation alone verifies ownership after leaving the game.