Skip to main content

Resource Pack Merging

Use the merge export when another plugin or provider builds your server's final resource pack.

This is designed for ItemsAdder, Oraxen, Nexo and custom pack pipelines. It gives the provider the TextEffect assets it needs without asking it to use TextEffect's standalone pack as the final pack.

Build a merge-ready export​

Run:

/texteffect zip merge

TextEffect creates:

plugins/TextEffect/generated/merge-ready/
├── TextEffect-Merge-Pack.zip
├── assets/
└── README.txt

The merge export is intentionally unprotected and contains only the assets files required by TextEffect. It does not contain pack.mcmeta, because your pack provider is responsible for building and sending the final combined resource pack.

Import it into your pack provider​

Import either of these into your provider:

TextEffect-Merge-Pack.zip

or:

assets/

Do not import both. They contain the same TextEffect files.

Then rebuild the provider's final resource pack and let that provider host or send the final result to players.

Important settings​

Once another provider sends the final combined pack, keep TextEffect's own sender disabled:

resource-pack:
  send-on-join: false

ItemsAdder​

For ItemsAdder, keep the imported TextEffect content in its resource-pack contents list, disable ItemsAdder's own text shader feature, then build the pack through ItemsAdder:

text_effects:
  enabled: false

After importing the assets, run:

/iazip

Shader conflicts​

TextEffect replaces Minecraft's text shader files. If another pack also replaces those same files, the final pack needs a compatible merge or priority decision before both features can work correctly.

The generated README.txt includes the exported paths and a short setup reminder for the merge flow.