Skip to content
EscClose·↵Search
Powered by Pagefind
English
English
GuidesWeaponsMapsMechanics
Language
English

How we verify Scavland data

Last updated: 2026-10-23

Scavland Wiki is an independent fan site. Early Access patches move quickly, so a number without a method becomes misinformation. This page explains how we decide what to publish, how we label uncertainty, and how you can reproduce or challenge our results.

We are not affiliated with NoShadow. Official facts always win over our guesses.

The three evidence layers

1. Confirmed from official notes as of DATE

Used when a statement appears in a primary source we can link:

  • NoShadow’s Scavland Steam store page;
  • Official Steam news / patch notes (we name the patch, e.g. Update 0.8.0 on October 17, 2026, or Hotfix 0.8.8 on October 19, 2026).

We rewrite in our own words and keep a citation. We do not paste entire patch notes as a page.

2. Wiki playtest log

Used when a value is visible in a running build or measured in a controlled check:

  • game version string from the client;
  • date/time of the session (Asia/Shanghai on our editorial clock when we record internally);
  • location or setup;
  • sample size (e.g. “n=5 reloads”);
  • raw observation vs interpretation.

Until a log exists, we write Wiki playtest log: TBD instead of inventing a number.

3. Editorial advice

Recommendations (“take AP into Gunner territory”) are our reading of the rules. They must sit next to the facts they depend on and must not be phrased as hidden official stats.

What we refuse to invent

  • Damage, RPM, recoil coefficients, or attachment percentages not shown in UI or notes
  • Reputation thresholds and Job reward matrices without observation
  • Radiation ticks, Mist timers, or cure item potency without observation
  • Loot tables, coordinates, and guarantee systems without logs
  • Tier lists without a stated comparison method

Empty tables with version columns are preferred. Fake precision is worse for players and for ad review than an honest TBD.

Patch-note synthesis standard (worked example)

Our Ammo types and armor penetration guide is the template:

  1. State the patch that changed the rule (0.8.0).
  2. Explain the rule in plain language (penetration subtracts from armor).
  3. Reproduce tables that appear in notes (enemy armor groups, price changes) with a source line.
  4. Separate “our loadout advice” from “what the notes say.”
  5. Note follow-up hotfixes (0.8.8 magazine ammo memory).
  6. Remind readers that later patches can invalidate the page — version badge at the top.

Category hubs should point to this quality bar instead of only listing titles.

Playtest protocol (checklist we use)

When filling a TBD table:

  1. Record version and mode (Explorer / Returner / Iron Man).
  2. Photograph or note the UI field names exactly.
  3. Change one variable at a time (ammo type, range band, enemy group).
  4. Write negative results (“no Mist meter found on HUD in this build”) — absences matter.
  5. Update “Last updated” and the version badge on the same edit.
  6. File corrections from readers through Contact with URL + version + source.

Corrections and reader reports

Email bgnwd15@gmail.com with:

  • page URL;
  • what is wrong;
  • game version;
  • patch-note link or clear description of the in-game UI.

We update when confirmed. Early Access means yesterday’s guide can be wrong; dated badges are part of accuracy, not a failure.

Ownership and originality

Articles are written by Scavland Wiki in our own words. We do not scrape other fan wikis into thin pages. When we only know a store bullet, we publish a status article that says what is unknown — that is still useful — rather than padding with generic survival clichés.

Advertising and incentives

Ads (Google AdSense) may appear on content pages. Ad placement does not decide which numbers we publish. Policy and trust pages may be excluded from ads. See the Privacy Policy for cookies and consent.

Version badges on every guide

When you open a guide, look for the game-version badge near the top. That badge means: “this page’s confirmed statements were checked against notes or builds at this version.” If a later hotfix lands (for example after 0.8.8), treat older advice as suspect until the badge and “Last updated” date move forward with it.

Why empty tables are intentional

An empty reputation or radiation table with a version column is not unfinished spam — it is a refusal to invent. Filling cells with genre stereotypes would create false precision, hurt players in Iron Man runs, and look like thin AI padding to reviewers. We publish structure first; numbers only after a log exists.