Unified Xaero Worldmap
Xaero's World Map has always been a personal tool. You see the chunks you walked through, and that's it. On a multiplayer server, that means five players mapping the same spawn area while nobody knows what lies past the nearest hill. Unified Xaero Worldmap fixes that by turning the map into a shared resource for the entire server.
Walk somewhere new and it appears on your friends' maps within seconds. No reload, no menu, no commands. Log off for a week, log back in, and your map is already filled in with everything the group discovered while you were away. It is one of those add-ons that quietly changes how a server feels.
What Unified Xaero Worldmap Actually Does
At its core, the add-on synchronizes explored map tiles between every player who has it installed. The behavior is straightforward but the effect is dramatic:
- Explored areas appear on other players' maps in near real time.
- Cave layers sync the same way the surface does.
- The Nether, the End and any other dimension on the server are included.
- Discoveries in a dimension you are not currently in still arrive and wait for you there.
- Maps you explored before installing the mod are shared in the background, so the group map starts with everyone's existing progress.
- Waypoints stay private. Only the explored map itself is shared.
There is nothing to configure on the client side. Install the mod on the server and on each player's game, and the shared map and its config file are created automatically in the world save folder. If you want the simplest possible setup, the foxygame.net launcher handles Unified Xaero Worldmap through its add-on catalog, matching the correct build to your loader and keeping it updated between sessions.
Supported Minecraft Versions and Loaders
The add-on follows Xaero's World Map 1.46, which means it supports every Minecraft version that release covers. That range runs from 1.16.5 all the way up to 26.3, and it is available for Fabric, Forge and NeoForge.
Version and Loader Overview
- Fabric: 1.16.5 through 26.3, wherever Xaero's World Map 1.46 exists.
- Forge: 1.16.5 through 1.21.11.
- NeoForge: 1.20.4 through 26.3, though on 26.3 only NeoForge betas exist so far.
Some versions in between are not supported, including 1.17, 1.19.3, 1.19.4, 1.20.2, 1.20.5, 1.20.6, 1.21.2, 1.21.3, 1.21.6, 1.21.7 and 1.21.9. The reason is simple: Xaero's World Map 1.46 does not exist for them, so there is nothing to build on. File names follow a clear pattern such as unified-xaero-worldmap-version+1.21.1-neoforge.jar, listing the mod version, the Minecraft version and the loader in that order.
How to Install Unified Xaero Worldmap
Setup is the same on both sides, which keeps things predictable. The server and every player need the same file: same Minecraft version, same loader.
On the Server
- Install your loader (Fabric, Forge or NeoForge) for your Minecraft version.
- Place Xaero's World Map, Unified Xaero Worldmap and Fabric API (Fabric) or xaerolib (Forge and NeoForge) into the server's mods folder.
- Start the server. The shared map and its config are generated automatically.
On Each Player's Game
- Install the same mods in the game's mods folder.
- Xaero's Minimap is optional and works alongside the add-on if you pick a compatible version.
- Join the server. The mod checks that both sides match and syncing begins on its own.
When you download Unified Xaero Worldmap, grab the file that matches your Minecraft version and loader. On Fabric you also need Fabric Loader 0.18.4 or newer. On Forge and NeoForge, xaerolib is required, though most launchers install it automatically as a dependency of World Map.
Safety, Compatibility and Performance
Server owners tend to ask two questions first: can someone break the shared map, and will this lag my server? The answers are reassuring. Merging is additive, one 16x16-block tile at a time. Tiles are added or updated, never deleted, so nothing a player sends can erase what someone else explored. Fresh data beats stale data, and old map data only fills gaps.
The mod is optional on both sides, so it never locks anyone out. A player without it joins normally and plays with their own personal Xaero map. A player on an incompatible version stays connected, with sync disabled and a single chat message explaining the mismatch. The same applies to players joining through a version-bridging proxy when map storage formats differ.
Performance-wise, the add-on costs roughly 0.01 ms per client tick. All parsing, merging and disk work runs on background threads at the lowest priority. While at least one other synced player is online, Xaero is asked to save map regions every five seconds instead of every sixty, which measured around 10 percent overhead in an uncapped-FPS test at roughly 2000 FPS. At normal framerates you will not notice it. Server owners can raise liveSaveIntervalMillis to trade freshness for even less work.
Configuration and Known Limitations
The server writes a config file with sensible defaults on first start, and those defaults suit a 5 to 20 player survival server. The settings people actually tune are liveSaveIntervalMillis, maxRegionsPerTick and maxStoreBytes. Values outside the allowed range are corrected automatically, and a broken config is backed up and replaced rather than crashing the server.
A few limitations are worth knowing before you commit. LAN world hosts do not sync their own map, because Xaero already maps the host's world straight from the save, though guests who join do sync. Existing maps travel on a timer rather than live, reaching other online players at their next periodic check, which defaults to every 120 seconds. Newly explored areas are live. Xaero's full cave mode is not synced, only the regular cave layers. Mixed loaders on one server, such as Fabric players on a NeoForge server, have not been tested.
Upgrading Minecraft across a map format change resets the shared map, which then rebuilds from what players upload. Nothing is deleted, and the old server map is kept aside on disk.
Final Thoughts
Unified Xaero Worldmap solves a problem most multiplayer groups did not realize they had. Instead of five private maps and a lot of redundant exploring, you get one living map of the world that grows with every player who logs in. It respects waypoint privacy, refuses to let anyone wipe progress, and stays out of the way performance-wise. If you run a survival server on Fabric, Forge or NeoForge anywhere from 1.16.5 to 26.3, this add-on is an easy recommendation.