Unified Xaero Worldmap

Unified Xaero Worldmap 2.0.3

2.0.3 is a small fix release for Windows. When the server saves a region of the shared map (the map store under <world>/unified_xaero_worldmap; in singleplayer the same store runs once the world is opened to LAN), it replaces the region file with a freshly written temporary file. Windows refuses that replacement while another program has the region file open, for example antivirus, a backup tool or a search indexer, and 2.0.2 and earlier then logged an ERROR "Failed to write region ..." with a stack trace. 2.0.3 retries, and a refused save is now a short warning. It adds no features and changes no settings.

Who should update: server operators on Windows, and players on Windows who open their singleplayer world to LAN. On Linux servers nothing changes. Updating is optional but recommended, and there is no need to update all players at once.

Fixed

• Saving a region no longer logs an ERROR when Windows refuses to replace a region file that another program has open (server). No map data was lost before either: the region stayed in memory, players kept getting it, and the next save (by default 30 seconds later) wrote it. Only at server shutdown could a refused save leave the file on disk older than what players had (their clients still had the tiles).
• What the server does now: it tries the replacement several times within about a second. Each save round waits at most about 3 seconds in total, so a folder that stays locked for a long time does not stall the map. If the file still cannot be replaced, the server logs one WARN per region, without a stack trace, saying that the file is open in another program and the region will be saved at the next save, and an INFO line once it is saved. At shutdown it tries a second time after a short pause, and if regions still cannot be saved it logs one ERROR line with their count.
• Other write errors (for example a full disk) are still logged as ERROR with the stack trace, as before.

Unchanged

The copied-tile guards and the report of 2.0.2 are unchanged. See the 2.0.2 changelog for them, including "If your map already has copied tiles".

Compatibility

2.0.3 works with 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 config key are unchanged, so 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.0.x.

Test result

• Automated tests: 745 core tests, also run on Java 8.

Requirements

Unchanged from 2.0.2:

• 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

Unchanged from 2.0.2: see the 2.0.2 changelog. In short, 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.0.x versions do, so 2.0.0, 2.0.1, 2.0.2 and 2.0.3 can be mixed; 1.0.0 cannot).

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