OBSIDREL / DOCS

Documentation

Guides, tutorials and technical references for the Obsidrel ecosystem.

DocumentationCooldowns and loot tables

Cooldowns and loot tables

Cooldowns belong in resources/cooldowns/. They can be referenced by conditions or mechanics.

yaml
ruby_use:
  enabled: true
  duration: 5s
  scope: PLAYER_ITEM
  persistent: false
  bypass-permission: 'obsidrel.admin'

The sample documents the PLAYER_ITEM and PLAYER scopes. Durations also include millisecond notation such as 750ms.

Loot tables

Reusable loot goes in resources/loot/. The shipped source sample distinguishes ALL and WEIGHTED modes.

yaml
ruby_cache:
  enabled: true
  mode: WEIGHTED
  rolls: 2
  delivery: INVENTORY
  entries:
    ruby:
      item: obsidrel:ruby
      amount: '1-2'
      weight: 70
    diamond:
      item: minecraft:diamond
      amount: 1
      weight: 20

Important: the example files ship many loot tables with enabled: false by default. Explicitly enable only tables you intend to test. The weight values describe relative selection weights, not a guaranteed item count.

Applying this in your project

Choose the cooldown scope (player or player-item) deliberately. For a weighted loot table, test many rolls; weights describe relative selection, not guaranteed percentages.

Back up before modifying production. Run /obsidrel reload, inspect warnings and test in game. Rebuild the resource pack for model or texture changes.

See the field reference for documented sample options.

Was this article helpful?Loading ratings…

Help us improve Obsidrel documentation. One vote per account and article. Discord AI feedback can also contribute when the answer cites this article.