Built for the question that stops a run

What this site does

Frostrail is a cooperative survival game about keeping the Eden Engine alive while a crew scavenges through a frozen world. During a beta, the most useful question is often not “what is this game?” but “will this save?”, “why can’t my friend join?” or “did we break the quest order?” Frostrail DB starts with those tasks.

Guides lead with a short answer, then give conservative steps a player can try without deleting files, buying access or treating an isolated forum post as a permanent rule. Database pages record only the fields visible in current public material. When damage, recipe cost or server behavior has not been published, the page says so plainly.

Independent and unofficial

Frostrail DB is not operated, sponsored or endorsed by FakeFish, Shiro Games, Shiro Unlimited, Steam or Valve. “Frostrail,” its artwork and other game assets belong to their respective owners. Official screenshots are used to identify and explain the game, with a dedicated media-attribution page linking back to their source.

For purchases, release dates, access decisions and developer announcements, use the official Frostrail Steam page. For beta bugs, use the in-game report button or the tester channels described by the developer. This site cannot grant playtest access, restore a save or speak for the development team.

How pages are maintained

Research begins with official store material, announcements, trailers and build-specific developer notes. Public community discussions can show that a question exists or that a workaround was reported, but they remain labeled as community evidence unless an official source confirms the behavior. Each time-sensitive page shows a visible refresh date.

The database is intentionally smaller than a speculative catalogue. A named item with a visible recipe is more useful than a long list of guessed icons. As the public build exposes stable names, locations, values and mechanics, the records can expand while retaining source context and change notes.

Corrections and contact

If a build changes a guide or you can reproduce a problem more precisely, send the page URL, build context, steps and any public source to [email protected]. We review corrections against current evidence and update the page rather than silently changing a factual claim.

For the full standard, read the editorial policy. For privacy and analytics choices, read the privacy policy.