Tags
Creators
Details
3.3.0
Compatibility
Changes
What's Changed
Fixes:
- Always try to find namespace for item - ItemsAdder by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/277
- Rework event scheduler - Avoid recursion and performance issues by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/279
- Cauldron brew merging issue by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/280
- Item migrations always setting items - Lectern signal issue by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/285
New features:
- API additions by @Thorinwasher in https://github.com/BreweryTeam/TheBrewingProject/pull/286, https://github.com/BreweryTeam/TheBrewingProject/pull/278, https://github.com/BreweryTeam/TheBrewingProject/pull/289
Full Changelog: https://github.com/BreweryTeam/TheBrewingProject/compare/v3.2.0...v3.3.0
Quote of the day
Can I eat this? @Mitality
A reaction after seing the new proposed Garden plugin icon
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:SyWdreMp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4zxCmDBL:SyWdreMp"
}

