Previous: Configuration File　·　Next: Item Source References

🕹️ Commands & Permissions

QCL is built on the Cloud command framework. The command root is /qcl, with alias /qinhcorelib. This page provides the complete command tree, usage examples, expected output, the permission node table, and recommended permission group assignments.

🌳 Command Tree Overview

Command	Alias	Permission	Function
`/qcl`	—	None	Show help
`/qcl status`	`/qcl probe`	`qcl.status`	Ecosystem status summary
`/qcl status detail`	`/qcl status full`	`qcl.status`	Detailed status (per-module / per-bridge / script extension lines)
`/qcl reload`	`/qcl rl`	`qcl.admin`	Reload config + economy + scripts + external item modules + GUI
`/qcl gui <id>`	—	`qcl.gui`	Open a custom GUI (player only)
`/qcl attr`	`/qcl attribute`	`qcl.admin`	Attribute system debug overview
`/qcl attr list`	—	`qcl.admin`	List all registered attributes (grouped by category)
`/qcl attr show [player]`	—	`qcl.admin`	View a player's attribute totals (summed across sources)
`/qcl attr debug`	—	`qcl.admin`	Toggle hit-damage tracing (player only)
`/qcl attr book`	—	None	Open the attribute panel book (player only)
`/qcl mobattr <key> <value>`	—	`qcl.admin`	Set an attribute on the mob you're looking at (for testing, player only)

/qinhcorelib is the full alias of /qcl; all commands below can be used with the /qinhcorelib prefix instead.

📜 /qcl — Help

Typing /qcl directly shows the help. No permission required. The help output has a fixed format: separator line + "Qinhuai Core Library" + three lines describing status / reload / gui.

————————————————————————
Qinhuai Core Library
/qcl status  - View ecosystem & bridge status
/qcl reload  - Reload configuration files
/qcl gui <id> - Open custom GUI
/qcl attr  - Attribute system debug (list/show)
————————————————————————

🔍 /qcl status — Status Summary

Permission: qcl.status　Alias: /qcl probe

/qcl status

Outputs a health summary of the entire Qinhuai ecosystem: soft-dependency probes (item source count + list, economy, attribute plugins, integrated plugins), platform status and health code, per-module health codes, health codes for each bridge (script / economy / PAPI / database / PDC), sub-plugin status (QI / QS / QF / QSt), config diagnostic code, API boundary code, item reference diagnostic code, and more.

Detailed Version

/qcl status detail

Alias: /qcl status full. On top of the summary, it additionally outputs: bridge count, module count, TraceId, per-module (enabled/disabled + available/unavailable + message), per-bridge (enabled/disabled + available/unavailable + source + message), as well as the lines appended by the script global:qcl_status.js:formatStatus.

🩺 For the meaning, normal values, and exception handling of each item, see Diagnostics & Troubleshooting.

🔄 /qcl reload — Reload

Permission: qcl.admin　Alias: /qcl rl

/qcl reload

During execution it shows "Reloading…", and on completion shows "Reload complete".

📦 What reload reloads

Reload Item	Description
config	Re-reads `config.yml`
Economy	Re-initializes the economy provider
Scripts	Reloads JS scripts
External item modules	Re-probes / re-integrates external item plugins
GUI	Reloads custom GUI definitions

⚠️ Which changes reload can't handle and require a restart

Change	Is reload enough?
`database.type` or MySQL connection parameters	❌ Restart required (the connection is established at startup)
`modules` module switches	❌ Restart recommended (affects module loading)
`debug` / `economy` / script content / GUI / item references	✅ reload is sufficient

See the "Change Effect Method Quick Reference" in Configuration File.

🖼️ /qcl gui <id> — Open GUI

Permission: qcl.gui　Player only

/qcl gui 主菜单

Opens the custom GUI with id 主菜单 (Main Menu). If that id does not exist, it shows:

GUI not found: 主菜单

🔗 For GUI definition and development, see GUI Programming API.

🗡️ /qcl attr — Attribute System Debug

Permission: qcl.admin (the book subcommand needs no permission)　Alias: /qcl attribute

Subcommand	Function
`/qcl attr`	Overview: configured backend / active backend / GraalJS status / registered attribute count
`/qcl attr list`	List all attributes, grouped by category, tagged vanilla / item / storage type and damage type
`/qcl attr show [player]`	View a player's attribute totals (omit to view your own; console must specify a player name)
`/qcl attr debug`	Toggle "hit damage tracing" — prints the attribute resolution each time you deal / take damage (player only)
`/qcl attr book`	Open the attribute panel book (player only, no permission)

🗡️ For how to configure attributes and write custom ones (yml + JS), see Attribute System.

🐲 /qcl mobattr — Set Attributes on a Mob (for testing)

Permission: qcl.admin　Player only

/qcl mobattr <attr key> <value>   # look at a mob (within 12 blocks) and set that attribute on it
/qcl mobattr clear                # clear all attributes from that mob

The fastest way to test a custom attribute: e.g. /qcl mobattr defense 100 gives the mob 100 defense, then hit it to see whether mitigation works.

🔐 Permission Node Table

Permission Node	Command(s) Controlled	Nature
`qcl.status`	`/qcl status`, `/qcl status detail`	View type (read-only)
`qcl.admin`	`/qcl reload`, `/qcl attr` (incl. list / show / debug), `/qcl mobattr`	Admin type (side effects / debug)
`qcl.gui`	`/qcl gui <id>`	Player feature type

/qcl (help) and /qcl attr book require no permission and are available to everyone.

👥 Recommended Permission Group Assignments

🛡️ Admin Group (admin / op)

yaml

permissions:
  - qcl.status   # View ecosystem status
  - qcl.admin    # Reload configuration
  - qcl.gui      # Open GUI

🧑 Regular Player Group (default)

yaml

permissions:
  - qcl.gui      # Only allow opening GUIs (as needed)

💡 qcl.admin (reload) has side effects, so only grant it to trusted admins. qcl.status is usually only granted to admins/ops as well; regular players typically only need qcl.gui (or even not that, triggered by your own GUI sub-plugin instead).

📖 Further Reading

➡️ Next: Item Source References — the unified reference syntax most used by server owners
⚙️ Configuration File — the boundary between reload and restart
🩺 Diagnostics & Troubleshooting — understand every line of /qcl status
📚 Diagnostic Codes　·　FAQ

🕹️ Commands & Permissions ​

🌳 Command Tree Overview ​

📜 /qcl — Help ​

🔍 /qcl status — Status Summary ​

Detailed Version ​

🔄 /qcl reload — Reload ​

📦 What reload reloads ​

⚠️ Which changes reload can't handle and require a restart ​

🖼️ /qcl gui <id> — Open GUI ​

🗡️ /qcl attr — Attribute System Debug ​

🐲 /qcl mobattr — Set Attributes on a Mob (for testing) ​

🔐 Permission Node Table ​

👥 Recommended Permission Group Assignments ​

🛡️ Admin Group (admin / op) ​

🧑 Regular Player Group (default) ​

📖 Further Reading ​