Knowledgebase

Evidence policy

The DayZ Friend Knowledgebase is built from the files supplied for the relevant game version. This page explains what its labels mean and how unsupported claims are handled.

What counts as evidence?

A guide can simplify technical information for players, but the underlying claim still needs to be supported by the supplied DayZ files. Configuration values, explicit source-code behaviour and calculations from those values can be documented. Missing information is marked as unknown rather than inferred from a classname, a field name or a community source.

Found in the files

Direct source fact

A value or behaviour stated directly in the supplied DayZ configuration, script, localisation or relationship data. Examples include an XML attribute, an item classname, or an explicit branch in the game source.

Followed through the configuration

Resolved inheritance

A value inherited from another configuration class. The guide keeps the inheritance chain so you can see where the value came from instead of presenting it as a guess.

Worked out from known inputs

Calculated

A result produced from a documented formula using known source values. Calculated results are labelled as calculated and are not presented as observed gameplay unless the source establishes that connection.

Not established by the supplied files

Unknown

The files do not establish the answer. This can include engine behaviour that is not exposed, runtime state, undocumented units or claims that would require in-game testing. Unknown information is left unknown rather than filled in from assumptions.

What the guides do not do

They do not copy values from community wikis, videos, forums or memory as if they were source facts.
They do not treat a field name as proof of undocumented game behaviour.
They do not invent units, gameplay limits, timings or compatibility rules that the files do not define.
They do not treat a missing entry in one file as proof that a classname cannot exist elsewhere.
They keep game versions separate and preserve exact source values where precision matters.

Corrections and updates

When better source material becomes available, the relevant guide is rebuilt for its stated game version. Corrections should explain what changed and why. A source-backed guide is not a guarantee that a server configuration will work in-game: always validate the file and test it on the intended platform and mission.

This policy is also linked from the source section at the bottom of Knowledgebase articles.