Current site pass
The current pass focuses on clearer entry rooms, stronger support pages, separate family rooms for beginner, building, crafting, progress, and troubleshooting work, and more visible maintenance signals across the highest-use hubs.
Site build notes
Track how the site structure and reader trust signals are changing.
This page records site-facing build notes, not game patch notes. Use it when you want to see how the homepage, guide hubs, support pages, media cues, and player task paths are being maintained over time.
Use this page for site changes, not gameplay routes
Open Version History when you want to know what changed in the site structure, how trust cues were improved, or where a new support page lives. For game patches and official post order, use News. For release-status wording, use Early Access.
What changed most recently
The homepage, guides hub, tools hub, and directory were tightened so readers can tell where guides, tools, support pages, and status pages belong.
Who should use this page
Use it if you compare site versions, review support coverage, or want proof that high-use pages are being maintained in public.
What this page is not
This is not the game patch archive. It exists to explain site-facing changes such as new hubs, trust labels, glossary help, and public support paths.
Current build notes
The latest site structure pass was about clearer rooms, not just more pages.
| Area | What changed | Why it matters |
|---|---|---|
| Homepage | Task-first routing, room definitions, and stronger support links were made easier to see. | Readers can tell whether to start with Guides, Database, Tools, Status, or Support without opening random pages first. |
| Guides hub | Coverage is now explained by lane, blocker, and stage instead of only by archive browsing. | The hub feels more like a route desk and less like a generic content wall. |
| Tools hub | Tool tasks, support rooms, and review paths were split more clearly. | Players can solve the current session problem first, then move into the right support page if the question changes. |
| Support layer | Version History, Glossary, FAQ, and the family-room pages were added as dedicated support pages. | The site now looks more like a maintained game information project with visible help rooms, not only a stack of guide articles. |
| Guide trust cues | Guide pages already show review date, patch sensitivity, build cue, and platform cue on higher-use routes. | Readers can judge freshness faster before trusting a route or co-op rule that may drift after updates. |
Recent milestones
These are the structural changes readers should notice first.
Open next
Use these pages after checking the current site build
- Guides Hub when you need the right page order for a blocker.
- Tools when the current session needs a checklist, route helper, or quick planner.
- Site Map when you want the full public room list.
- Glossary when the search term is broader than the guide title.
Trust layer
These support pages explain how the site is maintained
- About for editorial identity and review direction.
- Editorial Policy for source order and corrections.
- Media Policy for screenshots, diagrams, and replacement requests.
- Community for public reports, correction paths, and contribution rules.
Version history help
What this page should help readers understand in one glance.
Version history works best when it answers three things fast: what changed, why it changed, and which page should be checked next. That keeps maintenance visible without turning the page into a patch-note dump.
- Use this page for site structure, trust, and maintenance changes.
- Use News when you want game patch timing or fresh release context.
- Use reader reports when you want the public correction trail.
- Mixing game updates and site updates on the same page.
- Listing changes without saying why they matter to readers.
- Forgetting to point to the next useful page after a build note.
- Open News for the current review queue.
- Open FAQ / Help for the shortest support answer.
- Open Editorial Policy for source and correction rules.
Build notes depth
What the version page should prove about the site.
The strongest version-history page shows that the site is being maintained on purpose. Readers should be able to tell what got improved, why the change matters, and whether the newer page now deserves more trust than the older one.
- Use build notes to show visible maintenance, not hidden edits.
- Call out when a page moved from thin to useful.
- Link the trust or help page that explains the change.
- Listing version dates without telling readers what improved.
- Mixing gameplay changes with site-maintenance notes.
- Forgetting to link the updated support or policy room.
- Open News for game patch tracking.
- Open FAQ / Help for the shortest trust answer.
- Open About for editorial identity and review scope.