(1.12) Loot Table Primer

Overview

All champions get their drops from a single loot table if the loot table is enabled for use from the config file. This means that users can utilize customization mods such as LootTweaker to edit the loot table, or any other methods that can hook into or replace the existing loot table.

This primer is meant to introduce users to all the information they may need to know about the loot table itself to facilitate any sort of external customizations they wish to make.

Loot Table Source

The source pools for the loot table is located over here.

Entity Property

Champions utilizes a custom entity property in the loot table. The code for this property is located here. You can see an example of its usage in the loot table itself.

Template JSON:

{
  "condition": "entity_properties",
  "entity": "this",
  "properties": {
    "champions:is_champion": {
      "tier": 0,
      "min_tier": 0,
      "max_tier": 0
    }
  }
}

Note that all of the property fields (tier, min_tier, max_tier) are optional. If left out, they will just default to 0 and be ignored.

You'll see that there are three property fields.

1. tier - Specifies the exact tier of the champion's rank. If set to 0 or left out, all tiers will be applied within the constraints of the min_tier and max_tier fields, if either of them exist. If set to a non-zero positive integer, the other fields will be ignored.

2. min_tier - Specifies the minimum tier needed by the champion's rank. If set to 0 or left out, there will be no minimum.

3. max_tier - Specifies the maximum tier needed by the champion's rank. If set to 0 or left out, there will be no maximum.

Leaving out all of these fields is a valid configuration and will result in the loot being dropped by all champions.