Links
Tags
Creators
Details
All versions
1.0.9
Release
[Let's Do] HerbalBrews 1.0.92 years ago 4,434
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
HerbalBrews 1.0.9
Fixed Issues
Changed / New Features
- TeaKettle: The TeaKettle now features an integrated fluid handler, removing the need for Water Buckets. Additionally, a heat level indicator has been added to improve brewing precision. :stuck_out_tongue: Certain brews, such as coffee, require higher heat levels, while others, like cold brews, require no heat at all. Most of these values can be adjusted via .json.
- Cauldron: The Cauldron has been completely reworked. You can now combine different potions and craft a flask out of them. Flasks, like potions, cannot be stacked. For testing purposes, the default crafting time is set to 1 minute, which can be adjusted in the config. In the final release, the default crafting time will be 5 minutes. Stack size and crafting time are for balancing purposes.
- Jug: The Jug finally has a use! Place it and fill it with up to three different teas or coffees! When consumed, you will receive all effects from the drinks inside. Effects last 45 seconds and are configurable.
- TopHat: The TopHat has a new model – it’s now a proper top hat!
- Witch Hat & TopHat: Reduce magical damage by 40% – configurable.
- Teas: are now placeable as TeaSets. Purely decorative though.
- Various texture improvements.
- Added a configuration file.
- Effects slightly reworked All effects will be shared with nearby players. However, the more players there are, the weaker the effect.
- Advancements slightly reworked.
- DoAPI has been removed as a dependency. Farewell!
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:Eh11TaTm:mB0qbjB5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Eh11TaTm:mB0qbjB5"
}![[Let's Do] HerbalBrews](https://cdn.modrinth.com/data/Eh11TaTm/cea48ad39e9323e9e0f5354ee1d4c160f46b50be_96.webp)

