Tags
Creators
Details
1.1.3
Compatibility
Changes
We are happy to announce that we are continuing development of this plugin. We are fixing our old code as well as adding new features to the plugin while keeping its performance stable. We will be releasing new versions with more features packed as fast as we can. Lookout for DEV builds soon!
- Neptune Development
Bug Fixes
- Fixed
/ploggercommand showing Bukkit color codes instead of formatting them. - Recoded the
DatabaseManager.javafile with prepared statements to prevent any errors in the SQL Code. - Removed unnecessary
replace()methods and added a global placeholder instead. - Some minor code changes. Look at the commit here
Additions
- Added an Boolean in the config named
use-bstatsto toggle bStats. It will be enabled by default.
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:MQe5E2XE:lUKGbuJK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MQe5E2XE:lUKGbuJK"
}

