Pack Workflow
Pack Workflow
This page is the practical version of pack creation.
If you want the shortest clean path from idea to working content, follow this order.
Basic workflow
- Create a new folder under
/plugins/SkinEngine/packs/. - Add
pack.ymlso the pack exists as a real GUI entry. - Add one skin file in
configs/skins/. - Add the matching skin assets in
resourcepack/skins/. - Reload the plugin.
- Run
/se zip. - Join the server and test the content in-game.
Recommended order for larger packs
Once the first skin works, expand in this order:
- add more skin files
- lock down item categories and special states
- add translated names and descriptions if needed
- add decorative items for custom GUI visuals
- add image assets for titles and other font-based graphics
- test again after every meaningful step
A simple first milestone
For a first pack, aim for this only:
- one
pack.yml - one
swordoraxeskin - one PNG resource
- one successful
/se zip
That proves the whole pack pipeline is healthy before you add anything more complex.
Common mistakes
- building a full pack before testing the first skin
- mixing up
resourcepack/skins/,resourcepack/images/, andresourcepack/decorative_items/ - forgetting that the pack id comes from the folder name
- editing assets but forgetting to run
/se zip - using placeholders or tokens in the wrong context