This guide will show you how to add custom additions to PDAPI using datapacks. This is a simple 3 step process. This tutorial assumes you already have a base datapack created and a basic understanding of JSON files and how datapacks work. If not, follow this tutorial to create one.

Within the namespace folder of your datapack, create a new folder named drink_additions. This is where our custom additions will be stored.

Create a new .json file, the name of this will be the id of your addition so choose wisely. Below is the syntax of this .json file. Any of these options can be omitted and the default value will be used. The default values are shown below

{
   "pdapi:caffeine": 0,
   "bartending:alcohol": 0,
   "changesColor": false,
   "color": 0,
   "onDrinkActions": [],
   "weight": 0,
   "name": "Example Name"
}

pdapi:caffeine: The amount of caffeine in the drink (Defaults to 0)

bartending:alcohol: The amount of alcohol in the drink (Defaults to 0) (The Art of Bartending Only)

Note: Other mods can add their own chemicals. These are specified in the file in the same way as caffeine and alcohol.

changesColor: Whether or not the add-in should change the color of the drink it is added to (Default: false)

color: The color to add to the drink when changesColor is true in decimal form. You can use this page to see some decimal color values that Minecraft uses (Default: 0)

onDrinkActions: The actions to perform when drinking something containing this add-in (see next step) (Default: [])

weight: The modification weight of this specific add-in. Higher values are loaded later. Basically, if one datapack specifies a drink addition, lets say namespace:water, and a second datapack also specifies that exact addition (the namespace and filename have to be exactly the same) then the one with the larger weight is used. (Default: 0)

name: The custom name that will be given to the addition. This can be done either in the JSON file or in a resource pack by editing the translations file. The base translation key for drink additions is drink_addition.namespace.name_of_addition_file. If you would like for the tooltip of a drink to show the correct amount of an addition that has been added to a drink, (e.g. - Mocha Syrup x2) then x%1$s must be added to the end of the custom name.

In the 1.20.4 version of the mod caffeine (and other chemicals) are now defined in a specific section of the json file rather than the main part.

{
   "chemicals": {
      "pdapi:caffeine": 0,
      "bartending:alcohol": 0
   },
   [...]
}

This defaults to an empty object, meaning it can be safely left out if you don't want any chemicals in your drink. Any chemicals that aren't specified in this object will default to 0, meaning you only have to specify the ones you want.

{
   "changesColor": true,
   "color": 16711680,
   "name": "Magma Cream x%1$s"
}

Unless you want your add-in to be completely cosmetic, then you should probably add some actions. These are added in the onDrinkActions array in the add-in file. To add an action to your addition, first add a new object to the actions array. In this object, specify the type for the action, as well as any extra options needed depending on the type. Below is a preset list of action templates and their additional options to use. Unlike the base options for a drink addition, all options for an action are required unless specified.

{
   "changesColor": true,
   "color": 16711680,
   "name": "Magma Cream x%1$s",
   "onDrinkActions": [
      {
         "type": "pdapi:apply_status_effect",
         "effect": "minecraft:fire_resistance",
         "duration": 600,
         "amplifier": 1
      }
   ]
}

We are almost done! The last thing we need to do is create a recipe that allows us to add this into a drink using an item. This is done the same way you add any custom recipe to the game in a datapack.

Create a new folder in your namespace called recipes. Then create a new file for the addition recipe. You can name this anything you want, a common name would be [ADDITION NAME]_workstation.json.

Below is the syntax of a Workstation recipe, using our Magma Cream example from earlier.

data/example/recipes/magma_cream_workstation.json

{
   "type": "pdapi:drink_workstation",
   "base": {
      "tag": "pdapi:workstation_drinks"
   },
   "addition": {
      "item": "minecraft:magma_cream"
   },
   "result": "example:magma_cream"
}

In the type option, this should be set to pdapi:drink_workstation

base is the base drink that this item can be added to. This uses the standard Ingredient syntax that most recipes use. To automatically allow any drink to be used as the input, use the tag pdapi:workstation_drinks as shown above, or you can specify a specific item if you only want your ingredient to be able to be added to a single drink, say Brewed Coffee.

addition is the item that results in your addition. For this example, we want to use Magma Cream. This also uses the standard Ingredient syntax.

result is the ID of the resulting addition. This consists of the namespace of your datapack (example in this case) and the filename of the addition data, without the .json (magma_cream in this case).

And just like that, you have created a custom addition that you can add to a drink!