Name the symptom first
Choose the route that matches the failure type before opening the guide that solves it.
A symptom-first help page for players who know what feels wrong but not the right first route
Common problems
Match the symptom to the right first desk.
This page is here to stop broad player problems from turning into random clicks through unrelated shelves.
Start here when the player question still sounds like a symptom: lost, underpowered, directionless, stuck after a patch, or unsure which route owns the next session.
One desk first
Stay with one first desk until the weak layer is clear instead of mixing map, boss, ore, and update questions together.
Leave as soon as it is clear
Once the real issue has a name, move into the direct guide, tool, or database entry immediately.
Page contract
Common problems stays useful when the symptom boundary is obvious.
What this page solves
It matches a fuzzy player symptom to the right first desk before a reader opens unrelated shelves.
When to leave
Leave once the symptom has a clear name. The direct tool, map page, or database entry should take over next.
Why it stays visible
Recent fixes and feedback notes show the symptom desk is edited against real reader confusion, not left as a static link list.
Main symptoms
These are the most common player problems that deserve their own first route.
Direction
I do not know what to do next.
Use the roadmap, progression pages, or progress checklist when the save is busy but still lacks one clear next milestone.
Map confusion
I am lost on the map or cannot trust my old route.
Start with the interactive map or the map-focused update checks when the real blocker is still a biome lane, landmark clue, or return path.
Boss wall
A boss keeps stopping me.
Open boss prep or boss order when the fight itself is the wall, not one ore tier or one broad patch note.
Route value
I do not know which material or ore deserves the next session.
Use the ore priority tool or item shelf when the real issue is picking the route that pays back now.
Return trip
The old save feels wrong after an update or long break.
Run the returning-player check before reopening the full updates shelf so the first reset page stays small and useful.
Exact object
I know the item, boss, biome, or object name already.
Use the database when the object is clear and the main problem is reaching the right page family quickly.
Quick route table
Use the symptom shape, not the section name, to decide the first click.
ProblemBest routeWhy
The save feels broad and fuzzy
Help Center or progress checklist
Use a broad first-pass desk before opening several unrelated guides.
The route itself feels wrong
Interactive map or map-after-update check
This usually means the first issue is route trust, not the final target name.
A specific fight is now the only wall
Boss prep or boss order
Once the fight owns the session, the best answer is a narrower boss route.
The material choice still is unclear
Ore priority or items shelf
Do not let ore prestige choose the session before the blocker is named clearly.
The old save became shaky after a patch
Returning Player Check
Choose one reset route first instead of rereading the whole updates shelf blindly.
I only need the exact page fast
Search or page directory
Use the shortest lookup route when the topic already has a name.
After the match
Once the symptom has a route, move into the desk that finishes the real job.
Open Help CenterGo back here when the symptom still is broad and no single route has earned the next click yet.Open Returning Player HelpUse the dedicated return-help page when patch trust or old-save drift still is the main issue.Open the tools deskSwitch here when the symptom now clearly belongs to one practical helper.Open the page directoryUse the full directory when the symptom is solved and you only need the exact page title next.
Latest help updates
These were updated recently because they solve broad problems readers keep bringing back to the help desk.
Visible maintenance
Broad symptom pages feel more real when readers can see what changed and where feedback actually goes.
Section desk
Core Keeper Editorial DeskIndependent fan guide publisher
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
Send the symptom, page URL, and what result you expected.If a guide missed your case, send the page URL, game version, and the exact step, screenshot, or route cue that felt wrong.