DUXPLIMA Documentation

Modules

The files in modules/, what each holds, and the permission lists four of them share.

Each feature has a file of its own under modules/.

FileWhat it holdsDocumented in
settings.ymlVirtual storage and XP storage defaultsStorage & Selling
storage_limits.ymlItem and XP storage limits, with permission tiersStorage & Selling
multipliers.ymlSell multipliers by permissionStorage & Selling
autokill.ymlAuto-kill, its permission, split slimesAuto-Kill
boosts.ymlBoost itemsBoosts
friends.ymlShared access to a spawnerFriends
hologram.ymlThe text above a spawnerHolograms
other.ymlBreaking, drop chances, the pickaxe, vanilla spawners, auto-pickup, the level limit, titlesBreaking Rules, Levels

Not every enabled switch turns its feature off in 4.2.0:

SwitchEffect
hologram.enabled, multipliers.enabled, storage-limit.enabledWork as expected
auto-kill.enabledOnly decides, with force, whether new spawners start with auto-kill on
friends.enabled, boosts.enabledNot read. Hide the friends button with gui: false in the language file; remove boost entries to stop boosts

The permission lists

Four settings share one shape, a default and a map of permission to value:

permissions:
  uxmspawners-storage1: 5000
  uxmspawners-storage2: 10000
  uxmspawners-storage3: 20000

A player holding several of the nodes gets the highest value, not the sum, whatever the order. A player holding none gets the default. They are used for item storage limits, XP storage limits, sell multipliers and drop chances.

The comments in the shipped files ask for ascending order. It does no harm, and keeps the file easy to read, but the plugin does not need it.

Related: Permissions, config.yml