Tags
Creators
Details
3.4.5
Compatibility
Changes
BreweryX - v3.4.5
This update doesn't contain any new gameplay features. Most changes in this version are additions to BreweryX's addon API or bug fixes.
- BreweryX storage internals changed a bit and opened more of them up for the addon API
- Addons now enable after the DataManager has finished loading
- Fixed a few errors in the
MongoDBstorage type - Fixed BreweryX not initializing Barrel bounds in async regions (#70)
- Fixed BreweryX failing to startup due to duplicate-key stream exceptions (#68)
- Fixed
BreweryPluginItem potions not being recognized. Brewery will now only recognize brews from itself if you're using the proper config identifier of the recipe. (e.g.brewery:wheatbeer,brewery:ex). See the default config to take a look at how these recipes are defined. - Fixed a few typos in en.yml by @Vutka1
- A few other misc changes and additions
Full Changelog: https://github.com/BreweryTeam/BreweryX/compare/3.4.4...3.4.5
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:gvXaGv1n:oTKyYM4O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvXaGv1n:oTKyYM4O"
}

