Tags
Creators
Details
stable-1.6.1
Compatibility
Changes
Hello, in this version I added a new hotfix!
first, there was an GUI Conflict so, I created an new holder for the GUI´s, so the GUI´s wont get any conflict with another plugin.
Also, when I added the feature of antidupe or glitch abuse for the GUI´s, i fourcefully wrote it so if there is an GUI, that have the purpouse of helping (managment GUi´s, warps, crate edits, etc.), it activates, but now its only for the plugin itself, so it wont afect any other plugin! (thanks to the holder change btw)
This is more stable, i fixed a few bugs (messed up code :d), so its more stable and efficent than before.
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:9u4kWL9m:ZicBobYM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9u4kWL9m:ZicBobYM"
}

