You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The 3.x direction is: EasyLibrary becomes the minimal manager, official libs bec
17
17
18
18
## What EasyLibrary provides
19
19
20
-
- A 3.x internal package manager foundation for official packages such as `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libplaceholder`, `libworld` and `agent-bridge`.
20
+
- A 3.x internal package manager foundation for official packages such as `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libcommons`, `libplaceholder`, `libworld` and `agent-bridge`.
21
21
- Dry-run package install plans, checksum-backed downloads, backups, restart-required state and package lock diagnostics.
22
22
- Legacy standalone PHAR install planning through `/easylibrary libs install` while migration is in progress.
23
23
- Official library runtime diagnostics through `/easylibrary libs`, `/easylibrary packages` and `/easylibrary doctor`.
@@ -67,7 +67,7 @@ Run these commands after installing or updating EasyLibrary:
67
67
At minimum, a healthy server should report `Problems: 0`. When all official packages are installed and active, a full package-backed test server looks like this:
@@ -322,7 +323,7 @@ The preferred 3.x command path is `/easylibrary packages`. The old `/easylibrary
322
323
```
323
324
324
325
325
-
Current asset-ready internal packages in this wave include `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libplaceholder`, `libworld`, `agent-bridge`, `libcustom`, `libenchantment`, `libhud`, `libtrigger` and `libwindow`. Every package remains protected by the standalone shadow guard while a matching standalone plugin is installed.
326
+
Current asset-ready internal packages in this wave include `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libcommons`, `libplaceholder`, `libworld`, `agent-bridge`, `libcustom`, `libenchantment`, `libhud`, `libtrigger` and `libwindow`. Every package remains protected by the standalone shadow guard while a matching standalone plugin is installed.
326
327
327
328
### Internal package activation gate
328
329
@@ -411,7 +412,7 @@ First package targets:
411
412
- `libpacket`is the first dependency-safe classpath package and should be installed before command/runtime packages that depend on packet services.
412
413
- `libcommand`is asset-ready too, but should be installed after `libpacket`.
413
414
414
-
The package-backed loader has now validated the base wave (`libserializer`, `libform`, `libdb`, `libpacket`, `libcommand`), the isolated runtime wave (`libwindow`, `libcustom`, `libenchantment`, `libtrigger`), the standalone `libhud` wave, the dependency-heavy placeholder wave, the world-service wave and the final Agent bridge wave.
415
+
The package-backed loader has now validated the base wave (`libserializer`, `libform`, `libdb`, `libpacket`, `libcommand`), the isolated runtime wave (`libwindow`, `libcustom`, `libenchantment`, `libtrigger`), the standalone `libhud` wave, the dependency-heavy placeholder wave, the world-service wave, the final Agent bridge wave and the new `libcommons` classpath package wave.
415
416
416
417
`/easylibrary packages doctor`validates package paths, installed manifests, sha256 metadata, proxy marker data and stale restart markers. If a package is already active through the package-backed proxy, stale restart-required entries are cleared automatically.
417
418
@@ -429,11 +430,11 @@ The package-backed loader has now validated the base wave (`libserializer`, `lib
429
430
430
431
`/easylibrary doctor` also reports the active command provider and the selected command backend. The provider explains where `imperazim\command\Command` was loaded from, while the backend explains how EasyLibrary registered its command surface: `libcommand-rich`for the full command tree or `native-pocketmine-recovery` for the minimal recovery command. EasyLibrary 3.x only treats package-backed or standalone `LibCommand` as rich command providers; if neither is available, the core registers the recovery-safe native command.
431
432
432
-
The package-backed command path has been validated in-game with all 13 official packages active: `/easylibrary doctor`should show `Command provider: package-backed`, `Command backend: libcommand-rich`, `rich: yes`, `overrides: yes` and no official library runtime problems.
433
+
The package-backed command path has been validated in-game with all official packages active: `/easylibrary doctor`should show `Command provider: package-backed`, `Command backend: libcommand-rich`, `rich: yes`, `overrides: yes` and no official library runtime problems.
433
434
434
435
If LibCommand is unavailable, EasyLibrary registers a minimal recovery command that uses PocketMine's native command base instead of the rich LibCommand tree. That fallback intentionally exposes only recovery-safe commands: `doctor`, `config doctor`, `config reload`, `config migrate`, `config repair`, `packages doctor`, `packages install`, `packages repair` and `packages cleanup`. This means a broken or missing command provider can be recovered from console with `/easylibrary packages install libcommand confirm` after package writes are enabled.
435
436
436
-
During mixed-mode migration, installing `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libwindow`, `libcustom`, `libenchantment`, `libtrigger`, `libhud`, `libplaceholder`, `libworld` or `agent-bridge` while the standalone PHAR is still in `plugins/` is allowed. After restart, the package is expected to show as `installed-shadowed-by-standalone`; the standalone plugin continues to provide the runtime and EasyLibrary does not autoload the duplicate internal package.
437
+
During mixed-mode migration, installing `libpacket`, `libcommand`, `libserializer`, `libform`, `libdb`, `libcommons`, `libwindow`, `libcustom`, `libenchantment`, `libtrigger`, `libhud`, `libplaceholder`, `libworld` or `agent-bridge` while the standalone PHAR is still in `plugins/` is allowed. After restart, the package is expected to show as `installed-shadowed-by-standalone`; the standalone plugin continues to provide the runtime and EasyLibrary does not autoload the duplicate internal package.
0 commit comments