Tier, Block, Mob, and Crate Engine

Unlimited tier definitions

Tiers are stored under tiers in config/tiers.yml. Keys must be positive and unique. The ten included tiers are defaults rather than a hard limit: administrators may add, remove, or rebalance tiers. Runtime ordering follows required-breaks, not YAML key order, and the first tier must start at zero.

tiers:
  '11':
    name: '&dCrystal Depths'
    required-breaks: 50000
    blocks:
      - 'STONE:60'
      - 'AMETHYST_BLOCK:30'
      - 'DIAMOND_ORE:10'

Normalized selection weights

Weights are relative values, not required percentages:

effective chance = entry weight / sum of all positive weights

STONE:50 and DIAMOND_ORE:150 total 200, producing effective chances of 25% and 75%. Decimal weights, including values such as 0.00003, are supported. Zero or negative entries do not contribute to selection.

Mob events

mobs:
  enabled: true
  chance: 2.5
  entries:
    - 'ZOMBIE:70'
    - 'SKELETON:30'

chance is evaluated for each valid OneBlock break. If it succeeds, the entity is selected from its own normalized pool and spawned at the exact center. Island mob limits can prevent new spawning.

Equipment is assigned by entity and slot. Supported slots include HEAD, CHEST, LEGS, FEET, HAND, and OFF_HAND. drop-chance controls the equipment drop percentage.

Crates and inventory loot

crates:
  enabled: true
  chance: 2.5
  entries:
    rare:
      block: PURPLE_SHULKER_BOX
      weight: 20
      rolls: '3-6'
      loot:
        - 'DIAMOND:2-6:70'
        - 'NETHERITE_SCRAP:1-2:30'

Crates may use chests, trapped chests, barrels, or shulker boxes. Loot is inserted directly into the generated container. rolls defines the number of selections; each loot entry defines material, amount range, and relative weight.

Validation

Invalid materials, entities, equipment slots, percentages, amount ranges, or empty positive pools are rejected during startup or reload with a configuration path. Back up a working tier file before large balance changes.