Fixing common WayPoints Mod errors

When a mod misbehaves, the cause is usually simple. This guide covers the most common WayPoints Mod problems and how to fix them, starting with the quickest checks.

The mod does not appear in game

First, confirm the file is actually in .minecraft/mods and that you launched the modded profile, not vanilla. Then check the build matches your exact Minecraft version. A mismatched build simply will not load.

Crash on startup

A startup crash almost always means a version or loader mismatch. Make sure a Forge build is on a Forge profile (and NeoForge on NeoForge), update your loader, and remove any leftover files from other versions. Re-download from the official link if the file may be corrupted.

Waypoints are not showing

Check that the HUD is enabled in the mod settings and that the individual waypoint's visibility is on. Also confirm you are in the same dimension where the waypoint was created — markers are grouped per dimension.

The hotkey does nothing

Another mod may be using the same key. Open Minecraft's Controls or the mod's key settings and rebind the waypoint keys to something free.

Coordinates look wrong in the Nether

This is expected: one Nether block equals eight Overworld blocks. Use the dimension helper rather than comparing raw numbers when lining up portals.

It will not work on a server

Client-side features work on most servers, but some competitive or anti-cheat servers block client mods. Check that server's rules if your markers do not appear.

Still stuck?

Reinstall cleanly: remove the file, re-download the matching build, and add it back. If you are unsure about your version or loader, the download guide walks through choosing the right file.