Tags
Creators
Details
1.0.4
Compatibility
Changes
Hereafter, LibertyBans supports the Sponge platform, API versions 8 and above. This development, we hope, will extend the usability of LibertyBans. Deployable in many varieties of environments yet utilizing common code, LibertyBans has always been designed to support multiple platforms. The Sponge API is the natural continuation of this impetus.
Moreover, we have solved, by a clever exploit, the longstanding issue which made LibertyBans vulnerable to bugs in other plugins. Specifically, unrelocated libraries in other plugins will no longer affect LibertyBans. We will continue to recommend you to fix these bugs, because your server's stability is our concern too. However, LibertyBans will be able to proceed despite these situations.
Bugs fixed:
- Fixed an embarrasing bug which caused importing from BanManager to be impossible, since
/libertybans import banmanagerwas not recognized - Updated database revision per previous change in 1.0.3
Feature additions:
- Sponge support. API 8 and API 9 are supported
- The checkuser addon provides the
/checkusercommand, thanks to SnakeAmazing. This addon displays whether a user has an applicable ban or mute - The
LibertyBans/internal/attachmentsfolder allows attaching driver jars, which is useful for importing from LiteBans H2
Other:
- Protect classloading from unrelocated libraries, by filtering classes requested in parent classloader
- The
hypersql/andlibraries/folders are moved underLibertyBans/internal. Existing directories will be migrated automatically
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:PgXAUxLZ:fjs9xEtO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PgXAUxLZ:fjs9xEtO"
}
