Minecraft Forums

You are the win, MamiyaOtaru! we've donated, and I encourage everyone I know personally that uses VoxelMap to donate. No server upgrade until we have VoxelMap support for the new release!

Just a note to anyone who may be getting this error: Unknown World!
VoxelMap is one of my essential mods and I love it, but I'd been having a nagging issue with "Unknown world" errors in chat whenever I'd change worlds. I tried multiple server plugins as suggested in this thread to manage the world names, but no matter how many times I'd chosen the world in the map UI it never saved.

I just found out it's because I was using our world names with colons. Our worlds always follow a naming convention of "Destinos:WorldName" and I was using that convention in VoxelMap.

When I just on a whim, thought to try "Destonos_Worldname" it started working fine So if you're having this problem, try eliminiating :'s (and maybe other special characters?) from your names in VoxelMap.

new version

1.9.18

• Sheep colors (all of them *cough jeb_*)
• Smoother minimap motion when player is moving at high speed (lerping all the things)
• fix for squaremap transparency stencil not working correctly with minimap rotation on (primarily of use to resource pack authors)
• fix for radar being unable to be turned back on after turning it off (1.12)
• updated packed mixin library (1.12)

release for 1.16.

bumped version number

1.10.0

• Redone much of the icon system to better reflect the shape of mobs. Mobs that use a second layer aren't necessarily all simple rectangles now
• various things to get ready for 1.16, like being able to have multiple dimensions with the same dimension type
• big UI refactor

Some old changelogs that weren't listed here:

1.9.19

• on the map, sky color shows now (instead of being black all the time)
• upper slabs and staircases etc correctly show up as non transparent blocks on minimap

1.9.20

• radar icons no longer occasionally flash when new ones are loaded
• fixed possible miscoloration of some radar icons
• blocks with custom models worn on heads are more accurate

some new fixes

1.10.1 (and 1.19.21 for MC 1.15)

• fix player names on the minimap with high definition resource packs

1.10.2 (and 1.19.22 for MC 1.15)

• fix for icons for unknown mobs with non standard models (seems to also fix some icons showing as black squares)

1.10.3 (and 1.19.23 for MC 1.12-1.15)

• Can use non-roman characters in waypoint names. (fix to ensure waypoints file is stored with unicode encoding)

1.10.4 (and 1.19.24 for MC 1.15)

• fix for donkey, mule, and zombie/skeleton horse icons
• Forge release for 1.16.1

bad one snuck through when I enabled unicode letters in waypoint names. Fix uploaded

1.10.5 (and 1.9.25 for MC 1.12 - 1.15)

• fix bug causing duplicates of waypoints

I'm a longtime user. Having an issue I see just this morning where some worlds on a multi-world sever are not selecting the correct map.

Anything I can do here? I really don't want to have to reinstall Voxelmap and lose all my data.

new version

1.10.6 (and 1.9.26 for MC 1.12 - 1.15)

• config file moved to /config folder. Cache and waypoint data moved out of /mods to /voxelmap folder
• fix for world map data not saving on exit
• support for 512x resource packs (assuming Minecraft itself can handle them)
• fix for entities in minecarts/boats or on non living entities being rendered too high
• world map cache memory usage reduced ~25%
• VoxelMap can now handle more than 65536 unique blockstates (basically unlimited)

Quote from addlepated0329299»

Yeah, it seems from moving the cursor that the coordinate display changes corresponding to the area of the map. However, the further zoomed out I am, the more off the coordinates displayed are from the actual world. If I want to get an accurate coordinate set from the world map, I have to zoom all the way in, and even then can be 50-100 meters off from where I am in the world.

When zoomed all the way out, it's wayyyyy off. As an example, I'm currently standing on -340, +250. I hit 'M' for world map and hovered the cursor above my icon. It says I'm at -1150, -242. The numbers change depending on where the map is centered.

https://imgur.com/8VsSwtm

https://imgur.com/SXZpCcw

Edit - I think I figured out what's going on. In the world map, it's calculating coordinates relative to the top left corner rather than relative to the center. That's why it's more accurate the more zoomed in I am. I just tried zooming all the way in and putting my icon in the top left, and it gave me the correct coordinates when I hovered the cursor over my icon. Does that make sense?

I'm still experiencing this on 1.10.6b for Minecraft 1.16.1, Fabric 0.8.9 build 203, and it makes the world map extremely hard to use. I'm on macOS if that makes a difference. I find it strange that this isn't a more widespread issue. Perhaps it's only affecting macs?

Hullo,

I am having a problem with voxelmap showing waypoints from an older version of a world. To clarify, I play on a mc server that has multiworlds, We;ve just updated to 1.16.3 and the old nether was deleted from the server, and the new one installed. However when I go to the nether now, and look at the map, the new areas Ive uncovered in this new Nether, are overlayed over the old Nether. How can I reset this? Also, when I make a waypoint in this new nether, instead of showing that its in the Nether , its showing that its been saved in EWG Nether, the old one.

Ive tried deleting all the nether waypoints from the .points folder for this server but it hasnt done anything to the map itself.

Id really like to have a brand new nether map with no old map showing

I'm having a weird problem with Voxelmap crashing when I try to change the "worldmap" options in the options screen. I open the worldmap, hit "options," and then click "worldmap" and the game crashes without fail. Error report is here http://ronsoros.github.io/?26f2d42a575ef6e359247a2e26bf467190d36834

Any thoughts? Anyone experiencing the same?

Thanks for your feedback, Robijnvogel. The crash report can be found on Pastebin at https://pastebin.com/raw/fyBTGd7e. The relevant version and system information is below:

Minecraft Version: 1.16.4
Operating System: Windows 10 (64 bit)
Java Version: 1.8.0_51
Memory: 1200707000 bytes (1145 MB) / 1912602624 bytes (1824 MB) up to 2147483648 bytes (2048 MB)
CPU: 12x Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz

Mod Version: fabricmod_VoxelMap-1.10.11_for_1.16.3

Installation method: I installed it by dropping it into the mod folder after I installed Fabric loader and put the API in the mod folder.

Fabric Version: fabric-installer-0.6.1.51

Fabric API Version: fabric-api-0.25.4+1.16

Additional system details can be found in the crash report towards the bottom.

Also, I'm interested in reading your guide on reading crash reports and reporting crashes, but the link is forbidden. Is there any chance you can share an active link to it?

Thanks again for your input.

worldmap (and waypoint) options menu crash fixed for 1.16.4. Might backport to 1.16.3 if needed, but TBH I'd really rather just maintain the current version for each major release of Minecraft. Thanks for the report, dumb error on my part

Thanks!! I appreciate your efforts and all your work.