Unified Xaero Worldmap

Unified Xaero Worldmap 2.0.0

2.0.0 replaces 1.0.0, which was a single build for Fabric on Minecraft 1.21.1.

New

• Builds for Fabric, Forge and NeoForge on every Minecraft version family Xaero's World Map 1.46.x supports: 1.16.5, 1.18.2, 1.19.2, 1.20.1, 1.20.4, 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.10, 1.21.11, 26.1.2, 26.2 and 26.3 (NeoForge from 1.20.4 on). Pick the file for your Minecraft version and loader and install the same one on the server and every client.
• The mod uses the map region format World Map itself writes on each family, and a client and server only sync when they are on the same one (in practice: the same Minecraft family).

Not compatible with 1.0.0

Map data is now sent in one format that works on every loader and Minecraft version (protocol v5; 1.0.0 used v4, which only worked on Fabric 1.21.1). A 2.0.0 player cannot sync with a 1.0.0 server, and a 1.0.0 player cannot sync with a 2.0.0 server. Nobody is kicked: sync just stays off for that player, with a chat message saying which protocol each side runs. Update the server and every player to 2.0.0.

Requirements

• Xaero's World Map 1.46.0 or newer, on the server and every client.
• Fabric: Fabric API for your Minecraft version. Forge / NeoForge: xaerolib, which World Map needs anyway.
• Xaero's Minimap is optional (client only); if you use it, 26.4.0 or newer.

Known limitations

• On a LAN game the host's own map does not sync (Xaero maps the host's world straight from the save); guests sync normally.
• Xaero's "full" cave mode layer is not synced; the sliced cave layers are.
• Map data you had before joining reaches other online players at their next periodic re-sync (every 120 seconds by default), not live.
• A live update for a dimension you have never visited is written to your disk right away only when the server has Xaero's World Map installed (it is required); otherwise it arrives when you enter that dimension.
• Xaero map files in a pre-6.x save format are skipped until Xaero rewrites them.
• Client and server must be on the same Minecraft family. Joining through a version-bridging proxy such as ViaVersion turns sync off for that player, with a message.
• After the server moves to a Minecraft family with a different region format, the shared map starts over and is rebuilt from what players upload. The old server data is kept on disk, not deleted; your own old local map syncs again once World Map rewrites it (by revisiting the area).
• A map region you are looking at reloads briefly when other players' tiles arrive for it.
• Server and every client must run the same mod version.

By Obscura. Unofficial add-on, not affiliated with Xaero.