Where our data comes from

Our source hierarchy

We rank sources from hardest to softest. A number only appears on this site if we can point to which of these four tiers it came from.

1. 1.Steam’s official store APIappdetails

   Price, release date, platforms, languages, DLC — anything on the Blood Dungeon store page comes from Valve’s own appdetails endpoint, not a screenshot or a copy-paste from another wiki.

2. 2.Steam’s official achievement systemachievements

   Achievement names, descriptions, and global unlock rates. This is also our only source for bunkmate names — we don’t invent characters that aren’t named in an achievement.

3. 3.Steam reviews & concurrent playersappreviews / CCU

   Review counts and player counts, both read directly from Steam’s own endpoints, not estimated from a third-party tracker.

4. 4.Third-party videoopinion, not fact

   Any review or gameplay video we embed is labeled as a third-party opinion — never blended into our own factual claims about the game.

What we refuse to do

• We don’t invent boss names that aren’t in an achievement or the store page.
• We don’t invent numbers — no made-up damage values, drop rates, or stat blocks.
• We don’t name the 5 unconfirmed bunkmates just to fill out a roster.
• We don’t publish strategy advice for builds we haven’t actually tested.
• We don’t write “coming soon” to paper over a gap in what we know.

Our numbers move — on purpose

Review counts, achievement unlock rates, and player counts change every time Steam updates them, so every page that shows this kind of number prints a fetch timestamp next to it (currently Aug 26, 2026 UTC for this snapshot). A real example from a single day of tracking:

A mistake we made and fixed

We once read Steam’s appdetails.recommendations field as the review count for Blood Dungeon and reported it as zero reviews. That field doesn’t exist on this game’s listing — Steam simply omits it — so reading it back as zero turned “we don’t have this data” into “this data is zero,” which is a different claim and a wrong one.

The fix was switching to Steam’s appreviews.query_summary endpoint, which is the field actually meant to report review totals. It’s also why every number on this site is tagged with the exact source field it came from — a missing field and a zero look identical unless you write down which one you got.