-
Notifications
You must be signed in to change notification settings - Fork 2
LibCommand
ImperaZim edited this page Jun 30, 2026
·
2 revisions
| Field | Value |
|---|---|
| Package id | libcommand |
| Plugin name | LibCommand |
| Current line | 2.x |
| Namespace | imperazim\command |
| Hard dependencies | LibPacket |
| Soft dependencies | none |
LibCommand provides rich command classes, arguments, enums, subcommands and the EasyLibrary rich command backend.
- Package-backed through EasyLibrary.
- Standalone PHAR as
LibCommand.
EasyLibrary uses rich commands only when a package-backed or standalone
LibCommand provider is active. If LibCommand is unavailable, EasyLibrary uses a
native fallback backend for doctor/repair/install operations and module
diagnostics. This fallback is intentionally simpler than the rich LibCommand
tree, but /easylibrary and /modules remain reachable from console.
/easylibrary doctor
/easylibrary packages status libcommand
/easylibrary packages doctor
Expected rich backend shape:
Command provider: package-backed
Command backend: libcommand-rich
Development probe:
/elprobe run libcommand
- Package Manager
- Package Backed Plugins
- Standalone vs Package
- Package Switch and Migration
- Package Doctor
- Package Safety Gate
- Support Report Bundle
- Timings
- Package Recovery
- Proxy Troubleshooting
- Migrating from EasyLibrary 2.0 to 3.x
- Embedded Libraries Migration Map
- Removed Features and Replacements
- Deprecated APIs
- Compatibility Policy
- Config Migration
- 3x Dev Scope Checkpoint
- Plugin Developer Migration
- Server Administrator Migration
- Official Libraries
- LibPacket
- LibCommand
- LibSerializer
- LibForm
- LibDB
- LibCommons
- LibHttp
- LibAssets
- LibPlaceholder
- LibWorld
- EasyLibrary Agent Bridge
- LibCustom
- LibEnchantment
- LibHud
- LibTrigger
- LibWindow
- Public API Contract
- Module Boundary
- Module Smoke Matrix
- LibAsync Incubator
- LibReflect Incubator
- Doctor Output
- Repository Notifications
- Smoke Tests
- Common Errors
- Release and Changelog