How we check information

RRB Wiki publishes explanations, references and suggested practice plans. Our standard is to make the basis of a claim visible so a player can distinguish a documented requirement from a proposed way to practice.

Four evidence labels

• Official record: a game description, badge condition or store listing published through the game’s Roblox pages or APIs. It establishes what that record says, not every detail of implementation.
• Video observation: a readable feature at a cited timestamp in named footage. A brief countdown does not establish a full cooldown or damage formula.
• Source report: a named publication’s claim, such as an active code. We preserve discrepancies and distinguish that claim from our own testing.
• Editorial suggestion: a practice method, route or comparison framework developed for the guide. It is not presented as an official prerequisite or measured result.

What qualifies as our own test

“Tested by RRB Wiki” requires an actual recorded session with the date and timezone, game identity, device, steps and observed outcome. We would preserve relevant screenshots or recordings with private details removed. Code tests must record the exact response and observed reward; an “already redeemed” message does not prove a new redemption succeeded.

No independent in-game test has been completed for the current source-reviewed guides. Public footage, another publication’s success claim and a working copy button are not substitutes. We will not invent results to change this label.

Adding value to source material

We organize badge conditions into decision routes, distinguish cumulative progress from streaks, explain counterexamples and provide local planning tools. Articles should answer a player’s next decision rather than repeat a source in different words. We link sources and write our own explanation; we do not reproduce whole third-party articles.

Automated tools assist research organization, drafting and implementation. They can produce errors, so linked evidence and explicit uncertainty matter. We do not treat generated artwork as gameplay evidence or generated text as a record of a session.

Corrections and conflicting information

When assessing a possible correction, we check whether the source refers to the same experience, whether its date is relevant and whether the observation supports the conclusion. An unresolved conflict stays labeled rather than being silently turned into a precise fact.

For example, the source for RELEASE lists different Gears amounts in its introduction and code table. Our code list identifies the conflict. We have not verified which amount the game awards. The update log records meaningful corrections without manufacturing earlier test dates.

Media, authorship and commercial interests

Wiki pages identify the independent publisher. Game-developer names identify the game, not article authors. Promotional art, original illustration, redrawn diagrams and creator footage are labeled according to their origin. Attribution identifies the source; it does not imply permission or endorsement.

The current site has no advertising or affiliate tracking integration. Future paid placements must be identifiable and must not determine whether an uncertain gameplay claim is labeled verified. We will keep editorial corrections accessible regardless of monetization.