1 Global Configuration

01 — Global Configuration

Main file: plugins/Divinity/config.yml

What it controls

Section	Use it for
divinity	language, aliases, and chat prefix
data	autosave, SQLite/MySQL connection, and purge settings
tiers	stable tier IDs, colors, and display names
modules	global module overrides; { } means use module defaults
item-sub-types	specific classifications such as sword, helmet, or bow
item-groups	broad classifications such as WEAPON, TOOL, and ARMOR

First changes to make

• Keep data.storage.type: sqlite for a single server with no database service.
• Change data.storage.* together when moving to MySQL.
• Add new tier IDs instead of renaming tiers already used by item files.
• Use the existing aliases (div, prorpgitems, rpgitems, rpgi, quantumrpg, qrpg) when testing compatibility.
• Treat material groups as API: item requirements refer to names such as WEAPON and ARMOR.

Example: adding a tier and a subtype

config.yml — real structure from the bundled resource

divinity:
  lang: en
  command-aliases: div,prorpgitems,rpgitems,rpgi,quantumrpg,qrpg
  prefix: Divinity

data:
  auto-save: 15
  storage:
    type: sqlite

tiers:
  rare:
    color: '&a'
    name: '%TIER_COLOR%Rare'
  mythic:
    color: '&5'
    name: '%TIER_COLOR%Mythic'

item-sub-types:
  sword:
    name: Sword
    materials:
      - WOODEN_SWORD
      - DIAMOND_SWORD

item-groups:
  WEAPON:
    name: Weapon
    materials:
      - DIAMOND_SWORD
      - BOW

Reloading and validation

Reload the affected module after changing its files. For global changes, a full server restart is safer because storage, tiers, and item classifications can be referenced during module startup.

See also: 11 — Commands and Permissions, 03 — Item Stats.