Interactive maps are useful, but Early Access changes quickly; cross-check every marker in-game before treating it as final.
Prerequisites
- Beacon naming system
- Screenshot folder
- Patch date notes
- Own save verification
Uses
- Route planning
- Screenshot checklist
- Patch recheck workflow
Guide Steps
Verification Step 1
Approach from a known safe corridor and set a return beacon before crossing into unfamiliar terrain.
Verification Step 2
Scan from the edge first: terrain color, sound cues, creature patrol routes, and usable entrances matter more than rushing inward.
Verification Step 3
Record what changed after each visit: safe depth, visible landmarks, hostile boundaries, and any blueprint or lore scans found.
Verification Step 4
Treat unverified map markers as leads, not facts, until you confirm them in your own save.
Screenshot and version recheck
This page does not invent coordinates, drop rates, or screenshots. Use the screenshot briefs in the sidebar after implementation, and recheck recipes, blueprint names, and route entrances after patches.
Common Mistakes
- Copying third-party markers without attribution
- Publishing exact points without checking patch date
- Replacing in-game navigation habits