Use the map without losing your route
Filter one collectible type at a time, mark only places you have personally cleared, and verify a marker against a second source before spending a rare key. This site does not expose an interactive map until a rights-cleared coordinate dataset is available. Source 1Community interactive map discussionOpen source
Reliable first-pass navigation
Use in-game Beacons as anchors. When entering a region, record the Beacon name, the direction of the hub or major landmark, any locked door, and the return path. Open shortcuts before chasing a distant marker. This method survives incomplete community maps and reduces the chance of losing track after a death.
The Week 1 Update added daytime Beacons in Fainweald and Mammon, revised reward placement, fixed completed objectives reappearing on the map, and added a teleporter after the Grisha pit fight in one dungeon. A launch-week route may therefore show longer runs or fewer navigation anchors than the current build. Source 3The Week 1 UpdateOpen source
The specialist walkthrough currently organizes progression through the Prologue, Widow's Overlook, Mushroom Village, Sunken Village, Flooded Village, Blackridge Cliffs, Gloomshade Grove, Holding Cells, Citadel of Penance, and Desolate Peak, with later regions still being documented at the source check. Source 2Rock Paper Shotgun region walkthroughOpen source
Cleanup workflow
- Finish the region's main route and unlock both ends of shortcuts.
- Filter the external map to one collectible family.
- Compare each marker with your inventory or a location guide.
- Mark it complete only after the pickup or interaction occurs.
- Recheck patch notes if a door, NPC, or item is not in the recorded state.
Use the walkthrough for sequence and the Tarstone page for collectible counts. Named keys such as the Chapel Key have separate route instructions because their task is more precise than general map navigation.
What this page does not claim
The linked community map is not official, and this site does not copy its coordinates or imagery. Marker completeness, names, and locations may change. The page was checked on August 30, 2026 and only describes a verification workflow until a rights-cleared, independently validated dataset exists.
Build a Beacon-first route log
For every new region, record the Beacon name, compass direction or visible landmark, nearest hub connection, shortcut state, locked doors, and the path back. Beacons remain more dependable than an unlabeled screenshot because they exist inside the player's current build.
Use a simple entry such as: “Mushroom Village Beacon → tower path → illusory arch → Chapel Key rope.” This preserves a sequence another player can follow without pretending to provide precise coordinates.
Separate progression from cleanup
During a first pass, prioritize Beacons, shortcuts, main route, and safe return. Mark optional doors and pickups without taking every detour. During cleanup, filter one collectible family and compare it with inventory evidence.
| Pass | Goal | What to record |
|---|---|---|
| First visit | Survive and establish navigation | Beacon, hub direction, shortcut, locked door |
| Quest return | Complete one named task | NPC or key state, prerequisite, reward |
| Collectible cleanup | Verify one item family | Marker, inventory change, source, patch |
| Bug reproduction | Prove a mismatch | Exact route, state, screenshot, build |
Mixing all four jobs makes it difficult to know whether a marker is missing, completed, gated, or outdated.
Patch changes that affect routes
The Week 1 Update added daytime Beacons in Fainweald and Mammon, a teleporter after a Grisha pit fight in one dungeon, revised early dungeon rewards, and fixed completed objectives reappearing on the map. Source 3The Week 1 UpdateOpen source A launch route may therefore remain geographically recognizable while its return path or reward no longer matches.
When an external map disagrees, check the patch before moving a marker. Record whether the mismatch concerns position, access condition, map state, or reward. Those are separate claims.
Region sequence as an orientation aid
The current Rock Paper Shotgun walkthrough covers Prologue, Widow's Overlook, Mushroom Village, Sunken Village, Flooded Village, Blackridge Cliffs, Gloomshade Grove, Holding Cells, Citadel of Penance, and Desolate Peak in its documented sequence. Source 2Rock Paper Shotgun region walkthroughOpen source It is a navigational route, not proof that every detour must be completed in that order.
If an encounter is far stronger than the surrounding route, leave a note and continue elsewhere. Open-world freedom can place a player in a later-risk area before the build is ready.
Key routes
Named keys need more than a general map pin. Record pickup, inventory confirmation, door, dungeon, puzzle, and final reward. The Chapel Key, Crypt Key, and Blackmarrow Key use separate workflows because their locks and rewards are not interchangeable.
Do not spend a rare key based on one unverified community marker. Confirm the item name and expected lock from another source or the live prompt.
Tarstone and Shell cleanup
For Tarstones, filter by region and category, then compare the pickup with the inventory. The current specialist route documents 75 locations, but achievement thresholds and item variants should be tracked separately. For Shells, record the body or interaction landmark and selection result rather than only the map position.
Use the Tarstone guide and Shell roster to prevent duplicate-looking icons from becoming false missing markers.
Night and quest-state markers
Some community reports associate items, merchants, or events with Night Mode or a quest state. A marker without that prerequisite can look wrong during daytime. Record the world state and active quest before reporting a missing event.
Community discussion can help discover a lead, but threads often contain corrections when an event first believed exclusive is later found under another condition. Source 1Community interactive map discussionOpen source Label the state as confirmed only after reproduction.
Verify an external marker
- Open the current build and travel from a named Beacon.
- Match two stable landmarks.
- Confirm required key, mode, or quest state.
- Capture the scene before interaction.
- Verify the inventory, objective, or reward afterward.
- Record the patch and source date.
If the marker fails, reload once and approach from the documented route. Do not mark it removed until another current source or patch note supports the change.
Avoid false completeness
A map calling itself “100%” is still a community claim. Source 1Community interactive map discussionOpen source It may omit later discoveries, duplicate state-dependent events, or retain a fixed marker. This site does not reproduce its coordinates and should not advertise complete coverage without an independently validated dataset.
The useful promise is smaller: a transparent route log that tells readers what was checked, on which patch, and how to report a difference.
Troubleshooting navigation
If a door is locked, verify the key name and prerequisite before assuming a bug. If a Beacon is absent, check day or Night state and installed patch. If an objective reappears after completion, compare with the Week 1 map fix and capture the current state.
If the player is lost after death, return to the last named Beacon and reconstruct one segment at a time. An improvised shortcut can be faster once, but it is poor evidence for a repeatable guide.
This workflow was rechecked on September 3, 2026. The page remains intentionally coordinate-free until the project has a validated dataset it is permitted to publish.
A future interactive map should publish its source date, patch, marker schema, verification state, and correction history. Unconfirmed points need a visible label, completed-state variants must not duplicate locations, and every marker should link to a route that begins at a named in-game anchor.
