What is this site for?
It is a practical Core Keeper guide library built to help players solve one problem at a time: bosses, routes, items, progression, builds, updates, and return-player questions.
Short answers for the questions readers ask most often
FAQ
Quick answers before you open a guide.
A fast answer first, then the deeper page if you still need it.
This page keeps the common site questions in one place so the library feels easier to use and easier to trust.
Best next page
If the short answer is not enough, use All Pages or Database to narrow the topic faster.
Common questions
Short answers for the main things readers want to know.
Is this an official game site?
No. It is an independent fan guide project and is not affiliated with or endorsed by Pugstorm or Fireshine Games.
How do I find the right page fast?
Use the homepage, the All Pages directory, the Database page, or Search. Those pages are meant to get you to the right page before you start reading a lot.
What if a guide looks outdated?
Check the review note first. If it still feels wrong, send the page URL and the exact mismatch through Corrections or Contact.
Can I suggest a better clue or screenshot?
Yes. Use Contribute when you have a better route cue, image, version note, or a missing topic that would make the page more useful.
Does the site use accounts or paywalls?
No. Readers can browse the guides without signing in or paying.
FAQ maintenance
The FAQ stays believable when the correction path is visible too.
Readers trust a help page more when the site shows where stale answers, broken links, or missing topics should be reported.
Recent visible fixes
Public trust wording was unified across the main navigation and help surfacesAug 18, 2026About, 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.Homepage now surfaces recent corrections more directlyAug 18, 2026The 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.Topic hubs and trust surfaces were refreshed for the August 17, 2026 maintenance passAug 17, 2026Keyword topic pages, footer update labels, and public maintenance wording were tightened so topic landers read more like actively maintained guide surfaces than one-off filler pages.Helpful pages
If the answer is not here, these are the next best places to check.
Site page
All Pages
Open this when you need the next layer of site help.
Open page/pages
Site page
Database
Open this when you need the next layer of site help.
Open page/database
Site page
Contact
Open this when you need the next layer of site help.
Open page/contact
Site page
Corrections
Open this when you need the next layer of site help.
Open page/corrections
Site page
Disclaimer
Open this when you need the next layer of site help.
Open page/disclaimer
Site page
Contribute
Open this when you need the next layer of site help.
Open page/contribute
Best next step
Use the right entry page before you read any deeper.
Use Search firstBest when the exact boss, ore, patch, or map phrase is already known.Use the DatabaseBest when you know the shelf but not the exact page.Use FixesBest when the blocker already has a clear name.Use Contact or CorrectionsBest when a page needs another review or a visible fix log entry.
Why this FAQ exists
The FAQ works best when it keeps the site questions short and easy to leave.
What this FAQ is for
It answers the site questions that keep repeating so the reader can move on faster.
When FAQ is not enough
If the question is really about one page, jump to Search, Database, or the directory instead of staying here.
Why the corrections path is visible
A visible fix path makes the FAQ feel maintained, not frozen after launch.