Editorial & evidence policy

How We Verify Enshrouded 1.0 Builds

Confidence is a label, not a writing style. EmberBuilds distinguishes primary-source facts, practical planning, community leads and in-game reproduction so a polished page never looks more certain than its evidence.

Official basis

Official basis

The claim appears in a Keen Games release post or changelog. We link the primary source and keep its scope intact.

Verification pending

Verification pending

The recommendation is a useful launch plan, but current node values, gear stats or combat outcomes still need reproduction.

In-game verified

In-game verified

This label is reserved for a recorded game version, character and gear state, difficulty, test target and repeatable result.

Verification ladder

How a launch plan becomes a verified guide

  1. 01

    Anchor the mechanic

    Start with the official release description and record the exact patch date.

  2. 02

    Check the live tree

    Confirm names, connections, point costs and displayed values in the current client.

  3. 03

    Reproduce the loop

    Test whether the interaction works as described with an explicit level, gear state and difficulty.

  4. 04

    Compare like with like

    Only rank builds when the target, patch, gear assumptions and success measure match.

  5. 05

    Publish the open edge

    List unresolved behavior and update the changelog when a hotfix changes the recommendation.

Editorial promises

What we will not fake

A useful page can be honest about what it does not yet know.

×

No invented DPS

We do not turn tooltips or a single clip into a cross-build damage ranking.

×

No anonymous “tests”

A verified claim needs the game version, setup, target and method—not just the word tested.

×

No launch-day BiS theater

We publish gear priorities until the current item pool is checked under comparable conditions.

×

No hidden uncertainty

Open values stay in a visible verification queue on the guide they affect.

Corrections

Version changes are part of the guide

Material corrections should update the page date and evidence ledger. Hotfixes that change the recommendation belong in a visible changelog, while minor copy edits do not pretend to be new testing.

Browse current guides