Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per plugin resource-packs #8

Open
yusshu opened this issue Feb 5, 2024 · 0 comments
Open

Per plugin resource-packs #8

yusshu opened this issue Feb 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@yusshu
Copy link
Member

yusshu commented Feb 5, 2024

At the moment, plugins have to listen to the ResourcePackGenerateEvent and register their resources in the single, server resource-pack initially created by creative-central.

This new idea of per-plugin-resourcepacks would be similar to how external resource packs (e.g. from ModelEngine4, ItemsAdder, Oraxen) are currently handled in the Bukkit plugin. The external resource pack provider loads the resource-pack and it's then merged with the central resource-pack.

For example:

interface ResourcePackProvider {
  String pluginName();
  
  ResourcePack create();
}

We could have something similar for creative-central plugins, which would allow:

  • Check the amount of resources a plugin generates (we could have something like /central info <pluginName>)
  • Check which plugins are not compatible with other plugins

This will also remove the need of 'ExternalResourcePackProvider's, since they can be normal ResourcePack providers, but registered by creative-central.

@yusshu yusshu added the enhancement New feature or request label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant