Every number on this site traces back to a source we can name and a timestamp we can show you. This page explains exactly how — not as a trust badge to slap on the footer, but as a methodology you can actually check against what other Dungeon Quest Reborn sites publish.
How Our Live Stats Work
The population count, total visits, favorites, and like-ratio numbers you see across this site don't come from a spreadsheet we update manually. They come from Roblox's own public games API, called directly against Dungeon Quest Reborn's universe ID (9931749389):
games.roblox.com/v1/games?universeIds=9931749389returns the current player count, lifetime visit total, favorite count, the game's listing name (useful for catching event name-changes, like the "[1.5x Luck]" prefix that appeared in the listing in August 2026), and theupdatedtimestamp Roblox itself records for the experience.games.roblox.com/v1/games/votes?universeIds=9931749389returns raw upvote/downvote counts, which we divide ourselves to get the like ratio rather than trusting a pre-rounded percentage from somewhere else.
We capture the response and record the exact time we pulled it, in Beijing time, next to the number itself. When you see a stat on this site, the honest way to read it is "this was true at this specific timestamp" — not "this is permanently true," because a live player count changes by the minute. We re-pull these endpoints periodically rather than caching a number once and leaving it stale for months, and where a figure has visibly moved between two of our own checks, we say so explicitly instead of quietly overwriting the old number.
For anything the official API can't answer — dungeon-specific enemy HP, boss attack patterns, weapon stats — we go to the game's own community-maintained records, the most detailed non-official source that exists specifically for this game. We treat that as a second-tier source: useful and current, but not the same confidence level as Roblox's own numbers, and we say so on every page that uses it.
A Real Example: Why "Live" Stats Are Often Not Live
We looked closely at how another Dungeon Quest Reborn wiki displays its own "live" numbers, because it's a useful test case for a problem that's common across fan sites in this niche. At the same point in time we pulled Roblox's official API and got a total visit count of 9,357,530, that other site's homepage displayed "6.6M Total Visits" — an undercount of roughly 30%. Its displayed like ratio (98.1%) was also off from the API's actual figure (97.23%) at that moment. Both numbers on that page were dated the same day across nearly every article on the site, which is a strong signal that the "live" stats were captured once, baked into a static page, and never refreshed again — despite being presented as current.
That's not a one-off bug; it's what happens by default when a site pulls a number once during content production and never re-checks it against the source. We built our stats pipeline specifically to avoid that failure mode: every stat page on this site carries its own capture timestamp, and we treat "when did we last check" as information worth showing you, not something to hide because it might reveal the data isn't from five minutes ago.
How We Monitor Codes
Most Roblox developers who run active promo codes post them directly inside their game's own description field on Roblox — so that's exactly where we check, pulled through the same official API described above rather than a screenshot, a Discord scrape, or a copy from another site's codes page. We read the full description text character by character looking for code-like strings, and we also check the official Roblox game page's raw HTML for a Discord or X/Twitter link that might announce codes through a separate channel.
Because we're reading the same field developers publish to, we're not waiting for a human somewhere to notice a code first and write about it — the moment a code string appears in that description, our next check catches it. Until then, we log "no active codes" with the exact time we last confirmed that, and we update the Codes page's verification history every time we re-check, whether or not anything changed. A monitoring process that only produces output when something changes isn't verifiable from the outside; ours logs the negative result too.
Our Three-State Data Rule
Every fact on this site gets one of three labels, whether or not we spell the label out on the page itself: confirmed (directly verified against Roblox's official API or a source we trust enough to publish without a caveat), partially confirmed (a real source says this, but it's a single source, an estimate, or carries some caveat worth knowing), or unconfirmed (we looked, and we genuinely don't know).
We'd rather ship a page with visible gaps than fill those gaps with something that sounds plausible. That's a deliberate trade-off: a shorter, honest page converts trust into a long-term asset, while a padded page that gets one detail wrong once is enough for a player to stop trusting everything else on the site. Where you see phrases like "roughly," "community estimate," or "we couldn't confirm this," that's not hedging for its own sake — it's the actual confidence level of the underlying evidence, stated plainly instead of rounded up into something more certain-sounding.
Telling Dungeon Quest Reborn Apart From the Original Dungeon Quest
This is the single easiest mistake to make writing about this game, and we've watched other sites make it: Dungeon Quest Reborn (created March 24, 2026, developed by the Roblox group Delta Quarters OG) shares a theme and a name with the original Dungeon Quest (live since 2018, now run by Voldex Games) — but they are two separate Roblox experiences with no official affiliation we could find between them. The original game has years of accumulated content: multiple difficulty tiers, a wide rarity ladder, and dozens of named dungeons and zones built up over its much longer run.
Our method for keeping the two straight is simple but strict: we only publish a piece of game content as true of Dungeon Quest Reborn if we can trace it to a source that is specifically about Dungeon Quest Reborn — the official Roblox listing for this universe ID, or the community records maintained specifically for this game. If a claim only shows up in sources about the older game, or in a summary that doesn't make clear which game it's describing, we leave it out rather than assume the two games share a system just because they share a name. We apply the same rule to enemy and location names we encounter while researching this game's own dungeons: where a source describes an enemy's attack as "similar to" something in a place we can't independently confirm belongs to Dungeon Quest Reborn, we drop the comparison and describe only the confirmed enemy's own behavior. This is also why our Dungeons, Bosses, and Classes pages are shorter than some competitors' — we're not going to backfill dungeons #1–11 with content borrowed from the original game just to look more complete.