1.0.1
Compatibility
Changes
๐ v1.0.1 - The "Permission Logic" Hotfix
This is a critical update that addresses a missing permission check for the base command.
๐ง Fixed:
- Permission Implementation: Fixed a bug where
f0ring.usewas defined in the documentation but not actually checked in the code. - Access Control: Players without the
f0ring.usenode will now correctly be prevented from opening the GUI. - Security: Ensured that only authorized players can access the cosmetic menu.
Why update? Without this fix, every player on your server could access the menu regardless of their rank. Update to v1.0.1 to regain control over your server's cosmetics!
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:aW05oo9Y:5BasaYVi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aW05oo9Y:5BasaYVi"
}

