Datapack Tier Lists

A tier list can be bundled with a datapack for easier distribution. This is useful if you want to combine custom advancements, scoreboards, or other functionality to share it as a single datapack zip.

You can copy a tier list directly from the tier list editor into data / <namespace> / yet-another-minecraft-bingo / tierlists / <name>.tierlist.json, or create the file manually:

{
  "S": [],
  "A": [],
  "B": [],
  "C": [],
  "D": [],
  "groups": [],
  "requirements": {}
}

Each objective in the list can refer to an item, an advancement, or a custom objective ID.

For example, "minecraft:stone" will resolve to the stone item, whereas "minecraft:story/mine_stone" is an advancement.

Additionally, item tags can be used to substitute multiple items into the same list; e.g. "#minecraft:leaves".

Groups

Tier list "groups" are intended as a way to prevent similar or conflicting objectives from appearing on the same card.

This also weights the list as a whole rather than the individual objectives when generating a card, so that they don't appear any more frequently than other individual items.

Given the amount of variations of copper, cut copper, oxidized copper slabs, waxed lightly weathered cut copper stairs... if all of those were included in a list without placing them in a group, you would be guaranteed to get an entire card of copper variants on most rolls.

  "groups": [
    [
      "minecraft:copper_block",
      "minecraft:cut_copper",
      "minecraft:exposed_cut_copper",
      ...
    ]
  ]

INFO

Objectives in the same group can be placed on different tiers. It will also pick up items that are nested in custom objectives - e.g. if a "one_of" objective includes a "minecraft:copper_block".

While groups behave similarly to the "conflictsWith" property on custom objectives, note that "conflictsWith" does not affect the weighting of the list.

Requirements

Some tier lists might not work with all the possible game settings, especially when using scoreboards & datapack functions to write your own logic.

For example, opponent-based objectives usually aren't completable if there is only one team.

To solve this, you can use "requirements" to specify which settings your list needs. The mod will then warn players starting a game when the requirements aren't met.

  "requirements": {
    // Min/max number of teams needed to start the game
    "minTeams": 2,
    "maxTeams": 4,
    // Min/max number of players that must be on each team
    "minPlayersPerTeam": 1,
    "maxPlayersPerTeam": 8,
    // Require that certain objectives are successfully resolved
    // - by default, the mod ignores any missing objectives (such as modded items or custom advancements)
    "objectives": ["minecraft:copper_bulb"],
    // Require that only the default bingo teams are used
    // (bingo_red, bingo_pink, bingo_blue, ...)
    // This will prevent players from setting up their own teams when the feature is introduced -> https://gitlab.com/horrific-tweaks/bingo/-/issues/33
    "onlyDefaultTeams": true,
    // Require specific game options to be set.
    // Any value from game-options.json can be used here.
    "options": {
      "isLockoutMode": false,
      "isPvpEnabled": true
    }
  }