Fastest fixes
One page, one issue, one concrete mismatch.The easiest messages to act on name the exact guide, the step that failed, and what the player expected to happen instead.
Corrections, privacy questions, and site feedback
Contact
Send the page URL, the exact issue you hit, and the moment the guide stopped helping.
Short, specific notes are the easiest to check and schedule for a revision.
Use the contact address for guide corrections, privacy questions, broken links, layout issues, or suggestions that make the site more useful in real saves.
This inbox is for the independent Core Keeper guide site and is used for guide feedback, corrections, and reader questions, not account support or purchase issues.
What to send here
Page URL, what felt wrong in your own save, and what you expected to happen. That is usually enough to understand where the next page update should start.
What happens after a report
Specific page reports are easier to update because they can go straight back onto the right guide.
Core Keeper Editorial Desk works best when the message names the page, the issue, and what went wrong in the save.
If the note is concrete, it can usually be matched to a guide step, layout issue, screenshot gap, or wording problem without a long email chain first.
That is why the best reports are small and direct: one broken page, one missing clue, one outdated step, or one repeated visual that is hurting trust. No reader accounts, paid access, Google AdSense, custom analytics, or live ad scripts are enabled today. Cloudflare Insights is used for basic traffic and performance measurement.
Best detail to include
Say what kind of save this was.Patch return, fresh run, late-game cleanup, boss prep, ore route, or map search all point the editor toward a more specific check.
What slows the inbox down
Big complaints without a page link or live example.Notes like 'the site feels off' are harder to use than one broken page, one repeated image, or one route step that no longer matches the game.
What to send
The clearest reasons to contact the site.
Fix a guide
Guide correction
Send a note if a route, boss tip, item location, or progression step looks outdated or unclear.
Ask about data
Privacy question
Use the contact address for privacy questions or concerns about information shown on the site.
Flag site issue
Site feedback
Share layout problems, broken links, duplicate visuals, or places where a page feels hard to use.
Quick notes
The inbox works best when the message stays short and factual.
One page first
The fastest reports point to one URL and one issue instead of a long site-wide complaint.
Patch context helps
Version, hotfix, or mod context makes it easier to tell whether the page or the save changed first.
Visual problems count
Repeated images, awkward spacing, or a screenshot that no longer helps are all useful to report.
How reports get used
Useful reports move faster when they point to one exact page and one exact mismatch.
A good report names one exact page
The clearest note gives the URL, the wrong step, and a little save context so the issue can go straight back onto the right guide.
A broad complaint is harder to act on
Messages like 'the site feels off' are less useful than one broken route, one repeated visual, or one outdated step that changed trust.
Some issues belong on another page
Visible corrections, policy questions, and design cleanup can go through the matching support page when the note is bigger than one guide fix.
Best next pages
Use one of these if your note is really about site trust, not only one broken page.
Open correctionsBest for checking what has already been fixed or reopened.Read the policyBest for learning how edits, reviews, and standards are handled.Review the FAQUseful if your question might already be answered in a shorter form.Browse all pagesHelpful when the issue is real, but you still need to find the right page first.
Fastest email format
This is the simplest structure for a useful correction or layout report.
Start with the page
Paste the exact URL first.
That lets the issue go straight back onto the right guide instead of turning into a guessing game.
Name the mismatch
Say which step, image, or recommendation broke trust.
One unclear screenshot, one wrong route note, or one stale patch assumption is easier to fix than a broad complaint about the whole site.
Describe your save
A little context saves a lot of back-and-forth.
Fresh run, return after a patch, boss prep, ore route, modded setup, or map search all point to different fixes.
Small details that help
A few extra notes make corrections easier to verify.
Include the page URL so the issue is easy to find.
Mention the platform or game version if the issue depends on a patch.
Describe what you expected to happen and what the page currently says.
What this inbox can help with
Guide and site feedback belong here; game account support does not.
Guide pages are free to read and do not require registration.
The site does not provide downloads, cheats, account support, or paid game access.
The inbox is used for site maintenance and corrections, but it is not a live support channel.
Use official game support channels for purchases, account issues, or game-service problems.