Tags
Creators
Details
1.0.1+1.20.6
Compatibility
Required content
Changes
Note about this release: Any drinks with additions will lose all of their addition data when coming from 1.20.4 or below because of Minecraft's introduction of the Item Component system. Specialty Drinks will also lose their data and will become
Uncraftable Drinks
Additions
- Translations for Tags added
Changes
- Updated to 1.20.5 and 1.20.6 (Crying rn pain and suffering that was)
- The Drink Addition and Specialty Drink system has been moved over to custom Item Components (more info below)
- Just like Recipes have in this version,
OnDrinkSerializers andSpecialtyDrinkSerializers now useStreamCodecs to serialize packets
Drink Components
Pre-2.0.1 (1.20.4 and below), Drink data (Additions, Coffee Type, etc.) was stored in a CompoundTag under the key DrinkData. In here there were elements like Additions, a ListTag containing the IDs of the Additions added, or in Pluto's Coffee there was CoffeeType in brewed coffee which stored the Roast of coffee.
Drink Data has been split into several different components. Drink Additions use the pdapi:additions component, and Coffee Types in Pluto's Coffee use the plutoscoffee:coffee_type component.
Basically, if you wanted to give yourself an item with preset additions, here's the difference between versions
1.20.4 and below
/give @s pdapi:example_drink{DrinkData:{Additions:["pdapi:ice","pdapi:milk","pdapi:sugar"]}}
1.20.5 and above
/give @s pdapi:example_drink["pdapi:additions":["pdapi:ice","pdapi:milk","pdapi:sugar"]]
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| PlutosDrinksAPI-1.20.6+2.0.1-sources.jar | Unknown | 98.46 KiB |
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:3frUAX4S:Wbiz2thq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3frUAX4S:Wbiz2thq"
}

