Separate resource pack loading from ResourcePackManager::__construct() #6254
Labels
BC break
Breaks API compatibility
Category: API
Related to the plugin API
Category: Core
Related to internal functionality
Description
As per title. ResourcePackManager should focus on managing packs rather than where to load them from.
Justification
With its expanded API in newer versions, it's possible (perhaps even desirable) to construct a ResourcePackManager entirely using its API, as opposed to having it load packs from a certain folder on the disk.
Alternative methods
The text was updated successfully, but these errors were encountered: