BC-0003 · CORE GUIDE
Editorial review 2026-09-26
Roblox Build Supported Regions
The named initial-test markets in current Support are New Zealand, Serbia and Singapore. Treat that list as a documented region statement, not a worldwide calendar or proof that an individual account has every Build feature.
Objective
Record named-market evidence separately from individual account access.
Before you start
- Identify the location whose documented status you are checking.
- Use the current official region statement rather than a third-party prediction.
- Keep account observations distinct from country-level wording.
Steps
- Read the literal location list in the official source.
- Record whether the intended territory is named.
- Keep the named-location wording beside its source URL and the date you actually read that passage.
- Inspect the creation entry on the intended account without changing account location.
- Route a missing-entry question to the appropriate account/device checks.
- Leave unannounced territory dates unknown until official evidence changes.
Verification
- Every named supported market traces to the actual official list.
- No neighboring territory or regional bloc has been inferred.
- The account observation has its own result rather than inheriting the source result.
- Unknown dates remain unknown rather than becoming a forecast.
Limitations
- This guide does not inspect account location or eligibility.
- A documented market does not guarantee a feature on every account.
- Travel and account-location edge cases are not resolved by a simple named-market list.
Working notes
Read the market list literally. A named territory is not a statement about its neighbors, everyone who speaks the same language or every account currently traveling there. When a location is absent, record that absence instead of converting a general expansion plan into a launch date.
Keep source publication, source check and account observation separate. A dated announcement explains what was said at that time; a current support paragraph provides the present documented list; the interface shows what you can actually reach on the intended account. These observations answer related but different questions.
Use the list to choose the next investigation, not to diagnose the whole problem. A named market with a missing entry needs account and device checks. An unlisted market needs a current official announcement or support statement before you can claim documented access. Neither condition justifies changing account location to force an outcome.
Keep your evidence record small enough to update. Save the official URL, the exact named location and the date you read it, then add the observed account state. Do not collect identity documents or passwords for a region worksheet; this independent site cannot verify an account's location or unlock access.
Examples
- Market evidence row: intended location—record; official source—link; location explicitly named—yes, no or not checked; source observed on—record; actual creation entry—present, absent or not inspected. A yes in the source column does not automatically fill the account column.
- Source-update example: an older screenshot omits a territory that the current Support paragraph now explicitly names. Record the updated listing and its reading date, while keeping the account's entry state unconfirmed until inspected. A stale screenshot should not overrule newer official wording.
- Next-action branch: if your location is named but the entry is absent, move to the account/device investigation with the evidence row. If it is unlisted, follow official expansion information without inventing a countdown from another market's announcement.