Map workflow
Start with the clue you have
Map pages work best when you know a place name, coordinate, fort, island, city, shipwreck, or treasure clue and need to decide what else is nearby.
Route picker
Which map route should you run?
Use this table when a marker is visible but the best next page is not obvious.
| Your clue | Map action | Next page |
|---|---|---|
| Coordinate only | Search the coordinate and check the nearest region | Locations or Treasure Maps |
| City or island name | Filter by the area and scan nearby checks | Collectibles |
| Fort or hard water route | Check nearby sea lanes before engaging | Jackdaw Upgrades or Naval |
| Treasure clue | Match pickup area to dig coordinate | Treasure Maps |
| Mission sends you back | Search the mission area before replaying | Walkthrough |
Route order
A quick map cleanup loop
Use this loop when a route has several nearby icons.
- Search the city, island, or coordinate in the lookup.
- Open nearby treasure maps and Jackdaw plan rewards first.
- Clear viewpoints, fragments, shanties, chests, and keys while already there.
- Return to Walkthrough only if the region is tied to a sequence or memory.
- Confirm the current map marker before treating an older route hint as complete.
September route check
Re-open important markers after Title Update 1.0.7
Ubisoft's official news feed lists Title Update 1.0.7 for September 1, 2026. That confirms a current build checkpoint, not that every coordinate moved. Recheck the marker that matters to your save before beginning a full Caribbean sweep.
- Search the exact coordinate, city, island, fort, or shipwreck you need before opening a broad region filter.
- Confirm the marker in your current save, then bundle nearby collectibles, treasure, and viewpoint checks.
- If the marker looks different, keep the old clue as a route hint and record the current landmark before sailing again.
Coordinate reading
How do you use a map coordinate without landing at the wrong place?
A coordinate is a starting point, not a complete route. Treat the two-number clue, the parent location, and the visible landmark as three separate confirmations before you spend time sailing.
- Save the original coordinate exactly as you found it before trying a variation.
- Confirm the island, city, fort, or water route attached to the point.
- Bundle the nearest collectible, treasure, and viewpoint checks while you are there.
- If the marker is absent, keep the coordinate as a clue and do not invent a replacement.
| Clue state | Map action | Confirmation |
|---|---|---|
| Two numbers only | Enter the pair with or without punctuation | The result names a place or nearby marker |
| Coordinate plus island | Search the island first, then narrow the point | The marker sits in the expected regional context |
| Coordinate plus reward | Open the matching collectible or treasure family | The reward type agrees with the route |
| Several nearby results | Compare parent location and landmark | Choose the result that matches the current save |
| Old coordinate no longer lines up | Recheck the anchor after the update | The live marker or landmark confirms the next step |
Map systems in the current build
Use the map as a verification loop, not a pin collection
Resynced's map is tied to progression systems: forts reveal regional points of interest, Pathfinder draws a water route, and Follow Sea can steer the Jackdaw after you set a destination. Title Update 1.0.7 also fixed cases where completed icons or a conquered region failed to update, so a map check should include the save state as well as the marker.
- Search the coordinate, island, or named landmark and write down the parent region before sailing.
- If the route crosses open water, set Pathfinder first; use Follow Sea only after checking the destination and a safe interruption point.
- After a fort and full regional synchronization, reopen the map and confirm that the region points of interest are visible.
- If a completed icon remains stale, reload the save or revisit the smallest local cluster before assuming the coordinate moved.
- If a target ship is missing, check the current quest or encounter state; 1.0.7 fixed several out-of-map and map-icon update cases.
Coordinate field notes
Arrive, verify, and leave a coordinate with a landmark attached
Coordinates are easy to copy and easy to misread. A useful travel note keeps the number, the region, the visual anchor, and the expected reward together. If one part disagrees, the note remains useful without pretending the marker is certain.
- Enter the coordinate before opening broad filters so the map can return the narrowest useful result.
- Compare the result with the parent place and visual anchor before sailing.
- Use Pathfinder for the water leg and keep a manual interruption point when Follow Sea is active.
- After the stop, update the field note with the live marker and completion proof, even if the result differs from the old clue.
| Field note | Record this | Why it matters |
|---|---|---|
| Number pair | Exact digits and punctuation as found | Prevents a typo from becoming a new invented route |
| Parent place | Island, city, fort, or water lane | Narrows the map result and travel plan |
| Visual anchor | Ruin, beach, mast, tower, dock, or rooftop | Lets the player verify the point in the current build |
| Expected family | Chest, shanty, fragment, plan, contract, or mission | Stops a nearby result from being mistaken for the target |
| Completion proof | Icon, reward, counter, or objective state | Shows whether the route actually closed |
Region packet route
Turn one confirmed point into a route worth the sail
Once the marker is confirmed, the map job changes from finding a point to choosing what should travel with it. Use the same landing, dock, or water heading to bundle nearby checks, then close the packet with a save or counter proof.
- Do not add a nearby marker just because it appears on the map; keep it only when it shares the route line or solves the next player goal.
- Use the location name with the coordinate so a return trip can start from a place, not from an unlabelled number pair.
- Keep a packet marked partial when a reward, counter, or access condition is still missing. Partial is safer than silently treating a nearby point as complete.
- After the packet closes, hand the next problem to Collectibles, Treasure Maps, Naval, Jackdaw, or Walkthrough instead of repeating the map search.
| Packet stage | Player action | Leave only after |
|---|---|---|
| 1 · Pin | Confirm the coordinate, parent place, and visual anchor | The marker agrees with the current save |
| 2 · Reveal | Sync a viewpoint, fort, or location hub when it controls nearby visibility | The local region and travel line are readable |
| 3 · Bundle | Add collectibles, treasure, shanties, contracts, or Jackdaw checks sharing the same landing | Every added stop has an owner page and a reason to stay |
| 4 · Travel | Set Pathfinder, choose a safe interruption point, and sail with the correct supplies | The destination and fallback port are known |
| 5 · Close | Check the marker, reward, counter, or objective state after the stop | The packet is complete or the unresolved family is recorded |