Separate resource pack loading from ResourcePackManager::__construct()
dktapps opened this issue · comments
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.