Minecraft Forums

Update 20.3.1.1 (MC 1.15.2, 1.14.4):

* Fixed "core mod" part of the mod not fully working outside of my dev environment, which caused chunks to not update with new block changes.
* Fixed compatibility with Better Respawns and other similar mods.

Link Removed

Update 20.4.0 (MC 1.15.2, 1.14.4, 1.12.2, 1.12.1, 1.12, 1.8.9, 1.7.10):

+ Added a new option to show entity name tags under the minimap dots (for those that have a name tag).
* (1.15.2) Fixed the first 2 characters in player names on the minimap having weird shadows.
* (1.8.9 to 1.12.2) Fixed compatibility with Better Respawns and other similar mods.
* Fixed the empty text line under the minimap when the first word in the biome name doesn't fit in the minimap width.
* Fixed the location of the waypoints folder being affected by whether the game config folder is a symlink or not, even though it's not located in the config folder.

Link Removed

Update 20.4.0.1 (MC 1.15.2, 1.14.4):

* Fixed the "Reset Defaults" button placement.

Link Removed

Quote from Quavelen»

Hey Xaero, I'd like to ask - is automatically resetting all keybinds to default every time I update the minimap intentional, or a bug? I've been meaning to ask about it, but I kept forgetting because it only happens when I update lol. It's not a huge bother, just a minor annoyance.

Ummm. It's not intentional but does it even happen? Key bindings are not stored in the jar file, so I don't see how it would happen. Forge is responsible for this, btw.

Quote from Quavelen»

Hmm... I wrongly assumed it was your mod, then. I wonder why Forge resets it. Any ideas why?

Also I do know the key bindings are stored outside the jar file; I've manually replaced it before when they get reset. I just assumed that for some reason your mod overwrote existing keybinds every time I updated to a new version. If it's forge's fault, that makes it more confusing to me since I haven't updated that for a good week.

Oh well. It's not a serious issue, and I'm fine with having to rebind them.

Do you just replace the jar when you update?

Quote from Quavelen»

Not exactly, but yeah.

I delete the old jar, and then drop the new one in. With this last update I updated Forge from 31.1.14 to 31.1.16, and your minimap mod from 20.4.0 to 20.0.4.1; the keybinds were kept. So, maybe whatever was causing it in Forge is resolved now.

Alright. I don't see anything in the changelogs, so I can't confirm.

Update 20.5.0 (MC 1.15.2, 1.14.4, 1.12.2, 1.12.1, 1.12, 1.8.9, 1.7.10):

+ Added a new option to control the alignment of the info text under/above the minimap.
+ Added a new option to display current yaw and pitch angles of the view.
* Reordered some minimap options.

Link Removed

The fair-play version of the mod is now also updated to 20.5.0 (see previous changelog)!

Link Removed

Update 20.5.1 (MC 1.15.2, 1.14.4, 1.12.2, 1.12.1, 1.12, 1.8.9, 1.7.10):

* Reworked some controls handling. Any mouse buttons can now be used for the mod key bindings and pressing a key/button very quickly should no longer call the "key down" and "key up" events in the same frame, which fixes some bugs.
* If you have the world map mod installed, the waypoints menu and world map waypoints will now keep working even if you disable on-minimap, ingame and death waypoints.
* Fixed deathpoints not turning into regular waypoints when renamed.
+ Added tooltips to more minimap settings.

Link Removed

The fair-play version of the mod is now also updated to 20.5.1 (see previous changelog)!

Link Removed

Update 20.5.2 (MC 1.15.2, 1.14.4, 1.12.2, 1.12.1, 1.12, 1.8.9, 1.7.10):

* Added support for Xaero's World Map 1.5.6. Not compatible with older versions.
* (1.14.4, 1.15.2) Fixed GL Error spam under certain conditions when you have key bindings set to nothing.

Link Removed

The fair-play version of the mod is now also updated to 20.5.2 (see previous changelog)!

Link Removed

Update 20.6.0 (MC 1.15.2, 1.14.4, 1.12.2, 1.12.1, 1.12, 1.8.9, 1.7.10):

+ Added compatibility with the waypoints sharing format that will be used in the future (after enough people get at least this version of the mod). The format change is needed for compatibility with text formatting from FTB Utilities + similar mods.
+ Added a simple API for adding/removing custom waypoints with your own mod. This was requested for a specific use case but everyone will have access to it.
Use xaero.common.minimap.waypoints.WaypointsManager.getCustomWaypoints(String modName) to get your own waypoints table for your "modName".
Use constructor xaero.common.minimap.waypoints.Waypoint(int x, int y, int z, String name, String symbol, int colorId (0 - 15)) to create new waypoints that you can add to your table.
* Fixed waypoints sharing not working properly when the share message has text formatting. For example, when the waypoint name looks like a link, there is automatic formatting applied, which broke stuff.
* (1.12.2 and below) Fixed adding shared waypoints not working at all.
* (1.12.2 and below) Fixed the mod options limit. Was causing issues in Better PVP but would affect the minimap mod in the future.

Link Removed

The fair-play version of the mod is now also updated to 20.6.0 (see previous changelog)!

Link Removed

Quote from Quavelen»

Hey Xaero, I guess I need to bug you about something. I'm not 100% certain your minimap is actually causing this, but since the crash report is pointing the finger of blame at it, I realised I should ask about it anyways.

Today, I decided to try an open source project called "OptiForge", which aims to add Forge support to OptiFine's 1.15.2 previews. However when using your minimap in tandem with this, it crashes as soon as I attempt to open the debug menu (F3). Obviously your minimap functions flawlessly without this.

Here is the crash report: https://pastebin.com/ijqAwnhF

Here is the issue I opened on OptiForge GitHub: https://github.com/ZekerZhayard/OptiForge/issues/9

More information can be seen there, in that issue. Hopefully it's not something you need to fix, but I'm letting you know just in case.

Thanks for reporting! I have already received a report for this but I appreciate it either way. It's a compatibility issue in the world map mod and I'll fix it in a future update.