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
Currently resources are loaded from 'packs', in resource pack format (zipped archives). This creates difficulty when creating new plugins which require their own new textures — you have to choose a texture in an existing pack, or add it to a new pack for this purpose (e.g., https://github.com/deathcap/ProgrammerArt).
Would be convenient of plugins could somehow include their own resources (textures/sounds/etc.), independent of any artpack.
These free-standing resources should be overridable by the loaded packs (i.e., they would have the lowest priority), but could be added without any kind of container archive. Maybe an API something like registerTexture(name, data), where data could be fs.readFileSync() with brfs.
Currently resources are loaded from 'packs', in resource pack format (zipped archives). This creates difficulty when creating new plugins which require their own new textures — you have to choose a texture in an existing pack, or add it to a new pack for this purpose (e.g., https://github.com/deathcap/ProgrammerArt).
Would be convenient of plugins could somehow include their own resources (textures/sounds/etc.), independent of any artpack.
These free-standing resources should be overridable by the loaded packs (i.e., they would have the lowest priority), but could be added without any kind of container archive. Maybe an API something like
registerTexture(name, data)
, wheredata
could befs.readFileSync()
with brfs.example plugins that could benefit:
The text was updated successfully, but these errors were encountered: