
CoreProtect
CoreProtect is a fast, efficient, data logging and anti-griefing tool. Rollback and restore any amount of damage. Designed with large servers in mind, CoreProtect will record and manage data without impacting your server performance.
Tags
Creators
Details
22.4
Compatibility
Changes
If you enjoy using CoreProtect, please consider supporting the project on Patreon and joining us on Discord.
Patrons receive early access to development builds, as well as other exclusive benefits.
Changelog
- Added thread-safe logPlacement and logRemoval API methods.
- Fixed FAWE changes not being logged when using newer builds (@Telesphoreo).
- Fixed unnecessary database transactions when consumer is empty.
- Fixed obfuscation formatting in item names making tooltips unreadable.
- Fixed occasional NullPointerException while processing hopper transactions.
- Fixed NoSuchMethodError when shooting or dropping arrows in MC 1.20/1.20.1.
- Fixed MysqlDataTruncation error when logging custom skull data.
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:Lu3KuzdV:llmrc4cl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lu3KuzdV:llmrc4cl"
}
