01

Start from the clue

Describe the image or landmark, the approach, and the interaction. Put a tool or boss gate before the route to avoid wasted trips.

02

What the fragment changes

Record the map layer or route information it reveals, plus the nearby reward worth collecting on the same trip.

03

Keep version boundaries visible

Map data can move after launch patches. Show the last checked date and confidence instead of presenting old Beta coordinates as permanent truth.

04

A fragment route should end with a decision

Read the clue as a landmark: a gate, tower, bridge, dungeon mouth, or elevation change. The approach should say what blocks the trip and which Beacon is the safest reset.

Once the fragment is collected, look at the newly revealed layer before leaving. If a nearby Shell, sidearm, or Beacon is now visible, bundle that detour; if the route is still unknown, mark it and return after the next gate.

The exact total and coordinates remain a current-build check. That is intentional: a short honest checklist is more useful than a confident Beta map that sends players to the wrong room.