1.1.0
Compatibility
Changes
Reworked all the menus so they look a lot cleaner and more consistent (spawner info, tiers, library, builder). Item tooltips no longer show the random attribute/enchant clutter.
MySQL/SQLite now use a proper connection pool instead of opening a new connection every time
Save files are written safely so a crash mid-save won't corrupt your data
Fixed ghost spawners that kept spawning after the block was gone (broken without pickup perm, blown up, WorldEdit, etc.)
WorldGuard region checks actually work now, and Vault payments are UUID-based
Fixed a threading issue when saving templates from chat New stuff:
/bspawner clear to wipe all plugin-spawned mobs, plus an optional auto-clear timer
Option to limit one spawner per mob type per chunk
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:ybpu9LUV:K5fOEQl2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ybpu9LUV:K5fOEQl2"
}

