Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 2 months ago
All versions
1.0.1
Release
SpyHunt-Compass 1.0.12 months ago 70
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Spigot
Changes
[1.0.1] - 2026-09-04
🚀 New Features & Enhancements
- SMP Admin-Only Config Controls: Added
config.ymlwithadmin-only,admin-only-track, andadmin-only-trackertoggles so SMP server owners can restrict/trackand compass acquisition to staff/admins. - Configurable Messages: Fully customizable in-game messages and chat prefixes via
config.yml. - Dynamic Compass Lore: Compasses now visually display the currently tracked player's name and total target count directly in the item lore.
- Offline Target Removal:
/tracker remove <player>now searches the compass's stored target UUIDs to remove players even if they are offline. - Self-Tracking Prevention: Players can no longer track themselves, preventing erratic needle spinning.
- Formal Permission Nodes: Registered
spyhuntcompass.track,spyhuntcompass.tracker,spyhuntcompass.use, andspyhuntcompass.admininplugin.yml.
🐛 Bug Fixes & Optimization
- Fixed Dimension Portal Precedence: When a target enters another dimension, portal coordinates now take precedence over stale
lastSeenworld coordinates. - Fixed Target Cycling Lodestone Glitch: Compass needle updates immediately when cycling between two nearby targets by tracking previous target UUID.
- Fixed Block-Mining Chat Spam: Left-clicking blocks while holding a compass now has an interaction debounce to prevent spamming chat when breaking blocks.
- Eliminated Memory Leaks: Added
PlayerQuitEventcleanup to clear cached tracker state when players disconnect, and proper cleanup duringonDisable(). - Codebase Deduplication: Centralized
getOrGiveCompasslogic inCompassManageracross both/trackand/tracker.
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:qBluMYG3:zmuSr9LC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qBluMYG3:zmuSr9LC"
}

