99 NIGHTSFOREST ESCAPE

Start / How we verify

TRUST · METHOD

How this guide is verified

Two labels apply to a page, and a third marking appears inside some pages. This page explains what each one means, what evidence promotes a claim, how second-hand reports are handled, and what stays unpublished until evidence exists.

The three markings

A needs-verification page is not an unfinished page. It is a page whose remaining gap is one specific fact we could not observe, and the page names that fact. A community report does not close that gap; it tells you who else has claimed something about it, and what they claimed.

What counts as evidence

  1. Same session, same chain. The HUD, the prompt, and the result are captured in one browser session. A number seen in one session is never attached to a mechanic observed in another.
  2. Displayed, not inferred. If the client did not display a value, the page does not state a value — no estimated night length, no guessed damage, no derived burn time.
  3. No cross-version borrowing. The Roblox game with a similar name is a different product. Nothing from it is used to fill a gap here.
  4. Dated captures. Every first-hand claim carries the date of the session it came from, so a later patch can invalidate it visibly rather than silently.

How community reports are handled

  1. Named, public, dated. A community claim is only published with a link and a date. If the source shows no date, the page says “no date shown” rather than implying freshness.
  2. Never merged upward. A second-hand claim is not rewritten as if it were ours. It sits inside the labelled block, keeps a source line on the item, and contributes nothing to the page’s label.
  3. Conflicts are printed, not resolved. When two sources disagree, both claims appear with a note saying we have observed neither — a guide that silently picks the tidier number is the exact failure this site exists to avoid.
  4. Translation, not copying. Chinese-language sources are paraphrased. Facts themselves are not copyrightable, so paraphrasing does not put this site under the source’s licence; reproducing their sentences would, so we do not.
  5. Weak sources are labelled weak. A page with no revision history and machine-sounding text is treated as a lead, cited as a lead, and never used to support a number.

What this guide will not publish

Each of those topics has a page that states what is confirmed, shows what other sources claim, and stops there. Where a number is missing, the page gives you the recording routine to fill it in on your own run.

Why some facts are still open

Both browser entry points — the CrazyGames iframe and the direct Bloxd.io game page — stopped at a Cloudflare human check during the recorded session, and the game server refuses VPN connections. The opening session was short: it covered the HUD, movement, wood, basic tools, a first shelter, and one PvP contact. Night, fire fuel, boars, spirits, lost children, and revival were not observed, so they are not described as if they were.

The obvious next question was whether the public record can fill that gap. It partly can: a Chinese Bloxd wiki, one Bloxd-specific aggregator, and a low-trust SEO page all describe mechanics the listing omits, and they disagree with each other on campfire levels, child count, and whether death is final. That material is published as community reports with its contradictions intact, because the disagreement is itself the most useful thing a reader can know before a run.

Method published 30 Oct 2026, community-report rules added the same day. Applies to every page on this site, including the 18 marked needs verification.

Corrections

If a claim here is wrong, or you have a capture that settles an open fact, send it through Contact. Corrections are applied with the date they were made and recorded in the sources and test log.