VoxelMap-Updated fixes blurry minimaps on Retina and high-DPI displays

VoxelMap-Updated shipped 26.3-1.16.13 on 24 September across Fabric, Forge and NeoForge, and the changelog has exactly one entry: Retina and high-DPI displays render the minimap and all map elements sharply again instead of at the wrong scale.

What was broken

On a high-DPI display, the operating system reports a scaling factor – typically 2x on a Retina panel – and applications are expected to render at the higher pixel density while laying out at the logical size. Minecraft handles this at the window level, but any mod drawing its own GUI has to respect the same factor when it computes texture coordinates and element sizes.

Get it wrong and you get one of two failure modes: elements drawn at half size in a corner, or elements drawn at the right size but sampled from a texture at the wrong resolution, which produces a soft, smeared minimap. VoxelMap-Updated users on Retina Macs and 4K Windows laptops at 200% scaling had been living with the second one.

It is a small bug with a large annoyance factor, because a minimap is something you look at constantly and peripherally. A blurry one is worse than no minimap at all, since you end up opening the full map to read what the corner should have told you.

Navigating unfamiliar Minecraft terrain

Why the “Updated” in the name

VoxelMap is one of the oldest minimap mods in Minecraft, and the original project stopped tracking current versions some years ago. VoxelMap-Updated is a community continuation that keeps the same feature set and interface moving forward through new game versions.

Continuation forks are common in Minecraft modding and they carry a specific risk profile. The feature set is mature and well understood, which is good. The codebase was written against a much older game and has been patched forward repeatedly, which is why display-scaling bugs like this one surface at all – the original rendering code predates the era when high-DPI displays were the default.

That is the trade with any long-lived fork. You get a mod nobody would build from scratch today, maintained by people who care enough to keep it alive.

Where it sits against the alternatives

The minimap space has three serious options and they differ more than people assume.

The choice is usually made on waypoints and on what your server allows rather than on rendering. The full comparison is in the minimap mod roundup for 26.3.

A landmark used for navigation in Minecraft

The server permission question

Minimaps that show mob and player positions are a genuine gameplay change, not a cosmetic one. A player with entity radar can see an ambush before it exists, find a hidden base by its mobs, or track another player across the map.

Most PvP servers block or restrict this, either by policy or with a server-side mod that strips the data. Most cooperative SMPs allow it without much thought. Neither is wrong, but it should be a decision rather than an accident, and it belongs in the same conversation as the rest of your protection and claims setup.

If you are joining a server rather than running one, check before you install. Radar features are one of the more common causes of an accidental rule violation by a player who genuinely did not know.

Updating

Straight swap. The map cache format has not changed, so your explored-chunk data and waypoints survive. Back up the waypoint file anyway if you have accumulated a lot of them – waypoints are the single most annoying thing to lose and the easiest thing to forget to copy during a version migration.

Version tags to watch: 26.3-1.16.13 for Fabric and Forge, 26.3-1.16.12 for NeoForge. The version numbers are not aligned across loaders, which is a reliable way to install something slightly older than you meant to.

A note on the download counts

The 26.3 builds show download numbers in the tens rather than the thousands, which is not a sign the mod is dying. It is a sign 26.3 is new and the minimap crowd, who tend to be invested in long-running worlds, has not moved yet. That pattern repeats every version and is a reasonable proxy for how far along a version migration wave actually is.

Cache size and cleanup

Minimap mods that render a persistent world map store cached chunk imagery on disk, and VoxelMap is among the more generous with it. A long-running world explored across several thousand blocks will accumulate a cache measured in hundreds of megabytes.

That is usually fine and occasionally not – a laptop with a small SSD and five modded worlds will notice. The cache lives in the mod’s own folder rather than in your save, so deleting it loses your rendered map but nothing else, and it rebuilds as you re-explore.

The thing not to delete is the waypoint file, which sits in the same folder and is the only part of the data you cannot regenerate by walking around. Copy it somewhere before any cleanup.

Images: Ice and Fire project gallery.