26.1.2 ‐ 26.2

A guide about adding Resource Slime variants

The variant itself

To add a new slime variant to the game inluding the resource slime ball, slime itself and it's bucketed version, create a file under
<pack name>/data/<pack_namespace>/resourcefulslimes/slime_variant/<your_variant_name>.json
Note that unlike vanilla, NeoForge registries use additional mod namespace after the pack's.

The file contains just two fileds:

• "name" - It's for code purposes and should be the same as file name. It's used e.g. to display custom tooltips under resource slimealls.
• "tint" - A decimal representation of RGB color code used to tint the slime variant and items related to it.

An example file content used to create the cobblestone variant below:

{
  "name": "cobblestone",
  "tint": 8947592
}

To overwrite an existing variant place your file under
<pack name>/data/resourcefulslimes/resourcefulslimes/slime_variant/<existing_variant_name>.json
which follows the same schema.

This is it, you added your slime variant to the game! Continue reading to learn how to add a way to obtain it and make use of it's resource slimeballs.

The way to convert the slimeballs

As you added your slime variant to the game, you could've noticed it's slimeballs can't be processed by the slime sieve. That's why you need to add a sieving recipe too.

Sieving is considered a standard recipe and every file for it should be placed under
<pack name>/data/<pack_namespace>/recipe/<result_resource_name>_from_sieving.json or
<pack name>/data/resourcefulslimes/recipe/<existing_resurce_name>_from_sieving.json to overwrite existing entries.
Remember to suffix every file name with "_from_sieving" to avoid recipe conflicts.

The file should contain following fields:

• "type" - Default header for all recipes. In this case should always be set to "resourcefulslimes:sieving".
• "chance" - The chance that determinates if output should appear or be lost. 1.0 is guaranteed success, while 0.0 is no output at all.
• "required_variant" - The variant of the slimeball or the one you've added. Should follow the <pack_namespace>:<variant_file_name> schema or
  "resourcefulslimes:<existing_variant_name>" if you're overwriting an existing entry.
• "result" - An ItemStackTemplate providing the resulting resource.
• "ticks" - Amount of Minecraft ticks it takes to process the slimeball by a basic sieve. It's 400 for all default recipes of this kind.

Example file for cobblestone variant found below:

{
  "type": "resourcefulslimes:sieving",
  "chance": 1.0,
  "required_variant": "resourcefulslimes:cobblestone",
  "result": {
    "id": "minecraft:cobblestone"
  },
  "ticks": 400
}

The way to obtain the slime

There is the variant and the gain from it, now it needs to be obtainable. Slime creation recipes used by the Slime Lab although very different from vanilla recipes also go to the same folder.

The file name should follow the "<variant_file_name>_slime>" naming and contain following fields:

• "type" - Common to all recipes. In this case should always be "resourcefulslimes:slime_creation".
• "ingredients" - A List of SizedIngredients conatining from 1 to 3 entries, specifying item IDs and counts. Those are items used by the Slime Lab.
• "output_variant" - Looking like <pack_namespace>:<variant_file_name>, this is the variant of Resource Slime that should be produced.

The legendary cobblestone example below:

{
  "type": "resourcefulslimes:slime_creation",
  "ingredients": [
    {
      "count": 1,
      "ingredient": "minecraft:slime_block"
    },
    {
      "count": 64,
      "ingredient": "minecraft:cobblestone"
    }
  ],
  "output_variant": "resourcefulslimes:cobblestone"
}