docs(core): plan resource pack support as LibAssets

Author: ImperaZim

CHANGELOG.md

@@ -345,6 +345,8 @@ elprobe run <package>
   registration:
   `PluginLanguageTrait`, `PluginResourcePacksTrait`,
   `PluginCdnResourcePackTrait` and `components\utils\ResourcePacks`.
+  Resource-pack support should return later as a focused assets/resource-pack
+  library such as `LibAssets`, not as part of `LibCommons`.
 - `imperazim\components\filesystem\File` no longer depends on the removed
   Config wrapper; pass a directory string or use PocketMine `Config` directly.
 - Component enable/disable notices now use PocketMine `TextFormat` constants

README.md

@@ -218,7 +218,9 @@ were removed as well:
 `PluginLanguageTrait`, `PluginResourcePacksTrait`,
 `PluginCdnResourcePackTrait` and `components\utils\ResourcePacks`. Keep
 localization/resource-pack bootstrapping inside the owning plugin for now, or
-move it to a dedicated package if the ecosystem needs one later.
+move it to a future dedicated assets/resource-pack package such as `LibAssets`
+if the ecosystem needs one later. This does not belong in `LibCommons`, because
+resource packs require PocketMine lifecycle, files, manifests and server state.
 
 Use each standalone repository for complete API documentation and examples.
 

changelogs/3.0.md

@@ -1575,6 +1575,12 @@ reflection, which should not be presented as a stable EasyLibrary core API. In
 3.x, localization and resource-pack bootstrapping should stay inside the plugin
 that owns those assets until a focused library is deliberately designed.
 
+If resource-pack support returns as an official package, the preferred shape is
+a dedicated assets/resource-pack library such as `LibAssets`. It should cover
+manifest validation, zip packaging, checksums, local registration and optional
+CDN integration. It should not be part of `LibCommons`, because resource packs
+need PocketMine lifecycle, filesystem state and server resource-pack handling.
+
 The component logging polish is intentionally small but useful for the 3.x
 cleanup: active core output should be generated through PocketMine formatting
 APIs instead of embedded formatting bytes. This keeps console output and future
@@ -1596,7 +1602,8 @@ package instead of depending on EasyLibrary core for gameplay or utility APIs.
 
 If a plugin used the removed language or resource-pack traits, copy that
 bootstrapping into the owning plugin for now. Do not rely on EasyLibrary core to
-register resource packs through reflection in 3.x.
+register resource packs through reflection in 3.x. If/when `LibAssets` exists,
+move that integration there instead of depending on EasyLibrary core.
 
 If old code used the removed Config wrapper with `File`, migrate it to explicit
 file metadata:

docs/migration.md

@@ -89,9 +89,9 @@ Removed 2.x-era helpers:
 | `imperazim\components\plugin\ConfigManager` | Plugin-owned config registry or future dedicated config lib |
 | `imperazim\components\plugin\ExceptionHandler` | Native try/catch, domain-specific exceptions or future diagnostics/result helpers |
 | `imperazim\components\plugin\traits\PluginLanguageTrait` | Plugin-owned localization or future dedicated text/config lib |
-| `imperazim\components\plugin\traits\PluginResourcePacksTrait` | Plugin-owned resource-pack bootstrapping |
-| `imperazim\components\plugin\traits\PluginCdnResourcePackTrait` | Plugin-owned CDN/resource-pack integration |
-| `imperazim\components\utils\ResourcePacks` | Plugin-owned resource-pack registration or future dedicated resource-pack lib |
+| `imperazim\components\plugin\traits\PluginResourcePacksTrait` | Plugin-owned resource-pack bootstrapping or future `LibAssets` |
+| `imperazim\components\plugin\traits\PluginCdnResourcePackTrait` | Plugin-owned CDN/resource-pack integration or future `LibAssets` + `LibHttp` |
+| `imperazim\components\utils\ResourcePacks` | Plugin-owned resource-pack registration or future `LibAssets` |
 
 The old `File` constructor no longer accepts the removed
 `imperazim\components\config\Config` wrapper. Pass a directory string and file
@@ -101,7 +101,8 @@ configuration file.
 The removed resource-pack helpers used PocketMine internals and reflection.
 Do not depend on EasyLibrary core for that behavior in 3.x; keep resource-pack
 registration explicit in the plugin that owns the pack until a focused API is
-designed.
+designed. If this becomes an official library, it should be a dedicated
+assets/resource-pack package such as `LibAssets`, not `LibCommons`.
 
 For plugin code, prefer normal PMMP dependency declarations instead of assuming
 EasyLibrary always ships a class: