v2.0
Compatibility
Changes
BeansClear - Super Update:
-
New flag (beans-clear)
-
New flag (beans-allow-block-break / beans-allow-block-place) Now you can add which block or entity you want to break or place inside a region, it is a feature that many needed.
-
Cache: If the server is restarted, any blocks or entities that were placed before the restart will be removed.
-
New config Worldguard: false/true (The plugin now works without relying on WorldGuard. If you want BeansClear to work on all your worlds, set this configuration line to false.)
-
New config:
all-blocks: enabled: false time: 5 #IN SECONDS
all-entities: enabled: false time: 5 #IN SECONDS
(You will now be able to select all the blocks or entities in the game, without having to manually add them line by line.)
WARNING: Delete the old beansclear folder to get the new features, as beansclear still retains the core features.
Optional dependencies
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:KPntq1pU:YWPBsT9r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KPntq1pU:YWPBsT9r"
}

