Configuration reference

This is the config.yml ItemForge 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: language, license-key, limits, protected-materials, log, debug.

# ItemForge — the item in your hand, edited from one command.
#
# Every message lives in lang/<language>.yml. Everything that decides what is
# allowed lives here, which is the point: the plugins this replaces keep their
# protected list inside the code, so a server that wants to protect anything
# else has to recompile.

language: en

# The key BuiltByBit gave you. Checked in the background at startup; if their
# API is unreachable the plugin starts anyway.
license-key: ""

limits:
  # Longest display name, in visible characters. Formatting codes do not count.
  # Names longer than this break anvils, holograms and hover text.
  name-length: 48

  # Longest single lore line, and how many lines an item may carry.
  lore-line-length: 64
  lore-lines: 12

  # Highest level /item enchant will apply. Vanilla tops out far below this;
  # clients start misbehaving well past a few dozen.
  enchant-level: 10

  # Largest stack /item amount will set. 0 = the item's own maximum.
  amount: 0

# Materials nobody edits without itemforge.protected. These are the ones worth
# forging: a renamed spawner or a renamed written book is how a fake passes for
# the real thing on a survival server.
#
# The list covers EVERY verb, not just renaming, so think twice before adding a
# material this plugin has a command for. PLAYER_HEAD is the example: put it in
# here and `/item head` stops working for anyone without itemforge.protected,
# which is almost never what you meant.
protected-materials:
  - SPAWNER
  - WRITTEN_BOOK
  - FILLED_MAP

log:
  # Write each edit to the server log: who, what item, what changed.
  to-console: true

debug:
  # Anonymous usage stats at bstats.org. Turn it off on an offline network.
  bstats: true