Skip to content

Conversation

@WolfyScript
Copy link
Owner

The idea of the expansion packs is to make it easier to share custom content.

Expansions are read from zip files inside the WolfyUtilities/expansion_packs.
Each expansion zip file must have a pack.json that contains the following content:

{
  "pack": {
    "version": 1,
    //Usually your lowercase plugin name. Spaces are not allowed! Must be unique from other packs!
    "namespace": "<namespace>",
    "authors": [],
    "description": ""
  }
}

The data is then put in separate folders depending on their registry.

  • items/items – The CustomItem folder, that contains all the CustomItem json files.
  • particles/effects – All the custom particle effects
  • particles/animations – All the custom particle animations

That is all the default data, that can be loaded so far.

However, it is possible to register more custom ResourceLoader into the Registry you can get via Registries#getExpansionResourceLoaders.

… ResourceLoaders.

The register order is preserved and the resources loaded accordingly.
# Conflicts:
#	core/src/main/java/me/wolfyscript/utilities/registry/Registries.java
#	wolfyutilities/src/main/java/me/wolfyscript/utilities/main/WUPlugin.java
… ResourceLoaders.

The register order is preserved and the resources loaded accordingly.
@WolfyScript WolfyScript added the enhancement New feature or request label Mar 9, 2022
@WolfyScript WolfyScript self-assigned this Mar 9, 2022
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

Successfully merging this pull request may close these issues.

2 participants