Editorial policy

Source order

Official Steam store details, developer announcements, official videos and public developer statements are the first sources for release timing, supported features and named mechanics. A current in-game screen or official screenshot can support the specific fields it displays. It does not automatically support values or behavior outside the frame.

Community discussions are used carefully. A post can establish that a player encountered a problem, and a reply can document a workaround that someone reported. Until the result is reproduced broadly or confirmed by a developer, the page describes it as a report or community workaround. We do not convert reply counts into certainty.

Pre-release and beta data

Frostrail is scheduled to enter Early Access, so mechanics, interface, balance and availability can change. Build-specific pages show a refresh date. Old pre-alpha values are not mixed into a current-beta table without a visible historical label. An announcement about “progression between levels” is not rewritten as a guarantee about manual saves or beta carryover.

Unknown values remain unknown. We do not fabricate weapon tiers, quest names, server settings, drop rates, fuel efficiency or recipe conversions to make a database look complete. A short accurate database is preferable to a large fictional one.

Guide structure and safety

Operational guides begin with the shortest defensible answer, then provide reversible troubleshooting steps. Risky instructions—deleting saves, modifying game files, using unofficial keys or exposing account credentials—are not suggested without clear developer guidance and a stated recovery path.

When a question is unresolved, the guide should still help the reader capture the right host/client state, quest text, error message or action order for a useful beta report. The site does not present itself as the developer’s bug tracker.

Corrections and changes

Corrections can be sent to contact@frostraildb.wiki. Include the affected URL, the claimed correction, the game build or date, and a public source or reproducible observation where possible. Material corrections update both the affected sentence and its context; we do not preserve a known error for search traffic.

Minor spelling and clarity edits may be made without a public change log. Changes to a mechanic, date, official status or recommended procedure should update the visible page date. Sources are linked near the bottom of relevant guides so readers can inspect the underlying material.

Commercial independence

Coverage is chosen for player usefulness, not because a source, developer or advertiser requested favorable treatment. If the site later displays advertising or uses affiliate links, those relationships will be disclosed and will not alter the evidence standard. At launch, no advertiser determines the content or ranking of a guide.