Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 2 months ago
All versions
1.0.0
Release
SpyHunt-Compass 1.0.09 months ago 119
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Spigot
Changes
SpyHunt-Compass v1.0.0 Changelog
SpyHunt-Compass is a standalone version of the tracking compass feature from the SpyHunts plugin, designed for general survival or manhunt scenarios.
🌟 Key Features
🧭 Smart Tracking Compass
- Live Tracking: Points to the target player's location in real-time.
- Auto-Refresh: Compass target updates automatically every second (no need to click).
- Cross-Dimension Support:
- Overworld: Tracks live location.
- Nether/End: Tracks the last known location (portal) where the target entered the dimension if the tracker is in a different dimension.
- Smart Recovery: If target is offline or in a different world without portal data, points to their last seen location in the current world.
🎮 Commands & Usage
- /track <player>: Instantly get a compass tracking a specific player (clears other targets).
- /tracker: Get an empty tracker compass.
- /tracker add <player>: Add a player to your tracking list (cycle targets with Right-Click).
- /tracker remove <player>: Remove a player from your tracking list.
- /tracker help: View all available commands.
🛠️ Usability Improvements
- Tab Completion:
- Smart suggestions for commands.
- Privacy: Player names are HIDDEN from tab completion when using
/tracker addor/tracker remove.
- Inventory Management: Automatically gives a compass if you don't have one; updates the existing one if you do.
- Multi-Target: Supports multiple targets on one compass; cycle through them by Right-Clicking.
Developed by SpyGamingOG
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:reJ0mUh8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qBluMYG3:reJ0mUh8"
}

