Tags
Creators
Details
2.0.0.0+fabric
Compatibility
Required content
Changes
MinerTrack 2.0.0.0 is officially released! 🚀
This is the biggest update since the inception of the MinerTrack project! I have invested significant time and effort into a thorough refactoring and optimization to deliver a better experience. I hope you enjoy this update!
Support the Project MinerTrack has not received any donations in the past year, and the number of GitHub Stars remains low. Your support is my greatest motivation to continue development! If you appreciate this project, please consider supporting me via:
- Subscribing on Patreon: https://patreon.com/Author87668/join
- Starring the repository on GitHub: https://github.com/At87668/MinerTrack
Thank you so much to every supporter! ❤️
What's News
Code Refactoring
- Optimized the original Bukkit-only structure into a platform-agnostic core with a lightweight platform loader, facilitating easier multi-platform expansion.
- Completely rewrote legacy code to improve performance.
Configuration Optimization
- Migrated configuration naming conventions from Bukkit-specific standards to general Minecraft standards for better multi-platform compatibility.
⚠️ Breaking Change: If you are upgrading from v1, you must reconfigure your settings after the update!
Detection Optimization
- Introduced new reference parameters to reduce false postive.
Update Checker Optimization
- Now checking for version updates by platform.
Fabric Support
Version Compatibility
- Now supports Fabric for Minecraft 1.18+.
Mod Compatibility
- Now supports worlds and blocks added by mods. (Effective only in the Mod version)
Permission Node Support
- Integrated LuckPerms-compatible permission API to support permission nodes on Fabric.
Bug Fixes
- Fixed an issue where the
/mtrack resetcommand failed to correctly reset VL on Fabric. - Fixed an issue where bypass permissions were not applied correctly.
- Fixed an issue where the update checker ran on the Fabric main thread, causing server lag.
- Fixed compatibility issues preventing operation on Fabric versions 1.18–1.21.11.
- Fixed the issue where the updater didn't differentiate between channels.
Note: If you are upgrading from v1, you must reconfigure your settings after the update!
Enjoy~
Optional dependencies
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:O3VQnhG2:iNoFcR1q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O3VQnhG2:iNoFcR1q"
}


