Editorial Policy

Our Standard

BloxGuidesGG publishes guides, value lists, calculators, active codes, and wiki content for Roblox games. Our readers use this information to make real in-game decisions — trades, strategy choices, item purchases — so accuracy is not optional. A codes page shows the date its list was last checked against its source, and one older than 21 days goes on a re-check list; a synced database shows the date of its last pull; and a page with no check on record shows no date rather than an invented one.

Original Content with Editorial Oversight

BloxGuidesGG is operated by a single editor — Brandon Sorensen — who is publicly accountable for every page on the site. See the About page for who he is and which of these games he plays himself.

Blog posts are researched and written by an AI routine that Brandon set up. It is required to cite a primary source for every factual claim — the game's wiki, official patch notes, or a developer's Discord or social posts — and to leave out anything it cannot source. The same routine corrects codes against each game's wiki. It publishes on its own: Brandon reviews each post after it goes live, from the report the routine sends him, and corrects what is wrong. Guides and tier lists are drafted with AI from the same kinds of sources. For the five games Brandon plays himself, his own in-game testing is a source as well.

Articles are not scraped or spun from other sites. The databases are pulled from the wikis and APIs named on each table, which credit them. The site does not publish AI-generated images that misrepresent gameplay, fabricated screenshots, or invented quotes from developers or players.

If a guide on this site ever feels generic, templated, inaccurate, or contains a claim that can't be substantiated, flag it via the Contact page and it will be reviewed, then rewritten or removed.

How We Verify Codes

Active codes are the fastest-moving content on the site. Our process:

1. Source monitoring. We follow official game Discord servers and developer social accounts for new code announcements.
2. Primary-source check. Before a code is listed as active it is reconciled against a primary source: each game's own wiki, read through the Fandom MediaWiki API, plus the developer's own announcements. For the handful of games with no wiki, we cross-check several established code aggregators and publish only what they agree on. A codes page carries the date that check was last made — treat it as the age of the list — or no date at all if no check is on record.
3. Expiry tracking. A codes page older than 21 days goes on a re-check list. When the wiki marks a code expired, it moves to the expired list with that date — it is not silently removed.
4. Reader confirmation. Players can flag codes via the Contact page, and a flagged code is re-checked against its source.

Sourced and dated

11 of the databases on this site are pulled from an outside source — the fish roster, the fruit list, the pet values — and each one names the source it was pulled from and shows the date of its last successful pull, so you can open the source and check the number yourself. No refresh schedule holds for all of them: some are pulled by an automated job and some only when we run the pull ourselves, and a pull that fails leaves the previous copy in place with its older date. The date on the table is the age of the numbers.

How We Build Value Lists

Every value list says where its numbers come from:

• Trade values come from established community value lists, named on each page — Supreme Values and others for MM2, TrueVal and Proto for Fisch. Prices the game itself sets, such as Blox Fruit Dealer prices and Grow a Garden sell values, come from the game's wiki.
• MM2 values are maintained by hand against those lists, not by an automated pull — so treat the review date on the page as the age of the numbers.
• We do not inflate values to drive trade volume or deflate them to favor any trading party.
• On the Fisch list, where TrueVal and Proto disagree, the page shows both rather than picking one.

How We Build Calculators

BloxGuidesGG calculators (profit calculator, trade calculator, stock tracker, fishing calculator) are built on documented game mechanics:

• Formulas follow the developer's own patch notes and the mechanics documented by each game's community, rather than being reverse-engineered from a competitor's calculator. Where we have got one wrong we correct it site-wide and say so.
• The maths runs in your browser and nothing you enter is stored. Two calculators — the Grow a Garden crop calculator and the Sailor Piece damage calculator — send an anonymous usage event to Google Analytics naming the crop or build you picked.

How We Write Guides

Strategy guides, tier lists, and beginner walkthroughs are drafted with AI from primary sources:

• Tier placements follow each game's own wiki and the community consensus around it, not another guide site's list. For the games Brandon plays himself, first-hand experience informs the ordering too — for the rest, we rank on documented stats and community consensus and do not pretend otherwise.
• Where the community is split on a tier placement, we explain both positions rather than picking one arbitrarily.
• A tier list or guide shows the date a person last reviewed it. If no review is on record, it shows no date rather than an invented one.

Rumors, Leaks & Unconfirmed Information

Roblox communities run ahead of their developers. Update rumors, datamined files, and "expected nerf" chatter circulate long before anything is announced, and a lot of it never ships. We cover that conversation, but we do not launder it into fact:

• Anything unconfirmed is labelled unconfirmed, on the page, next to the claim — not in a disclaimer at the bottom. If it is a rumor, a leak, datamined content, or community speculation, the sentence says so in those words.
• We do not write an unannounced change as a known plan. A balance patch, item, or event is described as coming only when the developer has said so in a patch note, an official Discord or social post, or an in-game announcement — and we link that source. Where the community expects something the developer has not confirmed, we report the expectation and name it as the community's, not the studio's.
• Datamined content is treated as the weakest class of evidence. Files found in a game build show what was made, not what will ship, and cut content is common — so datamined items are flagged as datamined and never listed alongside released ones.
• Leaked or generated codes are never published. Codes come from official developer releases only. A code we cannot trace to the developer or the game's wiki does not go on the site.
• When a rumor is later confirmed or disproven, the page is updated to say which — the speculative wording is replaced with the sourced outcome rather than quietly deleted.

Corrections Policy

If you find an error — a wrong value, a dead code listed as active, a formula that doesn't match current game mechanics — please contact us. Each request is re-checked against its source and the affected page is corrected. We do not quietly delete or rewrite content to hide past errors.

Independence & Advertising

BloxGuidesGG is independently operated. It shows no ads at the moment: Google AdSense is switched off. We do not accept payment for positive coverage, sponsored tier placements, or inflated value listings, and advertisers have no influence on editorial decisions.

We are not affiliated with, endorsed by, or sponsored by Roblox Corporation or the developers of the games we cover, with one exception: Dive For Eggs is made by BloxGuidesGG's owner, and this site promotes it. Game names, trademarks, and assets are used here under fair use for commentary and educational purposes.