Where should I start?
Start from the page that matches the thing failing in your run: oxygen, food, water, material, base, or co-op.
FAQ / Help
Quick answers for using the site well.
Use this page when you are not sure which guide to open, whether a page is still current, or where to report a detail that changed in your run.
Short version
Start with the blocker, not the archive. If you need survival help, use beginner guides. If you need a route or material answer, use the map or resources pages. If the game changed, check the update tracker and reader reports before trusting an older page.
What this page is for
Use FAQ when you need a fast answer about where to start, whether a page still looks current, or which support page to use next. It should solve simple trust and navigation questions without forcing readers into the full policy pages first.
How do I know a guide is current?
Check the review date, patch sensitivity, and whether the page is mentioned in the latest updates or recent maintenance notes.
What if the page feels stale?
Use the reader reports page or the contact correction path and include the page URL, changed detail, and proof.
Do I need an account?
No. The guides, maps, resources, and support pages are available without registration or a paid login.
Common questions
The answers readers usually need during a play session.
Why do some pages say "Last reviewed"?
Because route, resource, co-op, and system pages can age faster than evergreen tips, and readers should know which pages were checked most recently.
Are these official game support pages?
No. This is an independent guide site. For purchases, accounts, refunds, or platform access, use the official game or store support channel.
What if the game changes after I read a guide?
Check the update tracker first. If the change is not listed, send a correction with the page URL, build context, and what happened in your run.
What should I send in a report?
Send one page, one changed detail, one context note, and one screenshot or route proof if the problem is about movement, danger, or materials.
Good paths
Best next clicks for common problems.
| If you need... | Open this | Why |
|---|---|---|
| a route or landmark | Map hub | It keeps route purpose, landmark context, and safety notes together. |
| a page that may have changed | Next to check | It shows which page groups are most likely to be rechecked first. |
| a correction path | Contact corrections | That is the fastest way to send one page and one proof note. |
| guide trust rules | Editorial policy | It explains what the site publishes, reviews, and refuses. |
| site-use rules | Terms of Service | It explains how the site may be used and what not to do with it. |
| maintenance history | Maintenance notes | It shows what has recently been changed and why. |
Why this page exists
A useful guide site needs quick help, not just a contact form.
Most players do not want a long support article. They want a quick answer on where to click next, how to judge freshness, and whether they should trust an older guide or move into the update tracker first. This page keeps those common questions from getting buried inside policy pages or long homepage text.
If you are here because a page looked wrong, stale, or confusing, the best next move is usually simple: check the latest updates, send a correction, and use the narrowest page that matches the blocker.
FAQ help
What the FAQ should answer without making the page feel circular.
The FAQ works best as a short bridge: it should answer the question, then point to the next room. If the answer needs a full policy or a full guide, the FAQ should say that quickly and move on.
- Use this page for simple site questions.
- Use the update tracker when freshness is the real issue.
- Use the support pages when a correction, media, or policy question needs detail.
- Using the FAQ for a problem that really belongs in the guide archive.
- Asking the FAQ to replace the privacy or editorial policy pages.
- Stopping at the answer when a next link would solve the next step faster.
- Open Reader Reports if the issue is about maintenance.
- Open Corrections if one page needs a fix.
- Open Updates if the answer may have changed after a patch.