Sources
Source Methodology
Official Roblox pages, public Roblox API snapshots and visible in-game proof are stronger than copied guides or social posts. Videos are leads unless they show current UI proof.
Game name, creator, public description, current thumbnail and public experience context.
Strong sourceUniverse 10247712813, root place 110373292461174, visits, favorites, server size and update timestamps.
Strong sourceGamepass names and checked Robux price rows for Collect All, VIP, 2x Throw Power and 2x Money.
Strong sourceCommunity demand, visible UI leads, route questions and player confusion points.
Lead sourceCodes
A code needs official text or a current in-game redeem screen. A YouTube title, comment or copied blog row is only a lead.
Prices, income and formulas
Exact shop prices, brainrot income, rarity and upgrade formulas need visible current UI proof. Without that, the wiki publishes decision rules instead of made-up calculators.
Video handling
Gameplay videos help find UI labels, search demand and player questions. Exploit/script videos are not embedded as recommendations, and no video alone turns a claim into a stable wiki fact unless the claim is visibly shown.
Watch for current UI, shop names, floor pacing and first-session route.
Use as a gameplay reference for route questions and visible UI checks.
Use as a high-reach community lead for common player questions.
Editorial standard for a stronger wiki
A site can look large and still be weak if its pages are built from copied rows. The stronger approach is slower: publish what players can use now, mark what is still being checked, and expand when proof arrives. This keeps the guide useful while still allowing it to grow into a full wiki.
The methodology also protects keyword density. The full game name appears in titles, descriptions and core page openings. Inside long sections, the writing uses normal player language. That is how the site can target the main query without reading like a keyword-stuffed page.
Content expansion rules
New pages should not enter the sitemap just because a keyword exists. A page should have a quick answer, player steps, common mistakes, a table or checklist, at least one internal link to a related page, and a clear explanation of what is known versus what is still being checked. That is the standard that keeps future expansion from becoming thin.
The current best expansion candidates are all brainrots, best brainrots, code not working, weights guide, floors guide, admin event, update log, and beginner mistakes. Each should be built only when it can answer a real player question better than the current page.