Tags
Creators
Details
1.0.1
Compatibility
Changes
A critical issue has been fixed: the management menu (accessed via RMB and Shift+RMB) will now correctly remain closed if all core features are disabled in the config (player-teleportation, inventory-inspection, punishment-system), restoring the behavior from the initial release.
- Fixed: The admin menu will no longer open if all systems (teleportation, inventory inspection, punishment) are disabled in the configuration file.
- Improved: Numerical ID search functionality has been enhanced for better accuracy and speed.
- Ban Status: The GUI now correctly propagates ban status updates. If a player is unbanned via a direct command, the menu will now accurately reflect their unbanned status.
- Head Caching: Player head/skin caching has been implemented. This feature is now active but may exhibit unstable behavior (experimental).
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:ml6KtwQF:7W2OTwWD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ml6KtwQF:7W2OTwWD"
}

