Choose the desk first
Decide which major surface should own the next click before you open a deep guide page.
A practical site-guide page for choosing the right major desk before you start reading
How to use this site
Know which major page should own the next click.
This page exists so readers do not have to guess whether homepage, help, search, tools, database, map, or updates is the right starting point.
Use this page when the main question is not yet the game problem itself, but how to move through this site in the fastest and cleanest way.
Use exact language when possible
Once the term is clear, search and database usually become faster than broad browsing.
Leave broad routes early
As soon as the problem has a smaller shape, switch into the exact page, shelf, or helper.
Page contract
The site guide reads better when its role, boundary, and exit point are all visible.
What this page solves
It helps readers decide which major desk should own the next click before they start reading deeply.
When to leave
Leave once the topic itself is clear. After that, the help, tool, database, map, or update desk should take over.
Why it stays visible
The site-guide page feels more real when it shows the same maintenance trail as the rest of the library.
Main site desks
These are the core surfaces that make the site work like a maintained library instead of a pile of isolated posts.
Homepage
Use the homepage when you need the shape of the whole library first.This is the best first stop when you want the main task desks, return surfaces, and current high-value routes all visible together.Help Center
Use Help Center when the player only knows the symptom and not the right first page yet.This is the strongest first route for broad questions like lost, underpowered, directionless, or old save feels wrong.Search
Use search when the player can already name the boss, ore, biome, patch term, or blocker.Search is faster than browsing once the phrase itself is clear enough to type directly.Database
Use the database when the object is known but the right page family still is not.This is ideal for one item, boss, ore, location, or progression shelf question.Tools
Use tools when one decision still needs to be narrowed before another full guide makes sense.Boss order, ore priority, progress checklist, and returning-player check exist to solve that first decision step.Updates
Use updates when patch trust, old-save drift, or return-player retests are part of the problem.This is stronger than generic browsing when the old answer may still exist but no longer be fully trustworthy.Site route table
Use the shape of the question to decide which main desk should own the next click.
ProblemBest routeWhy
I only know the feeling of the problem
Help Center
Symptom-first help works better than forcing the wrong shelf too early.
I know the exact term
Search
Search is fastest once the boss, ore, biome, or patch phrase is already clear.
I know the object but not the page
Database
Structured shelves are better than noisy keyword guesses here.
I need one decision before more reading
Tools
Use a helper when the next click still depends on boss order, ore timing, milestone fit, or return-player reset logic.
The save is old or patch-sensitive
Updates or Returning Player Check
Version trust becomes the first question before many older routes can be trusted again.
I know the topic, but I cannot remember the page title
All Pages directory
The full directory is better than random browsing when the topic family already is clear.
Support routes
These pages help once the site-usage question turns into a smaller search or symptom question.
Open Search HelpUse this if the real confusion is about search terms rather than which main desk to use.Open Common ProblemsUse this when the site-guide question still is really a player symptom question.Open All PagesUse the full directory when the topic is known and you want the exact title fast.Open LatestUse the maintenance desk when you want to see what was updated or corrected most recently.
Latest help updates
These support pages were updated recently because the site guide has to stay current too.
Visible maintenance
Site-guide pages should show public fixes and a clear feedback route like the rest of the library.
Aug 18, 2026
Public trust wording was unified across the main navigation and help surfacesAbout, contact, weekly, pages, topic, and policy surfaces now use clearer update language so the site reads like a normally maintained guide library instead of a repeated review template.
Aug 18, 2026
Homepage now surfaces recent corrections more directlyThe front page now has a clearer maintenance trail so readers can see recent fixes, current editors, and the public correction flow without digging through lower pages first.
Feedback route
Tell the desk which part of the site guide still felt unclear.If a guide missed your case, send the page URL, game version, and the exact step, screenshot, or route cue that felt wrong.