OBSIDREL / DOCS

Documentation

Guides, tutorials and technical references for the Obsidrel ecosystem.

DocumentationCooldowns: duration, scope and conditions

Cooldowns: duration, scope and conditions

Define reusable cooldowns in plugins/Obsidrel/resources/cooldowns/. They require a compatible Condition or other invocation.

Real Core-style example

yaml
ruby_use:
  enabled: true
  duration: 5s
  scope: PLAYER_ITEM
  persistent: false
  message: '<warning>Wait {cooldown_remaining}.</warning>

The Core sample also supports a bypass-permission field for an administrator exemption. Another sample uses 750ms and PLAYER scope.

FieldMeaning
enabledOn/off
durationTime such as 5s, 750ms
scopePLAYER or PLAYER_ITEM
persistentOptional persistence
bypass-permissionOptional exemption
messageFeedback with {cooldown_remaining}

Connect

yaml
ruby_ready:
  enabled: true
  type: COOLDOWN
  cooldown: ruby_use

Save as resources/conditions/ and use conditions: [ruby_ready] in an Action or Trigger. Evaluating COOLDOWN may reserve it: test fast clicks, different items and reconnects.

Conditions · Actions.

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.