6 Commands and Permissions

6 - Commands and Permissions

Divinity exposes a root command with aliases from config.yml. The bundled aliases are div, prorpgitems, rpgitems, rpgi, quantumrpg, and qrpg.

Shared module commands

Drop-based modules expose these administrator commands under their module alias:

/<module> list [page]
/<module> get [item-id] [level|range] [amount]
/<module> give <player> [item-id] [level|range] [amount]
/<module> drop <world> <x> <y> <z> <item-id> [level|range] [amount]
/<module> reload

random is accepted as the item ID by the shared item commands. quantumrpg.admin is the permission used by these generic administrative commands.

Namespace compatibility

The code accepts both quantumrpg.* and the equivalent divinity.* permission names. Use the divinity.* names in new server permission files; retain quantumrpg.* when integrating an older permission setup.

Important permission groups

Capability	Permission
normal player access	divinity.user
full administration	divinity.admin
bypass all requirements	divinity.bypass
bypass level/class/soulbound/untradeable	divinity.bypass.requirement.level, .class, .soulbound, .untradeable
class commands	divinity.classes.cmd.*
socket merchants	divinity.gems.cmd.merchant, divinity.runes.cmd.merchant, divinity.essences.cmd.merchant
GUI-based modules	<module>.gui as listed on the module page

The individual module pages list exact command nodes so permission files can stay least-privilege.

Modules with shared item commands

The shared list, get, give, and drop commands are available to item-based modules such as Active Items, Arrows, Consumables, Custom Items, Dismantle, Essences, Extractor, Fortify, Gems, Identify, Item Generator, Magic Dust, Money, Refine, Repair, and Runes. Item Generator additionally accepts an optional material argument.

get is player-only. Use give or drop from the console. Run /<module> help on the installed version before scripting commands because optional arguments vary by module and release.

Module-specific command groups

Module	Commands	Permission prefix
Classes	select, skills, aspects, stats, cast, progression administration	divinity.classes.cmd.*
Combat Log	log	divinity.combatlog.cmd.*
Dismantle	open [player]	divinity.dismantle.cmd.*, divinity.dismantle.gui
Drops	drop, give	divinity.admin
Essences, Gems, Runes	merchant [player]	divinity.<module>.cmd.*, divinity.<module>.gui.*
Extractor	open [player]	divinity.extractor.cmd.*, divinity.extractor.gui
Fortify	fortify, unfortify	divinity.fortify.cmd.*
Identify	identify	divinity.identify.cmd.*
Magic Dust	open [player]	divinity.magicdust.cmd.*, divinity.magicdust.gui
Party	chat, create, disband, drop, exp, invite, join, kick, leave, menu, roll, tp	divinity.party.cmd.*
Refine	refine, downgrade	divinity.refine.cmd.*
Repair	open [player]	divinity.repair.cmd.*, divinity.repair.gui
Sell	open [player]	divinity.sell.cmd.*, divinity.sell.gui
Soulbound	soul, untradeable	divinity.soulbound.cmd.*

Administrator permission policy

• Grant divinity.admin only to trusted administrators. It includes item creation and module reload capabilities.
• Do not grant divinity.bypass to normal players; it bypasses class, level, soulbound, and untradeable requirements.
• Prefer individual command and GUI nodes for moderators, builders, and testers.
• Test permissions with a non-operator account. Operators can hide missing permission nodes.
• Existing servers may keep quantumrpg.*; do not grant both namespaces unless your permission plugin requires it.

Example for LuckPerms:

/lp group divinity-admin permission set divinity.admin true
/lp group default permission set divinity.party true
/lp user <name> permission check divinity.sell.gui

Reload or restart?

• Use /<module> reload after editing only that module's settings.yml or content files.
• Restart after changing config.yml, engine.yml, storage, compatibility providers, profile enablement, or module loading.
• Check the console after every reload. If parsing fails, restore the backup instead of repeatedly reloading a broken file.