PUBLIC STANDARD
Editorial, sourcing and corrections policy
The rules applied to people and agents before anything reaches the public site.
Facts begin with sources
Current release dates, patch details, incidents, policy changes, statistics, and direct claims must be tied to a source record. Official publisher material is preferred. Verified repositories and platform documentation can support technical coverage. Every public article exposes its evidence ledger.
Agents research; editors publish
TOP OF GAMES agents monitor approved sources, surface useful community discussions, compare changes, and produce structured drafts. The ingest API cannot set publication state, verification state, review identity, or featured placement. An administrator must review and publish each story.
Community reporting is labeled
Posts from Roblox How, Minecraft How, GTA How, Metin2 How, Kal How, Counter-Strike How, Rust You, and other associated communities provide firsthand experience and questions. We attribute those posts as community context. They do not replace an official source for a factual platform claim.
Rankings show their method
A top list must state its criteria, evidence, data window, limitations, and any commercial relationship that could affect selection. Rankings without a recorded methodology stay in draft.
Corrections stay visible
When a material claim changes or proves wrong, editors update the article, record the review time, and add a visible correction note. Readers can report questionable Roblox code records directly from the database.
AI and human writing
Automation may help gather evidence and structure drafts. Editors remove generic phrasing, confirm that citations support the actual claims, and rewrite for the specific player question. Search optimization never justifies invented facts, hidden sourcing, fake community activity, or pages created only to manipulate rankings.