Tags
Creators
Details
Licensed MIT
Published 11 months ago
Updated 9 months ago
All versions
1.2
Release
Fungi Delight 1.211 months ago 806
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Effects and mechanics:
- Added "Weak Stomach" effect: A new mechanic where consuming Inky Caps (or compatible foods) makes the player intolerant to alcohol, configurable items and potions. If the player consume of these, they would trigger a bad reaction (Nausea, Poison, Weakness).
- Implemented undefined`fungidelight:alcohol_reaction` undefinedtag: Foods in this tag apply the Weak Stomach effect.
- Added a warning tooltip to items that causes Weak Stomach.
- Implemented `#forge:alcohol` tag: Defines drinks that trigger negative reactions.
- Added Configuration options:
- Toggle for Weak Stomach mechanic.
- Configurable whitelist for items that trigger the reaction.
Mod Compatibility:
- Added AlcoCraft+, Brewin' and Chewin', Create: Winery, [Let's Do] Brewery, [Let's Do] Vinery, OkayPy's Alcohol Mods compatibilities.
- Added `fruitsdelight` compatibility: Durian items now trigger the alcohol reaction.
- Added `environmental` compatibility: Added support for Buried Truffles.
- Refactored Recipes and AI Goals to use Tags:
- Recipes now accept generic `#forge:mushrooms/truffle`, `#morel`, and `#inky_cap` tags.
- Mob AI (Pigs/Cows) now detects blocks via tags for better mod integration.
Balancing & Adjustments:
- Buffed Inky Cap foods: Improved stats and effects to compensate for the toxicity risk.
- Buffed Truffle foods: Increased saturation and adjusted cutting board output.
- Fixed Inky Cap Salad having incorrectly high saturation.
Fixes:
- Fixed no potions related items showing up or being craftable.
- Renamed cleaned mushroom cap to cleaned inky cap.
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:fHzhaX3z:ZqzTHI54"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fHzhaX3z:ZqzTHI54"
}

