-
Notifications
You must be signed in to change notification settings - Fork 2
Plugin Developer Migration
ImperaZim edited this page Jun 21, 2026
·
1 revision
EasyLibrary 3.x no longer guarantees that official library namespaces are present just because EasyLibrary is installed.
Use hard dependencies only when required:
depend:
- LibCommandUse soft dependencies for optional features:
softdepend:
- EasyLibrary
- LibCommand
- LibPlaceholder
- LibWorld$plugin = $this->getServer()->getPluginManager()->getPlugin("LibPlaceholder");
if($plugin === null || !$plugin->isEnabled()){
return;
}Doctor output is for humans. Use public APIs, PMMP dependency declarations or future service/capability contracts for programmatic integration.
Package-backed and standalone providers keep the same public library namespaces. Your code should care that the provider exists, not whether it came from EasyLibrary package storage or a standalone PHAR.
- 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