Tags
Creators
Details
All versions
3.5.1
Release
CompassLocator 3.5.14 months ago 56
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.6–1.21.11
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v3.5.1
◆ Added
- ➕ Added support for Minecraft 26.2
- ➕ Added the
recovery_compass.persist-deathsoption — death points are saved todeaths.ymland survive a server restart - ➕ Added cross-platform
keep-after-death— the recovery compass is now kept on death on Spigot too, not only Paper
◆ Changed
- 🔧 Bumped the plugin version and all configs to 3.5.1
- 🔧 Migrated the action bar from the deprecated BungeeCord chat API to Adventure (
sendActionBar(Component)); legacy§color codes still work - 🔧 Plugin version is now read via
getPluginMeta().getVersion()with a safe fallback for older cores - 🔧
PlayerMoveEventnow refreshes the action bar only on block-coordinate changes instead of every movement (including head rotation) — far fewer packets - 🔧 Inventory events (
InventoryClickEvent/InventoryDragEvent) now trigger a state recalculation only when a compass is actually involved (hand / slot / cursor), not on every click in any chest - 🔧
keep-after-deathnow uses pure Bukkit API (items removed from drops and restored on respawn) instead of the Paper-onlygetItemsToKeep()
◆ Fixed
- 🐛 Fixed an NPE that crashed the recovery compass every tick when the death world was unloaded or deleted —
getWorldName(...)is now null-safe and returns "Unknown" - 🐛 Fixed a crash on malformed format strings —
distance-format/time-formatsnow run through a guardedsafeFormat(...)that warns instead of throwing - 🐛 Fixed the locator bar flickering for all players whenever someone equipped/unequipped a compass —
ensureWorldLocatorBarEnabled()no longer re-appliessetGameRule(LOCATOR_BAR, true)on every refresh (re-setting it broadcast a packet to every client in the world)
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:rHzZNmku"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kTZ1R8H1:rHzZNmku"
}

