How we make sure the things on this site are actually true.

BloxMeta exists so Roblox players don't have to click through ten outdated pages to find one working code or a tier list that reflects the current patch. Every page on this site is written or maintained by one of three editors who actually plays the game it's about. We don't publish content we wouldn't consult ourselves.

1. Automated tracking. Codes are pulled daily from community aggregator sources (currently TryHardGuides) by an automated fetcher, not typed in by hand. Every code on the site shows a “Community-sourced” badge unless it has also been individually verified — see below.
2. Human verification, when marked. A code only shows a “Verified” badge once an editor has personally redeemed it on a clean test account and confirmed it awards the listed reward. Not every code goes through this step, and we don't claim otherwise — the badge is how you tell the difference.
3. Document. Each code lists its reward, its source, and the date we last checked it. If a code is server-wide, one-time use, or region-locked, we say so.
4. Re-check. Codes are re-fetched on a rolling schedule — daily for the most-played games and at least weekly for everything else. If a fetch looks broken (far fewer codes than expected), we skip that round rather than mass-marking working codes as expired. Codes that genuinely stop working move to the expired section; we do not silently delete them.

Tier lists are the most opinionated thing on the site, so we're explicit about how we form them.

• Each tier list identifies its method. A playtest list uses a documented test setup; a research list reviews current unit kits and official patch information, then cross-checks multiple current rankings and sources.
• Rank changes require relevant evidence, such as a kit or patch change, documented test results, or a well-supported shift across current sources. Conflicts are noted and handled conservatively.
• We label our confidence: tiers we're sure about (e.g., S+ Tiger fruit), tiers that are situational, and tiers that depend on specific build orders.
• We write a short rationale for the most-debated entries so you can argue back if you disagree.
• Old rankings are kept in version history so you can see how a unit's rank has moved across patches.

• Every guide is written by one of the three editors. The byline is real — there are no ghostwriters.
• The author has played the game extensively. We don't write guides for games we haven't spent serious time in.
• Guides are reviewed by at least one other editor before publishing — usually for accuracy, sometimes for tone.
• When a guide's recommendations would change because of a patch, we update the existing guide rather than publishing a new one. The original URL stays.
• We don't accept guest posts or paid placements inside guides. Recommendations exist because we believe them.

Each guide is signed by one of three named editors — Sam, Leo, or Mack. Each editor has a public bio explaining their experience with the game in question. Read each one on the About page or visit any author's profile via the byline link on a guide.

We get things wrong. When we do, here's what happens:

• The page is updated with the correct information and the “Last verified” date is bumped.
• If the error materially misled readers (a code that didn't work, a tier rank that was significantly off, a wrong build recommendation), we add a brief note in the page intro acknowledging the change.
• Corrections are usually shipped within 24 hours of being reported.
• You can flag any error by emailing [email protected] or by using our contact page.

BloxMeta is funded by display advertising. Ad placements are managed by a third-party ad network. Ad revenue has zero influence on our editorial decisions:

• We do not take payments from game developers or publishers.
• We do not accept “sponsored” codes, tier placements, or guide recommendations.
• We do not sell links or guest posts.
• If we ever publish anything sponsored — a giveaway, an affiliate link, a partnership post — it will be clearly labeled as such on the page where it appears.

No guide, code description, tier list rationale, or article on this site is generated by AI. We use AI tools internally for things like proofreading and draft cleanup, but the actual research, gameplay, and writing are done by the three named editors. We block AI scraping bots from crawling the site as well.

• Community aggregator sites (currently TryHardGuides) for the automated daily code fetch — these are our primary source for code tracking, and we say so on every codes page.
• Official developer channels: in-game announcements, official Twitter/X, official Discord servers, official YouTube channels, used to cross-check major code drops.
• Patch notes and changelogs released by the games' developers.
• Our own playtests and runs across our test accounts, and manual redemptions on codes we mark “Verified.”