Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 2 weeks ago
All versions
1.4.1+neoforge
Beta
Drink Beer Refill 1.4.1 for 1.21.1 (NeoForge)2 weeks ago 1,667
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Drink Beer Refill 1.4.1
This version is preparation for mod cross-mod compat.
Added
- Added tank-only source and flowing fluids for all nine base beers, with one mug equal to 250 mB.
- Added standard Fabric Transfer API and NeoForge fluid-item capabilities for draining and filling beer mugs.
- Added per-beer fluid tags, the aggregate
#drinkbeer:beerstag, localized fluid names, and cross-loader regression coverage. - Added an optional NeoForge Create milk-sprite atlas pack that contains metadata only and activates only when both external Create textures exist.
Fixed
- Fixed Create 6.0.x JEI Spout pages showing 1000 mB for beer mugs that actually accept 250 mB, without adding duplicate filling recipes.
Compatibility
- Beer fluids are non-placeable and have no buckets. Create is optional; NeoForge creamy beers reference its milk textures only when both files are available, while Fabric and all fallback paths use vanilla water textures.
- The Create/JEI display patch is optional, client-only, limited to DrinkBeer fluids, and fails closed if Create changes the targeted method.
- Mixed beer remains item-only so its base-beer and spice components are never discarded by fluid conversion.
- Beer barrels keep their existing mug-based production and are not converted into fluid tanks.
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:RZwVw5iA:VnFS8aUY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RZwVw5iA:VnFS8aUY"
}

