Configuration reference

This is the config.yml EnchantsForge writes on first start, comments included. Every key you see here is the key the plugin reads; there are no hidden ones. Change a value, reload, and it applies.
Top-level sections: license-key, fusion-altar, orbs, messages.
# =============================================================================
# EFV2Addon — Configuration
# =============================================================================
# This is the addon for EnchantsForge that ships 15 new enchants, the Fusion
# Altar, and the Enchant Orb drop system. Edit values below and run
# /ce reload to apply (no restart needed).
# -----------------------------------------------------------------------------

# Your BuiltByBit license key. Leave empty to run in grace mode (the plugin
# still works, but logs a warning on startup). Required for paid distribution
# builds; ignored for source builds.
license-key: ""

# =============================================================================
# Fusion Altar
# =============================================================================
fusion-altar:
  # Master switch — set to false to disable Fusion Altar entirely.
  enabled: true
  # If true, all 4 candles in the structure must be lit. If false, unlit
  # candles also count. Visual purists usually keep this true.
  require-candles-lit: true

# =============================================================================
# Enchant Orbs
# =============================================================================
orbs:
  # Master switch — set to false to disable orb drops + orb application.
  enabled: true
  # When true, orbs only drop from hostile mobs (zombies, skeletons, etc.).
  # When false, every living entity may drop them.
  hostile-only: true

# =============================================================================
# Messages
# =============================================================================
# Use MiniMessage tags: <red>, <gold>, <#hex>, <gradient:a:b>, etc.
# Placeholders like <enchant>, <level>, <required> are replaced at runtime.
messages:
  # Sent when a non-admin tries to use admin commands.
  no-permission: "<red>You don't have permission to do that.</red>"

  # Fusion Altar — right-clicked a Lodestone that wasn't a valid structure.
  fusion-invalid-structure: "<red>Build a valid Fusion Altar: Lodestone center, 4 Crying Obsidian at (±2,0,0)/(0,0,±2), Candles at (±1,0,0)/(0,0,±1).</red>"
  # Inputs don't match any recipe in fusion.yml.
  fusion-no-recipe: "<gray>No valid fusion recipe for these enchants.</gray>"
  # Player has less XP than the recipe requires. <required> = level cost.
  fusion-not-enough-xp: "<red>You need <required> XP levels for this fusion.</red>"
  # Fusion succeeded — <enchant> is the output enchant id.
  fusion-success: "<green>Fusion successful! Applied <enchant> to your item.</green>"
  # Roll failed and no protection item was present — inputs destroyed.
  fusion-failure: "<red>Fusion failed! Both inputs were destroyed.</red>"
  # Roll failed but the protection item absorbed the loss.
  fusion-failure-protected: "<yellow>Fusion failed but your items were protected!</yellow>"

  # Orb applied successfully. <enchant>/<level> are the rolled enchant.
  orb-applied: "<green>Applied <enchant> <level> to your item!</green>"
  # The rolled enchant is already maxed on the target item.
  orb-max-level: "<yellow>That enchant is already at max level on this item.</yellow>"
  # The orb's rarity pool has no enchants compatible with the held item type.
  orb-incompatible: "<red>This orb has no compatible enchants for that item.</red>"