Tags
Creators
Details
1.4.0-beta.2+fabric
Compatibility
Required content
Changes
Drink Beer Refill 1.4.0-beta.2
This release migrates the project to a native Fabric and NeoForge multi-loader layout for Minecraft 1.21.1. It does not depend on Architectury Loom, Architectury Gradle Plugin, or Architectury API.
Added
- Added a Fabric 0.19.3 build with Fabric API 0.116.12+1.21.1 and Fabric Loom 1.14.10.
- Added Fabric implementations for registration, extended menus, C2S networking, Transfer API inventory automation, client registration, and per-world JSON configuration.
- Added shared registry-ID snapshots, loader-specific configuration tests, and five shared Holiday GameTests with thin Fabric and NeoForge discovery adapters.
- Added CI and publishing tasks that build, test, and publish separate Fabric and NeoForge artifacts.
Changed
- Split the project into
common,fabric, andneoforgemodules. Each loader compiles the shared sources in its own toolchain; no common JAR is embedded or published. - Moved shared gameplay to vanilla APIs behind small platform and client hooks. NeoForge retains deferred registration and capabilities; Fabric uses direct registration and Transfer API storage.
- Replaced loader-specific inventory and menu primitives in shared code with vanilla containers and slots while preserving all automation directions and restrictions.
- Kept Minecraft 1.21.1, Java 21, NeoForge 21.1.244, ModDevGradle 2.0.143, NeoForm
1.21.1-20240808.144430, Parchment2024.11.17, and JEI 19.21.0.246. - Fabric now stores server settings in
<world>/serverconfig/drinkbeer-server.json; NeoForge continues to usedrinkbeer-server.tomlwith matching fields, defaults, and ranges.
Fixed
- Fixed transparent planes on the holiday stars and colored lights rendering as black on Fabric by registering their cutout render layer.
Compatibility
- Preserved registry IDs, resource paths, NBT and codec formats, including the existing
drinkbeer:refreash_tradeboxpayload ID. - Verified both dedicated-server GameTest suites and loading NeoForge-created test worlds on Fabric and Fabric-created test worlds on NeoForge.
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:Ji4ut6NY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RZwVw5iA:Ji4ut6NY"
}

