Sources and corrections
Urban Reload Wiki Editorial Policy
We publish the strongest answer the evidence supports and make its limits visible. A plausible game detail is not enough to call it confirmed.
Source labels
| Label | What it means |
|---|---|
| Official-source information | A claim is supported by a developer-controlled page, announcement or relevant Roblox data. It is not automatically a personal gameplay test. |
| Tested observation | A game-specific check records the method, date, platform, conditions and evidence. Its scope is limited to what was observed. |
| Unverified | We do not have enough evidence to publish the claim as a fact. This does not establish that a feature does not exist. |
| Editorial assessment | An interpretation or recommendation based on stated evidence and criteria, separated from developer claims. |
Other guides, community messages and videos can identify questions worth investigating. They are not substitutes for checking the original claim or preserving a reproducible test.
What a gameplay test needs
Before publishing an observation as tested, keep the correct game identity, a real test date, platform, relevant version if known, steps, conditions and a screenshot or other record. If the version is unknown, say so rather than inventing a patch number.
Comparisons need compatible conditions. Weapon rankings must disclose their criteria; earnings estimates need elapsed time, costs and losses; attachment calculations need verified compatibility and formulas. A few observations do not establish an exact drop probability or an entire market’s price.
AI-assisted text cannot stand in for that record. Untested numerical or procedural claims are held back instead of being published as facts.
Dates mean different things
- Source reviewed: an editor actually checked the cited material.
- Tested: the described in-game test took place.
- Sampled: a data collector received and validated a snapshot.
- Updated: the article or its data changed in a meaningful way.
We do not change an article’s date merely because a build ran or a reader opened it. Source review is not labeled as gameplay testing.
Player-count data
The player-count feature uses public Roblox experience data. Concurrent players, cumulative visits and favorites are different measures. A snapshot is not daily active users, unique people or a full history of the game.
Any peak calculated from this site’s samples is labeled as an observed peak with a tracking period. Failed requests do not become zero-player observations, and missing time periods are not filled with invented values.
AI assistance and publication checks
AI may help draft copy, structure pages, summarize a cited source or implement a feature. It cannot authorize a factual claim. Before a draft is published, its source references, uncertainty labels, user-facing promises and required evidence are checked against the page’s purpose.
We do not publish a fake staff biography, pretend an AI has personally played the game or manufacture an “official” community link.
Corrections and changed information
Report an issue through the contact page, ideally with the exact passage and a public source or redacted test evidence. We check the submission against the published claim. A material correction should explain what changed; an unsupported claim may be removed while it is rechecked.
A broken link, a new game version and an incorrect conclusion require different fixes. We do not automatically accept a submitted code, invite or measurement simply because it was sent to us.
Independence
This independent site is not endorsed by Roblox or Squad Labs. The current version carries no paid placements or affiliate links. If the funding or editorial relationship changes, the relevant disclosure and policies should change with it.
Policy effective . About the publication.