3.4.10
Compatibility
Changes
This release contains a lot of fixes, changes, and a few feature additions. I would HIGHLY recommend upgrading to this verison if you are using any type of SQL storage method.
Changes
- SQLite is now the default storage method for BreweryX. For servers that experience slow saving times with
FlatFilestorage, you should migrate to SQLite, MySQL, or MongoDB. ~ by Nadwey->To migrate, start your server using the storage methodFlatFile. Next, change your storage method toSQLiteor another database storage method. Finally, run:/brew data reloadand/brew data saveto finalize your migration.
Additions
- You can now configure barrel inventory sizes ~ by Mitality
- BreweryX now hooks into the Lands plugin. ~ by Mitality
- You can now configure your own custom translations in BreweryX ~ by Thorinwasher
- Added a Ukranian translation ~ by Thorinwasher
Fixes
- Fixes SQL storage methods not deleting objects from the database. If you're using an older version of BreweryX with an SQL database, you should update! ~ by Jsinco
- Fixes Brewery not recognizing
cauldron.ymlrecipes, reference here ~ by Jsinco
That's it, Github generated release notes are below. Have a good day!
What's Changed
- Set SQLite as the default storage type by @Nadwey in https://github.com/BreweryTeam/BreweryX/pull/96
- Fix: SQL saving, Cauldron brew matching by @Jsinco in https://github.com/BreweryTeam/BreweryX/pull/105
- Fix lore of sealed potions by @Nadwey in https://github.com/BreweryTeam/BreweryX/pull/95
- Allow custom translations by @Thorinwasher in https://github.com/BreweryTeam/BreweryX/pull/103
- Ukrainian translation by @Thorinwasher in https://github.com/BreweryTeam/BreweryX/pull/102
Full Changelog: https://github.com/BreweryTeam/BreweryX/compare/3.4.9...3.4.10
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:gbkMRZcU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvXaGv1n:gbkMRZcU"
}

