Tags
Creators
Details
3.0.0
Compatibility
Changes
Warning
This is a major release, it breaks parts of the plugin API. OTHER PLUGINS INTEGRATING WITH THE TBP API MIGHT EXPERIENCE ISSUES
NOTE The plugin has backwards compatibility, but configuration files are irreversibly modified, TAKE A BACKUP!
What's Changed
- Feature: Cauldron particle configuration by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/232
- Feature: Folia compatibility by @Thorinwasher and @RitaSister in https://github.com/BreweryTeam/TheBrewingProject/pull/196
- Feature: Customizable barrel types and matchers by @Thorinwasher in #190
Full Changelog: https://github.com/BreweryTeam/TheBrewingProject/compare/v2.10.2...v3.0.0
Quote of the day
Next patch will be 2.11
šŗ1984š„¢(discord name)
You are once again wrong, you need to up your prediction game.
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:4zxCmDBL:QAeZjVLy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4zxCmDBL:QAeZjVLy"
}

