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-0066 · CORE GUIDE

Editorial review 2026-09-26

Roblox Build Credits Explained

Keep purchased Build credits separate from the daily free allowance and from your Robux balance. Read the actual offer and resulting account display; do not infer a universal conversion rate or spending order from the word credits.

Objective

Interpret free usage, purchased credits and Robux as separate account observations.

Before you start

Identify the exact labels shown in the current interface.
Treat purchases as optional decisions requiring their displayed terms.
Keep sensitive account and payment details out of public notes.

Steps

Record free and purchased usage displays separately where shown.
Inspect the current offer before deciding whether to purchase.
Do not invent a conversion or consumption-order rule.
After an authorized purchase, verify the observed balance state.
Separate a balance issue from a generation-result issue.
Escalate an unresolved discrepancy with the actual record rather than repeated paid tests.

Verification

No display is relabeled without evidence of what it represents.
Current offer terms are distinguished from historical examples.
A generated result is not treated as the only proof of credit delivery.
Unclear consumption order remains unknown rather than guessed.
The workflow does not encourage duplicate purchases to diagnose an issue.

Limitations

This page cannot inspect transactions or account balances.
It does not establish a universal bundle price or spending order.
It does not promise a refund or decide a billing dispute.

Working notes

Use distinct labels in your notes. Free allowance describes the replenishing usage available for the day. Purchased credits describe additional usage obtained through the offered purchase flow. Robux is the balance used for that purchase, not another name for the remaining generation allowance. Combining those displays can make a normal state change look like a missing balance.

Before any optional purchase, inspect what the interface says you will receive and spend. Record the displayed terms if you need a personal record, but do not assume an old screenshot still describes the current offer. This guide does not supply a credits-per-Robux formula or certify a particular bundle.

After a completed purchase, inspect the relevant usage or credit display rather than assuming a response message proves delivery. If the interface does not distinguish balances clearly, retain the visible wording and transaction context for a support question. Do not make another purchase simply to test whether the first one worked.

A purchased allowance and a successful game result are different questions. If a charge occurred but the expected creation is absent, record the project and transaction observations separately. Preserve the existing project state and use the official support route rather than asserting a refund or retrying charges without understanding them.

Examples

Balance record: free usage display—record its label and state; purchased credit display—record if shown; Robux transaction—record only if actually completed. An unlabeled bar should not be assigned to a balance category based on appearance alone.
Offer comparison: an earlier screenshot shows a bundle, while your interface shows a different offer. Use the current account presentation for the decision and retain its date; do not convert either screenshot into a promised universal price.
Discrepancy note: purchase appeared complete, credit state is unclear, project generation result is still unverified. Keep those as separate unknowns rather than concluding that the entire purchase disappeared or that a new payment is required.