Tags
Creators
Details
All versions
3.5.0
Release
CompassLocator 3.5.05 months ago 40
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
v3.5.0
◆ Added
- ➕ Added lodestone support for the normal compass — shows the bound lodestone's coordinates and the direction to it
- ➕ Added a separate "Lodestone broken" state with a real block check (lag-free — only in already-loaded chunks)
- ➕ Added the compass.use-lodestone-target option
- ➕ Added the compass.show-last-known-lodestone-when-broken option (show the last known coordinates instead of the "broken" label)
- ➕ Added the compass.format-preset option:
- classic
- compact
- minimal
- ➕ Added the recovery_compass.format-preset option:
- classic
- compact
- minimal
- ➕ Added the recovery_compass.keep-after-death option — the recovery compass is no longer dropped on death
- ➕ Added the messages.lodestone-broken string to the language files (ru / en)
- ➕ Added translatable distance units:
- messages.meters
- messages.kilometers
- messages.unknown
- ➕ Added auto-update for config.yml — new keys are appended while existing settings are preserved
- ➕ Added auto-update for the language files lang/ru.yml and lang/en.yml
◆ Changed
- 🔧 Bumped the plugin version and all configs to 3.5.0
- 🔧 config-version is now automatically synced with the plugin version on startup
- 🔧 Extended the normal compass logic with lodestone handling without losing the old behavior (coordinates, biome, direction, time, world)
- 🔧 The recovery compass and dual-mode now respect the format presets
- 🔧 The recovery compass distance now uses translatable units (m / km)
◆ Fixed
- 🐛 Fixed: after a plugin update the old config.yml was not topped up with new keys (you had to delete the config manually)
- 🐛 Fixed: on an old language file the "Lodestone broken" label was shown in English
- 🐛 Fixed lodestone "broken" detection — Bukkit used to return the stored position even after the block was destroyed, so the "broken" state never triggered
- 🐛 Fixed leftover English strings by moving distance units (m / km / unknown) into the language files
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:kTZ1R8H1:yG5he2VR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kTZ1R8H1:yG5he2VR"
}

