Unified Xaero Worldmap

Share and sync Xaero's World Map between players on a multiplayer server. What one player explores appears on everyone's map, caves and all dimensions included, and players catch up on join. Fabric, Forge, NeoForge, 1.16.5 to 26.3.
Back to Files

Unified Xaero Worldmap 2.1.0 (NeoForge 26.3)

File nameunified-xaero-worldmap-2.1.0-26.3-neoforge.jar
Uploader
NavrelisNavrelis
Uploaded
Nov 12, 2026
Downloads
51
Size
628.0 KB
Mod Loaders
NeoForge
File ID
9576294
Type
R
Release
Supported game versions
  • 26.3

Curse Maven Snippet

NeoForge

implementation "curse.maven:unified-xaero-worldmap-1704237:9576294"

Learn more about Curse Maven

What's new

Unified Xaero Worldmap 2.1.0

2.1.0 lets a server admin fill the shared map without anyone walking there. /uxwm import merges existing Xaero World Map folders into the shared map, and /uxwm render makes the server draw the surface map itself from chunks that are already generated in the world files (for example pre-generated with Chunky). Both reach the players through the normal periodic check, within 2 minutes by default for the dimension they are in. A server-drawn tile never overwrites a chunk a player really mapped, and a real visit always replaces it.

Who should update: server operators who want the new commands, and players who want to see the server-drawn map. Imported maps reach every player, 2.0.x included. Server-drawn tiles are sent to players on 2.1.0 only, so players should update too, but there is no need to update everyone at once.

New

  • Import existing maps (server). Put Xaero World Map folders (a player's xaero/world-map/<world> folder, the map of a singleplayer world, several players' maps) into <world>/unified_xaero_worldmap/import/ and run /uxwm import [<folder>], or just start the server: a non-empty import folder is imported at every start. Dimensions (Overworld, Nether, End, modded) and cave layers are recognised from Xaero's own folder layout, and .zip and .xaero region files are both read. The import only fills gaps: tiles the server already has win. Processed files are moved to imported/<date-time>/ after the data is saved, nothing is deleted, and a second import of the same data changes nothing.
  • Server-drawn map (server). /uxwm render [<dimension>] reads the chunks that are fully generated in the world's region files, through the server's own chunk IO, and draws their surface into the shared map. It generates and loads nothing, and it reads only chunks that are saved to disk, so run /save-all first. With no argument it draws every level without a ceiling; the Nether (a level with a ceiling) is drawn when you name it. Only the surface is drawn, so caves and the Nether keep filling from players. It works one region at a time, nearest the map origin (region 0,0) first, a few chunks per tick and never while the server is lagging, and it resumes after a restart.
  • Commands. /uxwm import and /uxwm render and /uxwm cancel need permission level 3, /uxwm status level 2. /uxwm status shows the regions per dimension (real and server-drawn), the store size, the running task with progress and estimated time, and the last finished task. One task runs at a time. Every command answers at once, also over RCON (/uxwm import with Import queued: import/...); the summary of an import or render follows in the server log (lines start with Map import: or Map render: ) and, if you are still online, in chat.
  • Two server settings: backgroundIoMillisPerSecond (default 200, the IO time that import and render may use per second) and renderChunkReadsPerTick (default 32, chunk reads of a render per server tick). New in config.json; a config from 2.0.4 gets the keys added on the next start.
  • Players keep their own tiles. Server-drawn tiles live in their own store (generated/, next to the player map store v2/) and carry a marker. A real tile always shadows a server-drawn one: when a player visits a server-drawn chunk, World Map redraws it from the real world and the real tile replaces it for everyone. A 2.1.0 client that downloads a server-drawn tile where it has a real tile of its own keeps its tile and sends it up.

Good to know

  • 2.0.x players keep syncing as before, receive imported maps, and are served exactly what a 2.0.4 server serves. They do not get server-drawn tiles until they update; an online 2.0.x player gets one chat line per player per server run, while the server holds server-drawn tiles, asking them to update.
  • An import can put an older tile over a player's newer one, but only for a tile that player never sent to this server (mapped before the mod was installed, or with sync off). It is the same "first uploader wins" that 2.0.x already has when two players with older maps join a fresh server. Import the newest maps, and import before players join. A visit redraws the chunk and heals it for everyone.
  • Several mw$ folders in one dimension (separate worlds behind one address) are not mixed: that dimension is refused and its files stay in import/; import one mw$ folder at a time.
  • Going back to 2.0.x is safe: the player map store v2/ is written exactly as before. A 2.0.x server logs one warning per start for each new folder (generated, import, imported) and leaves them alone.
  • Imports and renders are not broadcast live; online players receive them at their next periodic check (reconcileIntervalSeconds, 120 seconds by default). That check covers the dimension a player is in, with its cave layers; the tiles of another dimension arrive when the player enters it.
  • If an import or render fails, the error goes to the server log with its stack trace, /uxwm status shows it as the last task, the server keeps running and the next task can start. A failed render stays resumable: it resumes at the next server start and may fail again there (logged); /uxwm cancel while it runs ends it for good.

Unchanged

The zoom-out fix of 2.0.4, the Windows save retry of 2.0.3 and the copied-tile guards and report of 2.0.2 are unchanged. See their changelogs.

Compatibility

2.1.0 works with 2.0.4, 2.0.3, 2.0.2, 2.0.1 and 2.0.0 in any combination of client and server. The network protocol (v5), the map file formats and every message are unchanged; the one addition is an optional bit in the client's hello that older servers ignore. You can update servers and players one by one. Still not compatible with 1.0.0 (protocol v4); sync stays off with a chat message until both sides run 2.x.

Test result

  • Automated tests: 916 core tests, run on Java 17 and on Java 8 (1832 runs), all passed.
  • Real game, two clients and a server (1.21.1): the import and render scenarios passed 52 checks, the import with a server restart 35 checks, 0 failures.

Requirements

Unchanged from 2.0.4:

  • 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

  • Server-drawn tiles reach 2.1.0 players only.
  • Maps of another Minecraft family (another region format, for example 1.16.5 maps on a 1.21.1 server, or maps from before World Map 1.46) are skipped by the import and counted.
  • There is no undo for a render once players have synced it; deleting the generated folder before anyone has synced removes it.
  • The render marks its tiles with a version byte that World Map treats as "greater than 0". A 2.1.0 client checks that at start-up and does not take part in server-drawn tiles if its World Map behaves differently. A player who turned off World Map's update_chunks never redraws an existing tile, so their visits do not replace server-drawn tiles.
  • On a LAN game the host's own map does not sync, client and server must be on the same Minecraft family, and the server and every client must speak the same protocol version (all 2.x versions do, so 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 and 2.1.0 can be mixed; 1.0.0 cannot).

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

This mod has no additional files