# Community Packs

Community Packs are our integrated system to dynamically add custom content made by the community without the requirement for additional code.

# General Information [WIP]

<p class="callout info">This feature is available in **1.20.1-1.5+** and will **NOT** be added to outdated versions.</p>

Community Packs is a feature that allows players to add NEW assets to the mod without the use of an add-on mod.

---

#### Important- Update Changes

<p class="callout danger">Existing worlds should be safe to update but always take a backup in case you encounter an issue!</p>

To support community packs, some changes have been made. See additional pages for feature-specific changes.

- Common, Client and Recipe configs now generate in `config/swem`
- Community Pack features will likely break add-on mods.  
    **PLEASE BE PATIENT AND ALLOW CREATOR'S TIME TO UPDATE THEIR MODS**

---

#### Supported Features

<table border="1" id="bkmrk-feature-mod-version-" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 15.204%;"></col><col style="width: 17.4289%;"></col><col style="width: 67.3671%;"></col></colgroup><tbody><tr style="background-color: rgb(52, 5, 93);"><td class="align-center"><span style="color: rgb(255, 255, 255);">**Feature**</span></td><td class="align-center"><span style="color: rgb(255, 255, 255);">**Mod Version**</span></td><td class="align-center"><span style="color: rgb(255, 255, 255);">**Notes**</span></td></tr><tr><td class="align-center">Coats</td><td class="align-center">**1.20.1-1.5 Beta +**</td><td>Custom coats that do not override default, and support coat cycling + breeding tags.</td></tr><tr><td class="align-center">Tack</td><td class="align-center" style="height: 29.7969px;">**1.20.1-1.5 Release**</td><td>Custom tack that does not override default tack and can be purchased via EQ Shop.</td></tr><tr><td class="align-center">Animations</td><td class="align-center" style="height: 29.7969px;">**1.20.1-1.5 Release**</td><td>Custom animations that can be triggered via command (loop). </td></tr></tbody></table>

---

#### Frequently Asked Questions

<details id="bkmrk-%5B1%5D-community-pack-%26"><summary>\[1\] Community &amp; Content Packs</summary>

**⮞ WHAT IS A COMMUNITY PACK?** Community Packs are folders that include all the files necessary to add NEW assets such as custom coats to SWEM.

**⮞ WHAT IS A CONTENT PACK?** Content Packs is also a Community Pack, but usually with less content. It will merge into any Community Packs with the same name. This allows:

- Creators to set a consistent pack name and release smaller 'add-ons' to their main pack(s)
- Creators to easily provide updated file (ie fixes or improved) that override their original files
- Players to have fewer individual Community Packs to sort
- Players to have fewer Community Packs listed in game, and easier results by Creator   
    **Example:** `artist_kofi:`  
    **Example:** `artist_fantasy:` or `artist_bays:`

**⮞ HOW DO I KNOW IF A PACK IS READY TO USE (PREMADE)?** This depends on the source, most creators should clearly state if their content is files only or a read to use pack.

- Look at the file contents (unzip the file if it comes zipped)  
      
    ✅ Must be a folder, not a ZIP (or any other)file  
    ✅ Must have a lowercase name with no spaces. ✅`artist_packname` **❌** `Artist Pack Name`  
    ✅ Must have two folders inside it: `json` and `textures`  
    ✅ Must have at least one coats or tack item with all required files.  
     See Creator Corner if you are making a community pack and are unsure what is required.  
      
    **❌** Individual files in a single folder  
    **❌** PNG files in `json > coats` or JSON files in `textures > coats > legacy`   
    **❌** Files or folders with spaces, symbols or capital letters

<p class="callout info">There can still be other errors that prevent a pack working, but this criteria means the pack is structured correctly!</p>

**⮞ WHAT IF PACKS HAVE AN IDENTICAL NAME?**

Community Packs that do not use recommended format could have a duplicate name like `free_coats` or `kofi_coats`.

- Duplicate folders will merge into one with the files of both folders
- Files will not override or replace each other **unless** they have identical names

<span style="background-color: rgb(132, 63, 161); color: rgb(236, 240, 241);"> <span style="color: rgb(255, 255, 255);">**Creators** </span></span>

- Avoid conflicting names with recommended unique format of `coatname_artist` in all files and packs
- Avoid content 'options' with the same name - if you offer variants (ie braids vs roached) give them a unique name
- Avoid creating packs with 'old' files that may override new versions (ie fixed or improved textures)
- Update or remove old packs that may have any such files.

<p class="callout info">Always check that merged files maintain the correct folder structure and file names are valid (ie not coat\_name\_copy)</p>

**⮞ WHAT IF IT ASKS ME TO REPLACE FILES?** There is no correct answer to this:

- Replacing existing files to update a texture error is usually safe.
- Replacing existing files to update coat info for breeding tags, inspiration info is usually fine.
- Replacing existing files with outdated files could revert changes (replace with pre-fix version)  
    If you replace a file with a broken texture or non-functional json, you will need to fix it or re-download the original!

**⮞ CAN I HAVE MULTIPLE COMMUNITY PACKS?** Yes. You can install multiple Community Packs, but you should read **\[4\] Performance** if adding a lot of additional content.

</details><details id="bkmrk-%5B2%5D-modified-packs-%26"><summary>\[2\] Modifying Community Packs</summary>

<p class="callout info">Always read the Creator's Terms Of Use (TOU) as significant non-private alterations or reupload may be prohibited!</p>

**⮞ CAN I REUPLOAD A COMMUNITY PACK +/- MODIFIED?**

**✅**`JSON FILES` You can edit and distribute json files or overrides freely.  
**❌**`PNG FILES` You should not modify, re-upload, distribute or monetize Creator's work without explicit consent.

`PNG FILES` Creators have the right to set and enforce appropriate use of their content.

- You must not modify, re-upload, distribute or monetize Creator's work without explicit consent.

`JSON FILES` Creators can set reasonable requests on json modification, but do not own this asset.

**✅** You can provide **FREE** override files or packs.  
**❌** You must not create and distribute files that violate platform (ie Discord) or Community (ie SWEM) rules.  
**❌** You must not monetize file edits to profit off the original Creator(s) work without consent.  
**❌**You must not provide premade packs that include the content (pngs) of Creator(s) without consent.  
**❌** You must not remove artist credits, or add false credits.  
**❌** You must not remove artist reference, excluding reasonable modification.  
`Esperanza from Spirit` -&gt; ✅ `Palomino (Dreamwork's Spirit: "Esperanza")` **❌** `N/A`

**⮞ CAN I RENAME A PACK (AS A PLAYER / CLIENT)?**

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Multiplayer </span><span style="color: rgb(255, 255, 255);"> </span>**<span style="color: rgb(0, 0, 0);">No. This may prevent you from seeing any custom coats, even if you have all the correct files.</span>

<span style="color: rgb(0, 0, 0);">**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Singleplayer </span><span style="color: rgb(255, 255, 255);"> </span>**</span>Yes. This can sometimes help you organize custom content or shorten pack IDs.

- You must use a unique **lowercase** name with **no spaces** or **symbols**
- You should not edit information **in use by an existing save** (will need to change coats / tack affected).

**⮞ CAN I RENAME A COAT / TACK ITEM?**

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Multiplayer </span><span style="color: rgb(255, 255, 255);"> </span>**<span style="color: rgb(0, 0, 0);">No. This may prevent you from seeing any custom coats or tack, even if you have all the correct files.</span>

<span style="color: rgb(0, 0, 0);">**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Singleplayer </span><span style="color: rgb(255, 255, 255);"> </span>**</span>Yes, though this is **not recommended**.

- You must use a unique **lowercase** name with **no spaces** or **symbols**
- You must set this for the file names of both `json`, `png`, and the texture path inside the `json` file.
- You should not edit information **in use by an existing save** (will need to change coats / tack affected).

<p class="callout warning">You should use standard naming format `coatname_artist` with **appropriate artist credit** by name!</p>

**⮞ CAN I EDIT CUSTOM CONTENT INFORMATION (JSON)?**

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Multiplayer </span><span style="color: rgb(255, 255, 255);"> </span>**<span style="color: rgb(0, 0, 0);">Yes. Important information:</span>

- <span style="color: rgb(0, 0, 0);">Client-side (player) edits will only apply to your singleplayer worlds.</span>
- <span style="color: rgb(0, 0, 0);">Server-side edits will apply to all players, regardless of their individual pack settings.  
    `Texture Path` Players must use the same path to avoid black horses (missing texture)</span>

<span style="color: rgb(0, 0, 0);">**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Singleplayer </span><span style="color: rgb(255, 255, 255);"> </span>**</span>Yes, depending on type:

<table border="1" style="border-collapse: collapse; width: 100%; height: 287.094px;"><colgroup><col style="width: 16.0692%;"></col><col style="width: 25.5842%;"></col><col style="width: 58.3465%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="background-color: rgb(52, 5, 93); height: 29.7969px;">**<span style="color: rgb(255, 255, 255);">Content</span>**</td><td class="align-center" style="background-color: rgb(52, 5, 93); height: 29.7969px;">**<span style="color: rgb(255, 255, 255);">Variable</span>**</td><td class="align-center" style="background-color: rgb(52, 5, 93); height: 29.7969px;">**<span style="color: rgb(255, 255, 255);">Comments</span>**</td></tr><tr style="height: 198.703px;"><td class="align-center" style="height: 198.703px;">Coats</td><td style="height: 198.703px;">✅ Artist Credits \*  
  
✅ Inspiration \*  
  
✅ `lapis_cyclable`  
  
✅ `obtainable_by_breeding`  
  
✅ `base_colors`  
  
**❌** Model  
</td><td style="height: 198.703px;">Can include capital letters, spaces and symbols **inside the "" entry**.

Can include capital letters, spaces and symbols **inside the "" entry**.

Effect will apply to future lapis/redstone changes. **Must be true/false.**

Effect will apply to future breeding. **Must be true/false.**

Effect will apply to future breeding. Must use **valid tags.**

Must use Legacy until additional models are supported.

</td></tr><tr style="height: 28.7969px;"><td class="align-center" style="height: 28.7969px;">Tack</td><td class="align-center" style="height: 28.7969px;">TBC</td><td style="height: 28.7969px;"></td></tr><tr style="height: 29.7969px;"><td class="align-center" style="height: 29.7969px;">Animations</td><td class="align-center" style="height: 29.7969px;">TBC</td><td style="height: 29.7969px;"></td></tr></tbody></table>

<p class="callout warning">You must not remove or (unreasonably) modify Artist credits +/- reference and inspiration comments.</p>

</details><details id="bkmrk-%5B3%5D-multiplayer-use-"><summary>\[3\] Multiplayer Use</summary>

**⮞ HOW TO ADD COMMUNITY PACKS TO A SERVER?**

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Multiplayer </span><span style="color: rgb(255, 255, 255);"> </span>**Paste the community pack(s) into the server's `config > swem > communitypacks` folder as normal.

- Players (clients) must also use the exact same mod version as the server.
- Players (clients) must have a copy of the same community pack folder(s).
- Clients can have additional community packs installed for SP use.

<p class="callout info">See individual pages for troubleshooting common issues for each feature.</p>

**⮞ CAN I USE THE OFFICIAL SWEM COMMUNITY PACK ON A SERVER?** Yes. You can use this on a multiplayer server provided it is free to all players, not re-uploaded externally or monetized.  
You should not modify the contents, except to remove unwanted files or edit obtaining information (tags, breeding etc).

**⮞ CAN I USE CREATOR'S COMMUNITY PACK ON A SERVER?**

<p class="callout info">Always read the Creator's Terms Of Use (TOU) as public multiplayer use, alterations or reupload may be prohibited!  
</p>

</details><details id="bkmrk-%5B4%5D-performance-%E2%AE%9E-wi"><summary>\[4\] Performance</summary>

**⮞ WILL COMMUNITY PACKS MAKE MY GAME LAG?** Performance loss with the community pack features has not been reported, but individual results may vary.

- Community Packs store text and coat files in your config file which will occupy storage space.
- Community Packs require your game to load and register these on load, which may marginally increase load times.
- Community Packs add new content into the game, similar to adding more and more mods it can impact performance.

<p class="callout info">PCs with limited resources or low performance may have a limit on how much custom content it can realistically support.</p>

</details>---

#### Using Community Packs

<p class="callout info">This section explains how to use **PREMADE** Community Packs \[1\] - see [Creators' Corner](https://wiki.swequestrian.com/books/swequestrian-mod/page/creators-corner-wip) to create your own.</p>

<p class="callout warning">Read **\[2\] Modifying Community Packs** before you edit any Community Pack files.</p>

To install your custom content, you need to download or create a Community Pack or Content Pack.

- You can install multiple packs if they have a unique and valid name such as `artist_packname`.
- Content packs will merge into community packs of the same name, or work as a new pack if one does not exist.

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> GENERATE THE CONFIG FOLDER**

This is only required the first time you add or update the 1.20.1-1.5+ mod file.

1. **\[Optional\]** Backup any existing saves files (recommended)
2. Install the latest 1.20.1-1.5 Beta file
3. Load the game to the menu screen
4. Exit the game

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> INSTALL THE COMMUNITY PACK**

1. Download or Create your Community Pack  
    → Free Official Community Pack can be found [here](https://discord.com/channels/715626418893095012/737144919717707896/1266908931423469609)!  
    → Free and Paid Community Packs can be found on many creators pages [here](https://discord.com/channels/715626418893095012/1198308571130122250)!
2. Check the file is ready to install  
    → See **\[1\] Community &amp; Content Packs** above (FAQ)
3. Copy the Community Pack
4. Go to `config > swem > community-packs`
5. Paste the Community Pack file  
    → It should look like: `config > swem > community-packs > artist_pack_name`

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> VIEW THE CONTENT IN-GAME**

1. Load the game
2. Load into a save or (recommended) a new test world
3. See relevant pages:  
    → [Coats](https://wiki.swequestrian.com/books/swequestrian-mod/page/coats-new)  
    → [Tack](https://wiki.swequestrian.com/books/swequestrian-mod/page/tack-wip)  
    → [Animations](https://wiki.swequestrian.com/books/swequestrian-mod/page/animations-wip)

---


#### Known Issues

If you find an issue, please report it to our bugs channel on [Discord](https://discord.com/channels/715626418893095012/898242623716855868). We ask that you look to see if your issue was reported first!

\- <span style="color: rgb(126, 140, 141);">**1.20.1-1.5.2**</span> Pasture Blankets (equipped) disappear on world reload.

---

#### Changelog

<details id="bkmrk-this-is-not-a-comple"><summary>View Changes</summary>

<p class="callout info">This is not a complete list of version changes / fixes. It is a changelog of relevant wiki-related version information.</p>

<table border="1" style="border-collapse: collapse; width: 100%; height: 129.188px;"><tbody><tr style="height: 29.7969px;"><td class="align-center" style="width: 13.3498%; height: 29.7969px;">**MC Version**</td><td class="align-center" style="width: 20.0247%; height: 29.7969px;">**Release**</td><td class="align-center" style="width: 66.6255%; height: 29.7969px;">**Notes**</td></tr><tr style="height: 29.7969px;"><td class="align-center" rowspan="4" style="height: 29.7969px; width: 13.3498%;">1.20.1  
</td><td style="width: 20.0247%; height: 29.7969px;">1.20.1-1.5.2</td><td style="width: 66.6255%; height: 29.7969px;">Bug Fix: Pasture Blankets not showing up on racks.</td></tr><tr style="height: 10px;"><td style="width: 20.0247%; height: 10px;">1.20.1-1.5.0</td><td style="width: 66.6255%; height: 10px;">Public Release: Added support for custom tack and animations.</td></tr><tr style="height: 29.7969px;"><td style="width: 20.0247%; height: 29.7969px;">1.20.1-1.5-beta-7</td><td style="width: 66.6255%; height: 29.7969px;">Bug Fix: Change JSON file formatting and fixed load errors.</td></tr><tr style="height: 29.7969px;"><td style="width: 20.0247%; height: 29.7969px;">1.20.1-1.5-beta-5</td><td style="width: 66.6255%; height: 29.7969px;">Public Release: Added support for custom coats.</td></tr></tbody></table>

</details>

# Creators' Corner [WIP]

## <span style="color: rgb(255, 255, 255);">**<span style="background-color: rgb(224, 62, 45);"> READ ME </span>**</span>

This page is an early **WORK IN PROGRESS** and information is subject to change or correction for any errors.   
It is public to accept feedback and external input from creators prior to final additions and corrections.  
**Please contact [Delphi](https://discord.com/channels/715626418893095012/736460598652567603/1310732774897881170) via SWEM DC for feedback or to contribute any resources to this guide!  
If you are a content creator with a video guide, I will gladly add links to help visual learners.**

---

#### Note To Content Creators

This update will support you in sharing your content to a wider audience, with or without coding experience.

- You will no longer need to create resource packs that override a limited number of default options for coat or tack.
- You can add limitless (within reason) options to expand the game without creating a separate mod (add-on).
- You can integrate your content into some existing features of the mod, such as coat cycling and breeding tags.

To properly transition towards community packs, we recommend:

- Read this page carefully to fully understand creating community packs.
- Create **simple, clear and easy to follow / enforce** Terms Of Use (TOU) if you share or sell your content.
- Upload content in a player-friendly format, such as Community Pack, Content Pack or standalone files.

<p class="callout info">You must read and follow the Content Creation Rules (below) to comply with SWEM's license and permitted use of assets.</p>

<details id="bkmrk-content-creation-rul"><summary>Content Creation Rules</summary>

**⮞ YOU <span style="text-decoration: underline;">MUST NOT</span> SELL (OR TRADE FOR PROFIT) ANY ASSETS CREATED AND OWNED BY SWEM**

`EXCEPTIONS MAY BE MADE ON AN INDIVIDUAL BASIS WITH EXPLICIT CONSENT FROM SWEM (ALAHARRANHONOR)`

- Modified versions of the horse model
- Modified versions of any blocks or items
- Modified version of **any** default coats
- Modified textures of any blocks or items
- Freely provided materials:  
    → Shading layers  
    → Rights to use standard techniques (eyes, nose, hoof etc)  
    → Template resource packs  
    → Template community packs  
    → JSON files (not in a working community pack)

**⮞ YOU <span style="text-decoration: underline;">MUST NOT</span> SELL (OR TRADE FOR PROFIT) OR REDISTRIBUTE ASSETS OF OTHER CREATORS**

`EXCEPTIONS MAY BE MADE WITH EXPLICIT CONSENT FROM THE CREATOR OR THEIR T.O.U`

- Modified textures
- Modified .json files that remove or alter credits
- Free resources  
    → Including the **Official Community Pack** (free) and any donated works from community artists

**⮞ YOU CAN PROVIDE** <span style="text-decoration: underline;">**FREE**</span> **CONTENT THAT ACCEPTS AN <span style="text-decoration: underline;">OPTIONAL</span> DONATION**

`COAT MODIFICATIONS ARE ONLY PERMITTED WITH WITH EXPLICIT CONSENT FROM SWEM (ALAHARRANHONOR)`

- Modified horse model and "breed add-ons"
- Modified .json files   
    → Altered breeding tags or coat cycling information

**⮞ YOU CAN SELL CONTENT THAT IS AT LEAST <span style="text-decoration: underline;">90%\*</span> YOUR OWN WORK**

`90% ACCOUNTS FOR THE 10% FAIRLY ACCREDITED TO SIMILAR ARTISTIC STYLE, INSPIRATION, REFERENCE OR COLOR PICKING`

- `You can sell content that is at least <strong>90%*</strong> <strong>your own work</strong>`  
    → Models for entities, blocks or items  
    → Textures for entities, including coats using the freely provided shading layer or standard features (eyes, nose, hoof etc)  
    → Textures for inventory icons of **custom content** using the default **pixel** **outline** (shape) of SWEM tack  
    → Textures for blocks or items  
    → Animations

<p class="callout warning">**Star Worm Equestrian is PG13: appropriate for users of all ages.**  
Any content or creators that modify it to be or appear otherwise do so against the terms of use for this project.</p>

**⮞ YOU <span style="text-decoration: underline;">MUST NOT</span> SELL, PROMOTE OR FEATURE SWEM IN ANY CONTENT <span style="text-decoration: underline;">OR MEDIA</span> THAT INCLUDES:**

- Extreme violence or gore
- Mature (18+) themes  
    → Including realistic anatomy or animations

</details><details id="bkmrk-terms-of-use-%28tou%29-y"><summary>Terms Of Use Information</summary>

##### **WARNING**

Creating a complicated or highly restrictive TOU will set you up for frustration when it is inevitably violated or misinterpreted.   
To protect your content within the **very limited legal recourse for TOUs** we encourage creators to share their creations in a similar way to mods; allow public or private use with minimal restrictions, provided the creator receives the download or support.

- If you choose to share your content publicly, it is your responsibility to clearly inform users of appropriate use.
- It is unreasonable to expect users to be remain informed of alterations to TOU **after the time of download.**
- It recommended to:  
    → Post your full TOU in a public source that can be accessed by anyone without membership or sign up/in.  
    → Include your TOU as a text file in any premade community packs.  
    → Include your TOU as a link or summary in any location your files are hosted or downloaded.

##### **RECOMMENDATIONS**

<p class="callout info">Avoid **requiring** credit for use in media; it should be encouraged but **no credits does not equal insult!**  
→ **It is not standard practice to credit every creation (ie mods)** in casual images; nice if you do, but optional!  
→ It should only be "required" to **credit where appropriate** (promotion, inspiration or reference), and **not falsely claim.**  
</p>

<p class="callout info">Avoid **prohibiting** inspiration or reference; **similarity is not proof of plagiarism!**  
→ It is possible for creators to have a similar idea, share the same reference, or take respectful inspiration!  
→ It should be expected that work(s) **clearly and** **directly** referenced or inspired by your creation is fairly credited.</p>

<p class="callout info">Avoid **restrictive** use policies that are difficult to monitor and enforce.  
→ It is an unfortunate reality that players +/- servers will violate agreements, especially if they are restrictive.  
→ There is limited legal recourse to address this; so state what you are **willing and able to action if necessary!**  
</p>

<p class="callout info">Consider providing content in a compact format with **minimal individual downloads**!  
→ Players and servers will be less likely to distribute (or more likely to use) **easily** accessible files.  
→ It is suggested to provide creator pack(s) in bundles such as 'Bays', 'Pintos', '2023 Coats'  
</p>

<p class="callout info">Avoid uploading to **unsecure file hosting sites** or encouraging users to engage in **unsafe internet habits**.  
→ It is recommended to use popular sites such as Kofi, Google Drive.</p>

---

##### **EXAMPLE TERMS OF USE <span style="color: rgb(230, 126, 35);">(NOT A LEGAL CONTRACT OR LICENSE)</span>**

- `OWNERSHIP & AGREEMENT`  
    → The creator (name) retains all rights of ownership to this content  
    → The right to use this content is granted to you (player) in accordance with this agreement
- `USE`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used in content (images, videos) - credits are optional but appreciated.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used privately in singleplayer or a small private group.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used publicly in multiplayer.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used in reasonable commercial services `with/without` consent.  
     ✅🚫 Offered as part of a service (ie random / selected coat change) requiring real money  
     ✅🚫 Offered as a prize or reward for activity or events requiring real money  
     ✅🚫 Offered as an unlock via crowdfunding or engagement (ie server cost covered -&gt; unlock)  
     **NOTE: Commercial services must abide by Minecraft's EULA**
- `DISTRIBUTION`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be reuploaded `<span style="color: rgb(45, 194, 107);">with</span>/without` consent `<span style="color: rgb(45, 194, 107);">and</span>/or` credits `and/or` payment.  
     ✅🚫 Limited private use by friends or small groups  
     ✅🚫 Custom Community Packs (folder)   
     ✅🚫 Custom Modpacks (zip)  
     ✅🚫 Exceptions: Paid vs Free, Commissions (paid) or Gifts (prizes)  
     ✅🚫 Other: File Hosting Sites, Discord Servers etc
- `ALTERATIONS`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be altered `with/<span style="color: rgb(45, 194, 107);">without</span>` consent and `<span style="color: rgb(45, 194, 107);">with</span>/without` credits for `<span style="color: rgb(45, 194, 107);">public/private</span>` use.  
     ✅🚫 Texture  
     ✅🚫 Information (json: name, description, color tags etc)  
     ✅🚫 Other conditions

</details>---

#### Updating A Community Pack

<p class="callout info">Official Community Pack version is updated to work with SWEM 1.5.2 - please use the Beta 5 pack found [here](https://discord.com/channels/715626418893095012/737144919717707896/1266908931423469609).</p>

If you have a custom coat community pack for 1.20.1-1.5-beta7, you must modify it to stay compatible in newest release.

1. Close Minecraft
2. Locate your community pack(s)
3. Go inside `packname > jsons > coats`
4. Open the first coat file in a text editor
5. Change `"legacy": "default:coats/legacy/coat_artist.png"` to `"legacy": "legacy/coat_artist.png"`
6. Save and close the file
7. Repeat for all coat files +/- all outdated packs

---

#### Creating A Community Pack

<p class="callout info">You can skip step 1-3 by downloading a template community pack found on our [Discord](https://discord.com/channels/715626418893095012/748632231257440336/1266941242630209589).</p>

<p class="callout info">You can skip or delete any folder that will not be used for your content (ie tack folders if you will not add any tack).</p>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"><span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> READ ME: </span></span><span style="color: rgb(255, 255, 255);"><span style="color: rgb(0, 0, 0);"> RESOURCES</span></span>**

<details id="bkmrk-%5Bexpand%5D-recommendat"><summary>\[EXPAND\] Recommendations</summary>

**⮞ REMOVE ANY UNUSED FOLDERS**

Consider removing folders that do not contain any content (ie tack folder from a coat only pack). This will not prevent the pack from working, but it will be smaller, tidier and much clearer to users on the content contained within.

**⮞ USE A STANDARD NAMING FORMAT**

This keeps your creations consistent, well organized and easy to identify as your work.  
**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"><span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> PACKS </span></span>** `artist_packname` Example: `arishant_freecoats`**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);">  
 COATS </span>** `coatname_artist` **Example:** `maple_arishant`  
**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> TACK </span>** See naming format resources below.

You might notice some items recommend credits before **or** after the name, this is for a few reasons!  
**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"><span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> PACKS </span></span>** Sorted alphabetically in folder and in-game, so packs group by artist instead of pack name  
**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COATS </span>** Listed alphabetically in game once filtered by pack. **Example:** `apple_artist / banana_artist / coconut_artist`  
**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> TACK </span>** Listed alphabetically in game, instead of by type. **Example:** `midnight_bridle / midnight_halter / midnight_saddle`

**⮞ USE A UNIQUE NAME FOR PACKS**

Naming a pack `koficoats` will work, but if another pack shares the same name they would merge together.   
If you use `artist_packname` it significantly reduces the chance of name duplication and folder merging.

**⮞ USE A UNIQUE NAME FOR FILES**

Naming a coat `coatname` or tack item `name_type` without artist will work, but it increases the risk of file replacement.  
Pack that use the same name and coats or tack with the same name, will **replace** existing files of the same name.

If you are an artist that offers different variations of content, always use a unique name.  
**Example:** 2 files both named `coatname_artist` but one with braids and one with roached mane will replace the other if a player chooses to use both options. If you named one `coatname_braids_artist` and the other `coatname_roached_artist` the player can choose to have one or both without replacing the other.

**⮞ USE CORE PACKS AND CONTENT PACKS**

If you want to make every pack unique, that's up to you. Example: `artist_pack1` `artist_pack2` `artist_pack3`  
However, if you create a lot of content this is going to be annoying for you to keep track of, and overwhelming to players.

Instead of using many packs with just one of two creations inside, consider using a core pack and offering add-ons via content packs. **This is explained more in a section further down!**

**⮞ REMOVE (OR RENAME) OUTDATED FILES**

If you fix and issue with a pack, file or texture it is recommended to remove the original download. If you want to keep it as a legacy version, consider renaming it (ie `coatname_artist_old`). Old files using the name name may replace newer ones if accidentally downloaded, or included in an outdated pack.

</details><details id="bkmrk-%5Bexpand%5D-how-it-shou"><summary>\[EXPAND\] File Structure Example</summary>

<table border="1" id="bkmrk-%F0%9F%93%82-config-%F0%9F%93%82swem-%F0%9F%93%82comm" style="border-collapse: collapse; width: 100%; height: 112.156px;"><colgroup><col style="width: 10.0124%;"></col><col style="width: 8.89988%;"></col><col style="width: 18.2942%;"></col><col style="width: 16.9345%;"></col><col style="width: 10.6304%;"></col><col style="width: 9.88875%;"></col><col style="width: 25.3399%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-left" rowspan="24" style="height: 52.7813px;">📂 config  
</td><td class="align-left" rowspan="24" style="height: 52.7813px;">📂swem  
</td><td class="align-left" rowspan="24" style="height: 52.7813px;">📂community-packs  
</td><td class="align-left" rowspan="24" style="height: 52.7813px;">📂artist\_packname  
</td><td class="align-left" rowspan="11" style="height: 29.7969px;">📂jsons  
</td><td class="align-left" style="height: 29.7969px;">📂coats

</td><td>🗒️`artist_coat.json` files

</td></tr><tr><td rowspan="10">📂tack

</td><td>📂blanket

</td></tr><tr><td>📂breast\_collar

</td></tr><tr><td>📂bridle

</td></tr><tr><td>📂girth\_strap

</td></tr><tr><td>📂halter

</td></tr><tr><td>📂horse\_armor

</td></tr><tr><td>📂leg\_wraps

</td></tr><tr><td>📂pasture\_blanket

</td></tr><tr><td>📂saddle

</td></tr><tr><td>📂saddle\_bag

</td></tr><tr style="height: 22.9844px;"><td rowspan="12" style="height: 22.9844px;">📂textures  
</td><td style="height: 22.9844px;">📂coats</td><td>🗒️`artist_coat.png` files</td></tr><tr><td rowspan="10">📂tack  
</td><td>📂blanket

</td></tr><tr><td>📂breast\_collar

</td></tr><tr><td>📂bridle

</td></tr><tr><td>📂girth\_strap

</td></tr><tr><td>📂halter

</td></tr><tr><td>📂horse\_armor

</td></tr><tr><td>📂leg\_wraps

</td></tr><tr><td>📂pasture\_blanket

</td></tr><tr><td>📂saddle

</td></tr><tr><td>📂saddle\_bag

</td></tr><tr><td>📂tokens</td><td>🗒️`token_name.png` files</td></tr><tr><td colspan="3">🗒️ tokens.json  
</td></tr><tr style="height: 59.375px;"><td colspan="7" style="height: 59.375px;"><p class="callout info">Shown: The file structure for community packs, including correct placement inside `config > swem > community-packs`</p>

</td></tr></tbody></table>

</details>**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> CREATE THE PACK FOLDER STRUCTURE**

1. Create a new folder   
    → It can be in `config > swem > community-packs` or somewhere else (move later)
2. Name your community pack  
    → It must be in lowercase letters with no spaces  
    → It is recommended to use `artist_packname` such as `yourname_kofi` or `yourname_bays`
3. Go inside the empty folder
4. Create two new folders here  
    → `jsons` to store the information files  
    → `textures` to store the coat and tack files

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> CREATE THE JSONS FOLDER STRUCTURE**

1. Go inside the empty `jsons` folder
2. Create two new folders here  
    → `coats` to store **.json** information files for coats  
    → `tack` to store **.json** information files for tack
3. Go inside the empty `tack` folder
4. Create 10 new folders here  
    → `blanket`  
    → `breast_collar`  
    → `bridle`  
    → `girth_strap`  
    → `halter`  
    → `horse_armor`  
    → `leg_wraps`  
    → `pasture_blanket`  
    → `saddle`  
    → `saddle_bag`

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> CREATE THE TEXTURES FOLDER STRUCTURE**

1. Go inside the empty `textures` folder
2. Create two new folders here  
    → `coats`   
    → `tack`
3. Go inside the empty `coats` folder
4. Create one new folder here:  
    → `legacy` to store **.png** texture files for coats
5. Go inside the empty `tack` folder
6. Create 10 new folders here  
    → `blanket`  
    → `breast_collar`  
    → `bridle`  
    → `girth_strap`  
    → `halter`  
    → `horse_armor`  
    → `leg_wraps`  
    → `pasture_blanket`  
    → `saddle`  
    → `saddle_bag`

---

#### Creating A Content Pack

<p class="callout info">If you are making a pack for personal use, you can skip this. Content packs are aimed at Creators providing expansion content.</p>

A Content Pack is exactly the same as a community pack, but differs in how and why it is used.

- Content Packs use the same name as a 'core' community pack.
- Content Packs merge into any packs with the same name, or work as a standalone if one does not exist.
- Content Packs usually include less content, or content bundled by theme (ie Black Coats, Bay Coats)

<details id="bkmrk-%5Bexpand%5D-content-pac"><summary>\[EXPAND\] Content Packs Example</summary>

If you create a lot of content, you probably do not want to provide ALL of your coats in a single bundle, or maintain lots of individually named packs. This would quickly get confusing and difficult should any packs require a fix to files or textures.

Let's say you decide that your core pack will be `yourname_koficoats`. Each time you create a new coat, you will provide that coat in its own pack, using that name. You set it up like a normal community pack, and if a player downloads it it will work in-game when pasted into the community pack folder.

If you then create another new coat, you do the same thing; make a community pack named `yourname_koficoats` with just the NEW coat file and texture. If a player downloads that file and pastes it into the community pack folder, **it will merge into any pack folders that share the same name.**

This means you can offer optional content that players can pick and choose which files they want. They don't need to download any requirements, every pack will work on its own, or merge with others if they already exist.

<p class="callout warning">Unfortunately, downloads get renamed if they have the same name, ie `artist_pack [1]` and `artist_pack [2]`  
→ There is no way to avoid this without **downloading packs one at a time**, or manually renaming them to merge files.  
</p>

</details>---

#### Creating Content

If you followed the guide above, you have a basic community pack, but it needs content to work in game.

Community Packs can support custom coats, tack and animations - this can be all in one pack, or split into separate packs.

---

#### Adding Custom Coats

This guide will not cover how to create a coat, for information please read our [resources](https://discord.com/channels/715626418893095012/748632231257440336/1117996750842630194) on Discord.

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> CREATE OR DOWNLOAD A CUSTOM COAT**

1. Save or rename the file as `artist_coatname`  
    → The file type should display as `PNG File`
2. Paste this file into your community pack `artist_packname > textures > coats > legacy > coatname_artist.png`

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> CREATE A JSON FILE**

1. 1. Open a blank text editor file using Notepad (Windows) or TextEdit (Mac)
    2. Paste in the coat template code (below)
    3. Edit the template to your coat  
        → `credits` the name of the coat artist(s) **✅** `"credits": "Arishant",`   
        → `inspiration` optional notes on inspiration or reference **✅** `"inspiration": "Esperanza from Spirit",`   
        → `models` the texture path (location) for **legacy model** **✅** `"legacy": "legacy/esperanza_arishant_legacy.png"`  
        → `lapis_cyclable` if the coat can be cycled using lapis or redstone `true` or `false`  
        → `obtainable_by_breeding` if the coat can appear from a (bred) foal `true` or `false`  
        → `base_colors` which color tags the coat uses **✅** `["black","gray"]` **✅** `"base_colors": ["creamy"]`
    4. Save the file as a .json file by using `save as` and naming the file `artist_coatname.json`  
        → The file type should display as `JSON File`
    5. Paste this file into your community pack `artist_packname > jsons > coats > coatname_artist.json`

<details id="bkmrk-%5Bexpand%5D-coat-templa"><summary>\[EXPAND\] Coat Template</summary>

{  
 "credits": "Artist(s)",  
 "inspiration": "N/A",  
 "models": {  
 "legacy": "legacy/coatname\_artist\_legacy.png"  
 },  
 "lapis\_cyclable": true,  
 "obtainable\_by\_breeding": true,  
 "base\_colors": \["black","gray","white","creamy","brown","dark\_brown","chestnut"\]  
}

</details><details id="bkmrk-%5Bexpand%5D-info-%26-comm"><summary>\[EXPAND\] Info &amp; Common Mistakes</summary>

**⮞ LEGACY MODEL**

Legacy model is the current horse model in game, but more models are planned in future.

- Texture must use the `legacy` model texture path
- Future model types may come pre-listed listed, but do not function in game

**⮞ TEXTURE PATH** Texture path is the location of the coat file placed in `artist_packname > jsons > coats > legacy > coatname_artist.png`

- Texture path must match the exact name of the coat png file  
    → Must be a lowercase name with no spaces or symbols  
    → Can include numbers or underscores   
    → Should use the format `artist_coatname` or `artist_coatname_legacy` to indicate it uses original model  
    → Should share the same or similar name as the json file

**⮞ COAT CYCLING** Coat cycling is the function that allows a player to cycle through coat options by right clicking a horse with redstone or lapis.

- Cycling a coat will only work if:  
    → Set to `"lapis_cyclable": true,` in the json file  
    → Coat cycling is enabled in server config `allowCoatCycling = true`   
    → Coat is not blacklisted in server config `blacklistedCoatIds`  
    → Server config is per-world; enabling settings in one world does not auto-apply it to others!
- Summoning a (random) coat via command will only work if:  
    → Set to `"lapis_cyclable": true,` in the json file  
    → Coat is not blacklisted in server config `blacklistedCoatIds`

**⮞ BREEDING &amp; COLOR TAGS**

- Color tags must use at least one of 7 valid choices:   
    → `["black","gray","white","creamy","brown","dark_brown","chestnut"]`  
    → Separate multiple tags with a comma  
    → There must not be a comma between `"` and `]`
- Coats can appear from converting horses if:  
    → Coat has at least one valid color tag  
    → Coat has the same color tag as the vanilla horse (randomly chooses from coat options)  
    → Set to `"obtainable_by_breeding": true,` in the json file  
    → Converting is enabled in server config file (default) `tokensBreeding = false`  
    → Coat is not blacklisted in server config `blacklistedCoatIds`  
    → Server config is per-world; enabling settings in one world does not auto-apply it to others!
- Coats can appear from breeding if:  
    → Set to `"obtainable_by_breeding": true,` in the json file  
    → Coat is not blacklisted in server config `blacklistedCoatIds`  
    → Foals are assigned one tag from any their parents have and use one of 7 foal coats (one per tag)  
    → Foals choose from a random adult coat with the same tag when they grow up
- Color tags and breeding outcomes are **very basic** and do not support realistic genetics  
    → Setting tags you expect the horse to 'pass on' is more likely to get your coat **from** those tags.  
    → **Example:** Bay coat with "chestnut", "black", "brown" - any chestnut, black or brown foal can grow up to use it.  
    → Setting tags for any color a coat has a small amount of will result in dramatic changes from foal to adult coats.  
    → **Example:** Leopard Appaloosa with "black", "white" - a fully black foal would grow up to a mostly white coat.

<p class="callout info"> **RECOMMENDATION** → Set **one or two** tag(s) for a foal color you would expect to get the coat from **Example:** Black Foal -&gt; Black Horse </p>

</details>**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> TEST YOUR COMMUNITY PACK**

1. 1. Paste the community pack file in `config > swem > community-packs`  
        → Read [here](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip#bkmrk-community-packs) if this is your first time installing a community pack.
    2. Load the game
    3. Open a test world with cheats enabled
    4. Type `/swem summon LEGACY`  
        → Your pack should be listed in the options  
        → It may be above or below the default `swem:` options  
        → If your pack is not listed, you have made an error
    5. Select your coat and enter the command
    6. Check the coat has the expected texture.

If this worked as expected, you can repeat Step 1 + 2 to add additional coats to the pack.

<details id="bkmrk-%5Bexpand%5D-troubleshoo"><summary>\[EXPAND\] Troubleshooting Errors</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMMUNITY PACK TROUBLESHOOTING </span>  
FOLLOW <span style="text-decoration: underline;">EACH STEP</span> CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP <span style="text-decoration: underline;">AFTER</span> USING THIS!**

**⮞ \[1\] MOD VERSION**

- **Double check** you are using the latest 1.20.1 Beta version.  
    **→** Even if you feel sure, go and check it. It's the most common error!  
    **→** `Curseforge App` Will not auto-install beta files, go to `mod's page > versions > install`  
    **→** `Multiplayer Servers` Check server is on latest release  
    **→** `Multiplayer Users` Check client + server use same version  
    ⚠️ **Community Packs are for 1.20.1-1.5 and above only.**

⮞ **\[2\] OFFICIAL COMMUNITY PACK VERSION**

- Skip this step if you are not using the official Community Pack.  
    **→** Check you have `swem_community_pack_beta_5` or above.  
    **→** Check this is the latest version posted - it may have a new release!  
    **→** `Multiplayer Servers` Check server has the correct pack  
    **→** `Multiplayer Users` Check clients have the same pack name + contents as server

**⮞ \[3\] COMMUNITY PACK LOADING**

- Open the game and load into a world
- Type `/swem summon LEGACY`  
    **→** Is the pack listed?   
    **→** Is **any** pack listed (excluding `swem:`)  
      
    ✅ Pack(s) are recognized  
    **❌** Pack(s) are not recognized, specific packs are invalid or have no valid files. **Go to solutions \[3\].**

**⮞ \[4\] COAT REGISTERED**

- Type `/swem summon LEGACY packname:`  
    **→** Is the coat(s) you expect to see listed? **Example** `kofi_coats:spirit_arishant_legacy`  
      
    ✅ Coat(s) have registered.  
    **❌** Coats have not registered OR specific coat(s) are invalid. **Go to solutions \[4\].**

**⮞ \[5\] JSON -&gt; TEXTURE PATH**

- Summon coat(s) from the pack  
    **→** Do coat(s) have a texture that is correct for that horse?  
      
    ✅ Coat(s) have the correct texture  
    **❌** `Black Texture` Texture path or file name is invalid or missing. **Go to solutions \[5\].  `Multiplayer` Player is missing the pack or no texture for that coat path. **Go to solutions \[5\].**  
    **❌** `Wrong Coat` Texture path or file name is incorrect. **Go to solutions \[4\]. ❌** `Looks Wrong` Texture or UV map error. **Contact Coat Artist or request help.**

**⮞ \[6\] OTHER**

- `Lapis Cycling`   
    **→** If you cannot cycle **any** coats using lapis or redstone, it is disabled in server config.  
    **→** If you can cycle coats, but some options are missing, it is disabled in the coat **.json** file.
- `White Texture`   
    **→** If a coat is white, the pack or coat .json files were removed or renamed  
    **→** If that is not the case, information in .json may have an error (invalid format) **Go to solutions \[5\].**
- `Texture Error`  
    **→** If a coat appears broken (color in wrong places, missing pixels, marker blocks) it needs a texture or UV fix.  
    **→** If you are not the coat artist, contact the original creator.
- `Error On Load / Crashing`   
    **→** Too many potential causes **→** Paste your **latest.log** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord with a description of the issue(s).

  
<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **SOLUTIONS &amp; SUGGESTIONS** </span>**ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES**

<p class="callout warning">**It is not recommended to modify packs from a Creator <span style="text-decoration: underline;">unless</span> you intend to customize it and solve any issues.**  
✅ You should follow this troubleshooting guide to identify your likely issue first.  
✅ You should notify Creator's of potential problems with the **default pack** (might need a fix or update).  
**❌** You should NOT expect Creator's to troubleshoot an issue you might have caused by altering files!</p>

**⮞ ISSUE \[3\]**

- Check the community pack:  
    → Pack is directly in `config > swem > community-packs`   
    → Pack is a **folder** and not a zip file! **→** Pack has a valid **lowercase** name with **no spaces** ✅`artist_kofi` **❌** `Artist Kofi Coats`  
    **→** Pack includes at least one `.json` and `.png` file in the **correct folder**  📁 jsons &gt; 📁 coats &gt; `JSON FILES HERE`  
     📁 textures &gt; 📁 coats &gt; 📁 legacy &gt; `PNG FILES HERE`  
      
    If this is **ALL** correct the issue is not the community pack structure. **Go back to Step \[4\] above.**

**⮞ ISSUE \[4\]**

- Identify a coat that is missing in game
- Check the **.json** file for the coat  
    → File is listed as a `JSON File` type  
    → File is directly in `community-packs > artist_packname > jsons > coats`  
    → File has a valid **lowercase** name with **no spaces** ✅`coatname_artist` **❌** `Coat - Artist`  
    → File texture path uses ✅ `"legacy": "legacy/coatname_artist.png"` **❌** `"legacy": "default:legacy/`  
      
    If this is correct, the most likely issue is formatting (invalid json).  
    → Compare your json to the template and note any missing `"` `,` or `{ }` or different indentation  
    → If unsure, delete and rewrite the .json file using a blank template  
    → Reload the game and repeat **Step \[4\]** above.  
      
    If this is **ALL** correct or changes did not work, paste your **.json** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord

**⮞ ISSUE \[5\]**

- Identify a coat with a black (missing) texture
- Check the **.json** file for the coat  
    → File uses `legacy` model line (not any for future models)  
    → File texture path uses ✅ `"legacy": "legacy/coatname_artist.png"` **❌** `"legacy": "<strong>default:</strong>legacy/`  
    → File texture path has the **exact** name used by the coat texture **.png** file
- Check the .png file for the coat  
    → File is listed as a `PNG File` type  
    → File is directly in `community-packs > artist_packname > textures > coats > legacy`  
    → File has a valid **lowercase** name with **no spaces** ✅`coatname_artist` **❌** `Coat - Artist`
- `MULTIPLAYER SERVERS`  
    → Client (player) has community pack(s) with the same name (ID) as those on the server.   
    → Client (player) has **.png** files with the same names as those in the server pack.  
      
    If you cannot check this due to permissions, you will need to contact server admins.

**⮞ \[6\] OTHER <span style="text-decoration: underline;">OR</span> NOTHING WORKED**

- Create a post in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord  
    → Describe your issue(s) and **what you have tried** → Upload your latest.log file to provide info that may help others assist you  
     **DO NOT UPLOAD PAID/PRIVATE PACKS WITH TEXTURES FROM CREATORS WITHOUT CONSENT**

</details>
---

#### Adding Custom Tack

This guide will not cover how to create tack, for information please read our <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> \[RESOURCES\] </span> on Discord.

<details id="bkmrk-%5Bexpand%5D-file-naming"><summary>\[EXPAND\] Files &amp; Naming Format</summary>

<p class="callout info">This is the standard format used in the Beta pack. It is recommended to use a consistent naming format as shown here.</p>

<table border="1" style="border-collapse: collapse; width: 100%; height: 1083.63px;"><colgroup><col style="width: 11.9901%;"></col><col style="width: 33.993%;"></col><col style="width: 54.0168%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Type**</span></td><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Texture + Name**</span></td><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Comment**</span></td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">**Bridle**</td><td style="height: 30.1094px;">`name_bridle_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_bridle_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_bridle_bit_legacy`</td><td style="height: 30.1094px;">Horse Texture </td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_bridle_name_blanket`  
</td><td style="height: 30.1094px;">Bridle Rack Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">**Blanket**  
</td><td style="height: 30.1094px;">`name_blanket_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_blanket_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_saddle_name_blanket`  
</td><td style="height: 30.1094px;">Saddle Rack Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_saddle_5_name_blanket`</td><td style="height: 30.1094px;">Blanket Rack (5X) Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">**Saddle**</td><td style="height: 30.1094px;">`name_saddle_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_saddle_legacy`</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_saddle_name_saddle`</td><td style="height: 30.1094px;">Saddle Rack Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_horse_armor_name_saddle`  
</td><td style="height: 30.1094px;">Armor Rack Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="3" style="height: 90.3282px;">**Girth Strap**</td><td style="height: 30.1094px;">`name_girth_strap_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_girth_strap_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_saddle_name_girth_strap`  
</td><td style="height: 30.1094px;">Saddle Rack Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="2" style="height: 60.2188px;">**Breast Collar**  
</td><td style="height: 30.1094px;">`name_breast_collar_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_breast_collar_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="3" style="height: 90.3282px;">**Leg Wraps**  
</td><td style="height: 30.1094px;">`name_leg_wraps_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_leg_wraps_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_leg_wraps_hoof_legacy`</td><td style="height: 30.1094px;">Horse Texture (hoof)</td></tr><tr style="height: 30.1094px;"><td rowspan="2" style="height: 60.2188px;">**Saddlebag**  
</td><td style="height: 30.1094px;">`name_saddle_bag_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_saddle_bag_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">**Horse Armor**</td><td style="height: 30.1094px;">`name_horse_armor_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_horse_armor_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_horse_armor_wings_legacy`</td><td style="height: 30.1094px;">Horse Texture **Optional (Default: Amethyst Tier)**</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_horse_armor_name_horse_armor`</td><td style="height: 30.1094px;">Armor Rack Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="3" style="height: 90.3282px;">**Halter**</td><td style="height: 30.1094px;">`name_halter_icon`  
</td><td style="height: 30.1094px;">Inventory Icon</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_halter_legacy`  
</td><td style="height: 30.1094px;">Horse Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_halter_lead_name_halter`  
</td><td style="height: 30.1094px;">Lead Rack Texture</td></tr><tr style="height: 30.1094px;"><td rowspan="6" style="height: 180.656px;">**Pasture Blanket**  
</td><td style="height: 30.1094px;">`name_pasture_blanket_icon`</td><td style="height: 30.1094px;">Inventory Icon **Optional (One or Both)**</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_pasture_blanket_armored_icon`  
</td><td style="height: 30.1094px;">Inventory Icon **Optional (One or Both)**</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_pasture_blanket_legacy`</td><td style="height: 30.1094px;">Horse Texture **Optional (One or Both)**</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`name_pasture_blanket_armored_legacy`  
</td><td style="height: 30.1094px;">Horse Texture **Optional (One or Both)**</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_pasture_blanket_3_short_name`</td><td style="height: 30.1094px;">Pasture Blanket Rack (3X) Texture</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`rack_pasture_blanket_5_long_name`</td><td style="height: 30.1094px;">Pasture Blanket Rack (5X) Texture</td></tr></tbody></table>

</details>**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> CREATE OR DOWNLOAD TACK ICONS**

This is the icon that will display in inventory slots of when held in hand. Each tack item needs ONE icon.

1. Save or rename the files as `name_type_icon`  
    → Use the recommended naming in **Files &amp; Naming Format** above.  
    → Name should relate to in-game name **✅** Midnight Saddle → `midnight_saddle_icon`  
       
    → Type should match a valid tack type **✅ `midnight_blanket_icon` `midnight_girth_strap_icon`  
    → The file type should display as `PNG File`  
    → Icons should be default 16 x 16 pixels
2. Paste this file into your community pack `artist_packname > textures > tack > [type] > name_type_icon.png`  
    → Type should use the relevant folder **Example** Midnight Saddle → `textures > tack > saddle`

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> CREATE OR DOWNLOAD TACK TEXTURES**

This is the texture for the tack on the horse. Note, there are a few optional variations:

- Bridles need a texture for both the 2D components **and** the 3D bit.
- Leg wraps require `leg_wraps` **and** `leg_wraps_hoof` for hoof rendered textures.
- Horse armor has `horse_armor` for default tiers up to diamond and `horse_armor_wings` for default amethyst tier  
    → Custom armor can support wings **without** being amethyst tier, **or** non-winged armor at amethyst tier.
- Pasture Blanket has `pasture_blanket` (cosmetic only) and `pasture_blanket_armored` with amethyst tier armor protection.

1. Save or rename the files as `name_type_artist`   
    → Name and Type means the same as in Step One.  
    → Legacy is optional, but recommended to indicate it is for the original horse model.  
    → The file type should display as `PNG File`
2. Paste this file into your community pack `artist_packname > textures > tack > [type] > name_type_artist.png`  
    → Type means the same as in Step One.

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> CREATE OR DOWNLOAD RACK TEXTURES**

This is the texture for the tack on compatible storage racks. Not all tack supports rack storage.

- Bridles and halters can be stored on [Bridle Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/bridle-rack) `rack_bridle`
- Halters can be stored on [Halter &amp; Lead Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/halter-lead-rack) `rack_halter_lead`
- Blankets (Saddle Pads) can be stored on [Blanket Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/blanket-racks) `rack_saddle_5`
- Saddles, Blankets (Saddle Pads) and Girth Straps can be stored on [Saddle Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/saddle-rack) `rack_saddle`
- Saddles and Horse Armor can be stored on [Armor Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/horse-armor-rack) `rack_horse_armor`
- Pasture Blankets can be stored on [Pasture Blanket Racks](https://wiki.swequestrian.com/books/swequestrian-mod/page/pasture-blanket-racks) `rack_pasture_blanket_3_short` `rack_pasture_blanket_5_long`
- Breast Collars, Leg Wraps and Saddle bags do not support any tack storage racks.

Rack textures are **default** for blankets (saddle pads), girth straps and pasture blanket.

- They can support a premade grayscale template with a color overlay.
- The texture template can be copied from `assets > swem > textures > block`
- The color code (RGB code) is specified in the tack `.json` file
- You can make a custom texture instead; retexture the template.
- If you create a custom texutre, use \[255, 255, 255\] (white) overlay in .json to disable the overlay.
- If you create a custom grayscale texture, use the RGB color overlay as normal.

Rack textures are **custom** for bridles, halters, saddles and horse armor.

- <span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> **\[TBC\]** </span> They use a modified version of the horse tack texture.
- <span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> **\[TBC\]** </span> This can be found in...

1. Save or rename the files as `racktype_name_type`  
    → Name and Type means the same as in Step One.  
    → Rack Type means the compatible storage type (see list above)  
    → The file type should display as `PNG File`
2. Paste this file into your community pack  
     → `artist_packname > textures > tack > [type] > racktype_name_type_artist.png`  
    → Type means the same as in Step One.

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP FOUR: </span> CREATE JSON FILE(S)**

This is the information file that registers custom tack as an item in game, and specifies its properties.

1. Open a blank text editor file using Notepad (Windows) or TextEdit (Mac)
2. Copy the template code for your tack item (below)
3. Edit the template to your coat  
    → You only need to edit the <span style="color: rgb(132, 63, 161);">**BOLDED PURPLE**</span> text - leave the rest unless you know what you're doing!  
    → `credits` the name of the texture artist(s) **✅** `"credits": "Arishant",`   
    → `inspiration` optional notes on inspiration or reference **✅** `"inspiration": "Midnight Tack Set",`   
    → `coin` tier of coin required to purchase at EQ Shop**✅** `"coin": "iron"`  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** Valid tiers are `copper` &gt; `iron` &gt; `emerald` &gt; `gold` &gt; `diamond` &gt; `netherite` &gt; `amethyst`  
    → `amount` number of tokens required to purchase at EQ Shop **✅** `"amount": <span style="color: rgb(0, 0, 0);">2</span>`  
    → `name` item name (ID) in **lowercase** letters **✅** `"name": <span style="color: rgb(0, 0, 0);">"midnight</span><span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">_bridle</span></span>"`  
    → `icon` texture path for the inventory icon **✅** `"icon": "bridle/midnight<span style="color: rgb(0, 0, 0);">_bridle_icon</span>.png"`  
    → `type` the tack type and tack slot it is equipped in **✅** `"type": "bridle"`  
    → `model_type` if it is western or english tack (specific items) - input ONE type **✅** `"model_type": "western"`  
    → `color` RGB color code overlay for rack textures (specific items) **✅** `"color": [0, 51, 102],` &lt;- Dark Blue  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** Custom rack textures should use a white overlay \[255, 255, 255\] to not alter colors.   
    → `tier` tier of horse armor (inherits the [benefits](https://wiki.swequestrian.com/books/swequestrian-mod/page/horse-armor) of all previous tiers) **✅** `"tier": "amethyst"`  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** Valid tiers are `cloth` &gt; `iron` &gt; `gold` &gt; `diamond` &gt; `amethyst`   
    → `can_wear_armor` if it supports [armor equipping](https://wiki.swequestrian.com/books/swequestrian-mod/page/horse-armor#bkmrk-usage-16) (specific items) - set to true or false **✅** `"can_wear_armor": false`→ `textures` texture path for the horse texture **✅** `"bridle": "bridle/midnight<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">_bridle<strong>_</strong>bit_legacy</span></span>.png"`  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** The path and textures required vary by tack type - only modify the template where shown!   
    → `rack` texture path for tack storage racks (specific items) **✅** `"bridle": "bridle/<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">rack_bridle_</span></span>name<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">_bridle</span></span>.png"`  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** The path and supported storage racks vary by tack type - only modify the template where shown!
4. Save the file as a .json file by using `save as` and naming the file `name_type.json`  
    → Use the **Files &amp; Naming Format** guide (above)  
    → The file type should display as `JSON File`
5. Paste this file into your community pack `artist_packname > jsons > tack > [type] > name_type.json`  
    → Type should use the relevant folder **Example** Midnight Bridle → `textures > tack > bridle`

<details id="bkmrk-%5Bexpand%5D-bridle-temp"><summary>\[EXPAND\] Bridle Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name </span>**<span style="color: rgb(0, 0, 0);">Bridle</span>",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**iron**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">2</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">\_bridle</span></span>",  
 "icon": "bridle/**<span style="color: rgb(132, 63, 161);">name</span>**<span style="color: rgb(0, 0, 0);">\_bridle\_icon</span>.png",  
 "type": "bridle",  
 "data": {  
 "model\_type": "**<span style="color: rgb(132, 63, 161);">western / english (select one)</span>**",  
 "can\_wear\_armor": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "bridle": "bridle/<span style="color: rgb(132, 63, 161);">**name**<span style="color: rgb(0, 0, 0);">\_bridle**\_**bit\_legacy</span></span>.png",  
 "halter": "bridle/<span style="color: rgb(132, 63, 161);">**name**<span style="color: rgb(0, 0, 0);">\_bridle\_legacy</span></span>.png"  
 }  
 },  
 "rack": {  
 "bridle": "bridle/<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">rack\_bridle\_</span>**name**<span style="color: rgb(0, 0, 0);">\_bridle</span></span>.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-blanket-tem"><summary>\[EXPAND\] Blanket Template (Saddle Pad)</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name </span>**<span style="color: rgb(0, 0, 0);">Blanket</span>",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**iron**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">2</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**<span style="color: rgb(0, 0, 0);">\_blanket</span>",  
 "icon": "blanket/**<span style="color: rgb(132, 63, 161);">name</span>**<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">\_blanket\_icon</span></span>.png",  
 "type": "blanket",  
 "data": {  
 "color": \[**<span style="color: rgb(132, 63, 161);">255, 190, 0</span>**\],  
 "can\_wear\_armor": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "blanket": "blanket/<span style="color: rgb(132, 63, 161);">**name**<span style="color: rgb(0, 0, 0);">\_blanket\_legacy</span></span>.png"  
 }  
 },  
 "rack": {  
 "saddle": "blanket/<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">rack\_saddle\_</span>**name**<span style="color: rgb(0, 0, 0);">\_blanket</span></span>.png",  
 "blanket\_5": "blanket/<span style="color: rgb(132, 63, 161);"><span style="color: rgb(0, 0, 0);">rack\_blanket\_5\_</span>**name**<span style="color: rgb(0, 0, 0);">\_blanket</span></span>.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-saddle-temp"><summary>\[EXPAND\] Saddle Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name </span>**<span style="color: rgb(0, 0, 0);">Saddle</span>",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**gold**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">4</span>**  
 },  
 "meta": {  
 "name": "<span style="color: rgb(132, 63, 161);">**name**</span>\_saddle",  
 "icon": "saddle/<span style="color: rgb(132, 63, 161);">**name**</span>\_saddle\_icon.png",  
 "type": "saddle",  
 "data": {  
 "model\_type": "**<span style="color: rgb(132, 63, 161);">western / english (select one)</span>**",  
 "can\_wear\_armor": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "saddle": "saddle/<span style="color: rgb(132, 63, 161);">**name**</span>\_saddle\_legacy.png"  
 }  
 },  
 "rack": {  
 "saddle": "saddle/rack\_saddle\_<span style="color: rgb(132, 63, 161);">**name**</span>\_saddle.png",  
 "horse\_armor": "saddle/rack\_horse\_armor\_<span style="color: rgb(132, 63, 161);">**name**</span>\_saddle.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-girth-templ"><summary>\[EXPAND\] Girth Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Girth Strap",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**copper**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">3</span>**  
 },  
 "meta": {  
 "name": "<span style="color: rgb(132, 63, 161);">**name**</span>\_girth\_strap",  
 "icon": "girth\_strap/<span style="color: rgb(132, 63, 161);">**name**</span>\_girth\_strap\_icon.png",  
 "type": "girth\_strap",  
 "data": {  
 "color": \[**<span style="color: rgb(132, 63, 161);">255, 190, 0</span>**\],  
 "can\_wear\_armor": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "girth\_strap": "girth\_strap/<span style="color: rgb(132, 63, 161);">**name**</span>\_girth\_strap\_legacy.png"  
 }  
 },  
 "rack": {  
 "saddle": "girth\_strap/rack\_saddle\_<span style="color: rgb(132, 63, 161);">**name**</span>\_girth\_strap.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-breast-coll"><summary>\[EXPAND\] Breast Collar Template</summary>

{  
 "display": {  
 "name": "<span style="color: rgb(132, 63, 161);">**Name**</span> Breast Collar",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**copper**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">5</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_breast\_collar",  
 "icon": "breast\_collar/**<span style="color: rgb(132, 63, 161);">name</span>**\_breast\_collar\_icon.png",  
 "type": "breast\_collar",  
 "data": {  
 "can\_wear\_armor": true  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "breast\_collar": "breast\_collar/**<span style="color: rgb(132, 63, 161);">name</span>**\_breast\_collar\_legacy.png"  
 }  
 },  
 "rack": {  
 "blanket": ""  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-leg-wraps-t"><summary>\[EXPAND\] Leg Wraps Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Wraps",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**iron**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">1</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_leg\_wraps",  
 "icon": "leg\_wraps/**<span style="color: rgb(132, 63, 161);">name</span>**\_leg\_wraps\_icon.png",  
 "type": "leg\_wraps",  
 "data": {  
 "can\_wear\_armor": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "leg\_wraps": "leg\_wraps/**<span style="color: rgb(132, 63, 161);">name</span>**\_leg\_wraps\_legacy.png",  
 "hoof": "leg\_wraps/**<span style="color: rgb(132, 63, 161);">name</span>**\_leg\_wraps\_hoof\_legacy.png"  
 }  
 },  
 "rack": {  
 "blanket": ""  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-saddle-bag-"><summary>\[EXPAND\] Saddle Bag Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Saddle Bag",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**gold**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">1</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_saddle\_bag",  
 "icon": "saddle\_bag/**<span style="color: rgb(132, 63, 161);">name</span>**\_saddle\_bag\_icon.png",  
 "type": "saddle\_bag",  
 "data": {  
 "color": \[**<span style="color: rgb(132, 63, 161);">255, 190, 0</span>**\]  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "saddle\_bag": "saddle\_bag/**<span style="color: rgb(132, 63, 161);">name</span>**\_saddle\_bag\_legacy.png"  
 }  
 },  
 "rack": {

 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-horse-armor"><summary>\[EXPAND\] Horse Armor Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Horse Armor",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**amethyst**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">4</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_horse\_armor",  
 "icon": "horse\_armor/**<span style="color: rgb(132, 63, 161);">name</span>**\_horse\_armor\_icon.png",  
 "type": "horse\_armor",  
 "data": {  
 "tier": "**<span style="color: rgb(132, 63, 161);">amethyst</span>**"  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "armor": "horse\_armor/**<span style="color: rgb(132, 63, 161);">name</span>**\_horse\_armor\_legacy.png",  
 "wings": "horse\_armor/**<span style="color: rgb(132, 63, 161);">name</span>**\_horse\_armor\_wings\_legacy.png"  
 }  
 },  
 "rack": {  
 "horse\_armor": "horse\_armor/rack\_horse\_armor\_**<span style="color: rgb(132, 63, 161);">name</span>**\_horse\_armor.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-halter-temp"><summary>\[EXPAND\] Halter Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Halter",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**emerald**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">4</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_halter",  
 "icon": "halter/**<span style="color: rgb(132, 63, 161);">name</span>**\_halter\_icon.png",  
 "type": "halter",  
 "data": {  
 "color": \[<span style="color: rgb(132, 63, 161);">**255, 190, 0**</span>\],  
 "can\_wear\_armor": <span style="color: rgb(132, 63, 161);">**true**</span>  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "halter": "halter/**<span style="color: rgb(132, 63, 161);">name</span>**\_halter\_legacy.png"  
 }  
 },  
 "rack": {  
 "halter\_lead": "halter/rack\_halter\_lead\_**<span style="color: rgb(132, 63, 161);">name</span>**\_halter.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-pasture-bla"><summary>\[EXPAND\] Pasture Blanket Template</summary>

{  
 "display": {  
 "name": "**<span style="color: rgb(132, 63, 161);">Name</span>** Pasture Blanket",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**emerald**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">4</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket",  
 "icon": "pasture\_blanket/**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket\_icon.png",  
 "type": "pasture\_blanket",  
 "data": {  
 "color": \[**<span style="color: rgb(132, 63, 161);">255, 190, 0</span>**\]  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "pasture\_blanket": "pasture\_blanket/**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket\_legacy.png"  
 }  
 },  
 "rack": {  
 "pasture\_blanket\_long\_5": "pasture\_blanket/rack\_pasture\_blanket\_5\_long\_**<span style="color: rgb(132, 63, 161);">name</span>**.png",  
 "pasture\_blanket\_short\_3": "pasture\_blanket/rack\_pasture\_blanket\_3\_short\_**<span style="color: rgb(132, 63, 161);">name</span>**.png"  
 }  
 }  
 }  
}

</details><details id="bkmrk-%5Bexpand%5D-armored-pas"><summary>\[EXPAND\] Armored Pasture Blanket Template</summary>

{  
 "display": {  
 "name": "Armored **<span style="color: rgb(132, 63, 161);">Name</span>** Pasture Blanket",  
 "credits": "**<span style="color: rgb(132, 63, 161);">Artist(s)</span>**",  
 "inspiration": "**<span style="color: rgb(132, 63, 161);">N/A</span>**"  
 },  
 "cost": {  
 "coin": "<span style="color: rgb(132, 63, 161);">**diamond**</span>",  
 "amount": **<span style="color: rgb(132, 63, 161);">2</span>**  
 },  
 "meta": {  
 "name": "**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket\_armored",  
 "icon": "pasture\_blanket/**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket\_armored\_icon.png",  
 "type": "pasture\_blanket",  
 "data": {  
 "color": \[**<span style="color: rgb(132, 63, 161);">255, 190, 0</span>**\],  
 "is\_armored": **<span style="color: rgb(132, 63, 161);">true</span>**  
 },  
 "textures": {  
 "horse": {  
 "legacy": {  
 "pasture\_blanket": "pasture\_blanket/**<span style="color: rgb(132, 63, 161);">name</span>**\_pasture\_blanket\_armored\_legacy.png"  
 }  
 },  
 "rack": {  
 "pasture\_blanket\_long\_5": "pasture\_blanket/rack\_pasture\_blanket\_5\_long\_**<span style="color: rgb(132, 63, 161);">name</span>**.png",  
 "pasture\_blanket\_short\_3": "pasture\_blanket/rack\_pasture\_blanket\_3\_short\_**<span style="color: rgb(132, 63, 161);">name</span>**.png"  
 }  
 }  
 }  
}

</details>**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP FIVE: </span> TEST YOUR COMMUNITY PACK**

It is recommended to check your pack early after doing just one or two items to ensure you have followed instructions correctly.

1. 1. Paste the community pack file in `config > swem > community-packs`  
        → Read [here](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip#bkmrk-community-packs) if this is your first time installing a community pack.
    2. Load the game
    3. Open a test world with cheats enabled
    4. Place an EQ Shop Block
    5. Give yourself some tokens   
        → Choose a type that is a valid currency for your tack (as specified in .json)
    6. Place the tokens into the input slot
    7. Check your tack items display and can be purchased
    8. Check the tack item has the correct inventory icon
    9. Check the tack can be equipped and:  
        → The tack has the expected texture  
        → The tack has the expected features (ie supports armor if it should, armor tier, wings etc)
    10. Check the tack can be placed on supported racks (if relevant) and displays the correct texture

<details id="bkmrk-%5Bexpand%5D-troubleshoo-1"><summary>\[EXPAND\] Troubleshooting Errors</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMMUNITY PACK TROUBLESHOOTING </span>  
FOLLOW <span style="text-decoration: underline;">EACH STEP</span> CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP <span style="text-decoration: underline;">AFTER</span> USING THIS!**

**⮞ \[1\] MOD VERSION**

- **Double check** you are using the latest 1.20.1 Beta version.  
    **→** Even if you feel sure, go and check it. It's the most common error!  
    **→** `Curseforge App` Will not auto-install beta files, go to `mod's page > versions > install`  
    **→** `Multiplayer Servers` Check server is on latest release  
    **→** `Multiplayer Users` Check client + server use same version  
    ⚠️ **Community Packs are for 1.20.1-1.5 and above only.**

**⮞ \[2\] COMMUNITY PACK LOADING**

- Open the game and load into a world
- Type `/give @p <id:>` Example `/give @p artist_packname:`  
    **→** Is the command valid? (displays autofill options)  
      
    ✅ Pack is recognized  
    **❌** Pack is not recognized or has failed to register at least one item. **Go to solutions \[2\].**

 **⮞ \[3\] ITEM REGISTERED**

- Type `/give @p <id:>` Example `/give @p artist_packname:`  
    **→** Is every item you expect to see registered listed?  
      
    ✅ Items are registered  
    **❌** Item(s) have invalid or missing files. **Go to solutions \[3\].**

**⮞ \[4\] JSON -&gt; TEXTURE PATH**

- Give yourself an item from the pack  
    **→** Does it have the correct inventory texture?  
    **→** Does it have the correct horse texture (when equipped)?  
    **→** Does it apply to the required parts of the horse or tack model (ie Bridle bit)?  
    **→** Does it have the correct rack texture (if supported)?  
      
    ✅ Item texture paths are correct  
    **❌** `Missing Texture` Texture path or file name is invalid or missing. **Go to solutions \[4\].  `Multiplayer` Player is missing the pack or no texture for that coat path. **Go to solutions \[4\].**  
    **❌** `Wrong Texture` Texture path or file name is incorrect. **Go to solutions \[4\]. ❌** `Looks Wrong` Texture or UV map error. **Contact Coat Artist or request help. ❌** `Wrong Perks / Protection / Features` JSON information is incorrect.

 **⮞ \[5\] OTHER**

- `Texture Error`  
    **→** If a texture appears broken (color in wrong places, missing pixels, marker blocks) it needs a texture or UV fix.  
    **→** If you are not the texture artist, contact the original creator.
- `Error On Load / Crashing`   
    **→** Too many potential causes  
    → Check you have no duplicate JSON files  
    **→** Check no JSON information uses the same item name as another item in the pack (ie midnight\_saddle x 2) **→** Paste your **latest.log** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord with a description of the issue(s).
- `Pasture Blanket Rack Textures (Black or Wrong Texture)`  
    **→** Check the rack texture path uses `5_long` or `3_short` and not `long_5` or `short_3`
- `All Text Appears as ▯ in Minecraft` Potentially caused by invalid packs.

  
<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **SOLUTIONS &amp; SUGGESTIONS** </span>**ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES**

<p class="callout warning">**It is not recommended to modify packs from a Creator <span style="text-decoration: underline;">unless</span> you intend to customize it and solve any issues.**  
✅ You should follow this troubleshooting guide to identify your likely issue first.  
✅ You should notify Creator's of potential problems with the **default pack** (might need a fix or update).  
**❌** You should NOT expect Creator's to troubleshoot an issue you might have caused by altering files!</p>

**⮞ ISSUE \[2\]**

- Check the community pack:  
    → Pack is directly in `config > swem > community-packs`   
    → Pack is a **folder** and not a zip file! **→** Pack has a valid **lowercase** name with **no spaces** ✅`artist_tackpack` **❌** `Artist: Tack Pack!`  
    **→** Pack includes at least one `.json` and `.png` file in the **correct folder**  📁 jsons &gt; 📁 tack &gt; 📁 \[type\] &gt; `JSON FILES HERE`  
     📁 textures &gt; 📁 tack &gt; 📁 \[type\] &gt; `PNG FILES HERE`  
      
    If this is **ALL** correct the issue is not the community pack structure. **Go back to Step \[3\] above.**

**⮞ ISSUE \[3\]**

- Identify an item that is missing in game
- Check the **.json** file for the tack item  
    → File is listed as a `JSON File` type  
    → File is directly in `community-packs > artist_packname > jsons > tack > [type]` &lt;- Correct folder for the tack type  
    → File has a valid **lowercase** name with **no spaces** ✅`name_type` **❌** `Itemname - Type`  
    → File information uses the correct template for the tack type  
    → Folder contains **.json** files only - **no .pngs or any other file type**  
      
    If this is correct, the most likely issue is formatting (invalid json).  
    → Compare your **.json** to the template and note any missing `"` `,` or `{ }` or different indentation  
    → If unsure, delete and repaste the .json file text from a valid template for the specific tack type  
    → Reload the game and repeat **Step \[3\]** above.  
      
    <span style="color: rgb(255, 255, 255);">**<span style="background-color: rgb(224, 62, 45);"> KNOWN ISSUE </span>**</span> Opening or modifying a pack on a Mac creates a .DS\_store file.  
    → This is usually invisible to Mac users and prevents the pack from working. [**Discord: Bug Report**](https://discord.com/channels/715626418893095012/1312075496640610325/1312075496640610325)  
      
    If this is **ALL** correct or changes did not work, paste your **.json** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord

**⮞ ISSUE \[4\]**

- Identify an item with a missing or incorrect texture
- Check the **.json** file for the coat  
    → File uses the correct path:  
     `"icon":` for inventory textures  
     `(horse > legacy >) "type":` for horse textures   
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** Specific items have more than one texture, such as bridles (bit = halter + bridle) and leg wraps (wraps + hoof)  
    → File texture path has the **exact** name used by the coat texture **.png** file
- Check the .png file for the coat  
    → File is listed as a `PNG File` type  
    → File is directly in `community-packs > artist_packname > textures > tack > [type]`  
    → File has a valid **lowercase** name with **no spaces** ✅`name_type` **❌** `Item Name - Tack Type`  
    → File uses the correct naming format (see **Files &amp; Naming Format**)
- `MULTIPLAYER SERVERS`  
    → Client (player) has community pack(s) with the same name (ID) as those on the server.   
    → Client (player) has **.png** files with the same names as those in the server pack.  
      
    If you cannot check this due to permissions, you will need to contact server admins.

**⮞ \[5\] OTHER <span style="text-decoration: underline;">OR</span> NOTHING WORKED**

- Create a post in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord  
    → Describe your issue(s) and **what you have tried** → Upload your latest.log file to provide info that may help others assist you  
     **DO NOT UPLOAD PAID/PRIVATE PACKS WITH TEXTURES FROM CREATORS WITHOUT CONSENT**

</details><details id="bkmrk-%5Bexpand%5D-checking-js"><summary>\[EXPAND\] Checking JSON Validity</summary>

It is easy to make small errors when creating or editing JSON files. Even a simple missing `{` can make your pack invalid.  
There is a simple way to check if your JSON files have any formatting errors, using an online validator.

1. Open an online validator like [THIS](https://jsonlint.com/)
2. Paste in the contents of your JSON file
3. Click `Validate JSON` to check the file
4. View the output below

[![image.png](https://wiki.swequestrian.com/uploads/images/gallery/2024-12/scaled-1680-/image.png)](https://wiki.swequestrian.com/uploads/images/gallery/2024-12/image.png)

<p class="callout info">This is a valid JSON File with no formatting errors!  
→ Packs can still fail to register or work if the files and folders are incorrect or duplicated.  
→ Packs can still fail to register if other files have format errors, or files have invalid or missing data.  
</p>

[![image.png](https://wiki.swequestrian.com/uploads/images/gallery/2024-12/scaled-1680-/QYdimage.png)](https://wiki.swequestrian.com/uploads/images/gallery/2024-12/QYdimage.png)

<p class="callout info">This is an invalid JSON where the `{` is missing after `"data":` making `"color":` invalid  
→ You may not necessarily understand what it is telling you, but you can use this section to compare to examples.  
→ If you cannot resolve your issue, sharing a screenshot of this output may assist helpers in tech help to find your issue.  
</p>

</details>---

#### Adding Custom Animations

<p class="callout info">It is recommended to provide a command list with Animation Packs, as they will not auto-fill in game.</p>

This guide will not cover how to create animations, for information please read our <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> \[RESOURCES\] </span> on Discord.

1. Create your custom animation(s) in blockbench
2. Create an animation resource pack  
    → Replace `assets > swem > animations > swem_horse.json` with a custom animation file  
    → This must include all the existing animations **and** any new animations
3. Install the resource pack in the `resourcepack` folder
4. Use `/swem rrp anim <Animation Name>` to trigger the animation

Additional information:

- Animations cannot be triggered via keys (like gaits) but must use a command.  
    → Default animations can still be replaced if you want to override gaits
- Animations will loop until the command is re-run to stop it.
- All clients (players) must install the resource pack to view triggered animations
- **<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> TBC </span><span style="color: rgb(255, 255, 255);"> </span>**<span style="color: rgb(0, 0, 0);">Multiplayer Servers</span>

---

#### Resources

<details id="bkmrk-creating-tack-textur"><summary>Creating Tack Textures \[WIP\]</summary>

<p class="callout info">**Credits:** Jenny</p>

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **HORSE TACK TEXTURES** </span>

1. Download a copy of the latest SWEM .jar (mod file)
2. Unzip the .jar file to access the SWEM files
3. Download / Open Blockbench
4. File &gt; Open Model  
    → Open Horse Model: `assets > swem > geo > entity > horse > swem_horse`
5. View the blocks menu on the bottom right
6. Toggle all blocks to Off using the eye icon  
    → This is to prevent accidental texturing of the wrong element  
    → Each tack type renders specific blocks - ie painting neck for leg wraps will not show!
7. Toggle on only relevant elements for your chosen tack type  
    → This might include multiple blocks - see chart below
8. **<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> TBC </span><span style="color: rgb(255, 255, 255);"> </span>**Create a new texture that is 512 x 512 pixels (16x)  
    → Alternatively, import a base texture to use as a template  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** These are found in `assets > swem > textures > entity > horse > [type]`
9. Switch to the paint tab and texture
10. Right click the completed texture in the texture menu &gt; `save as`
11. Save the file as `name_type` or `name_type_descriptor` **✅** `midnight_blanket` `midnight_blanket_blue`  
    → Using a descriptor is useful for multiple variant sets **✅** `blanket_blue` `blanket_red`

<table border="1" style="border-collapse: collapse; width: 100%; height: 2740.46px;"><colgroup><col style="width: 15.0803%;"></col><col style="width: 58.9617%;"></col><col style="width: 25.958%;"></col></colgroup><tbody><tr style="height: 53.7969px;"><td colspan="3" style="height: 53.7969px;"><p class="callout info">Blockbench has a search function (magnifying glass) in the outliner (blocks) menu to search by name or keyword.</p>

</td></tr><tr style="height: 29.7969px;"><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Tack Type**</span></td><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Group**</span></td><td class="align-center" style="height: 29.7969px; background-color: rgb(52, 5, 93);"><span style="color: rgb(255, 255, 255);">**Element(s)**</span></td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">Bridle (Western)</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleLeftBit`

</td><td style="height: 47.2188px;">WesternBridleLeftBit (5X)</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleLeftRein`

</td><td style="height: 47.2188px;">WesternBridleLeftRein</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleLeftRein1`

</td><td style="height: 47.2188px;">WesternBridleLeftRein1</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleLeftRein2`

</td><td style="height: 47.2188px;">WesternBridleLeftRein2</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleRightBit`

</td><td style="height: 47.2188px;">WesternBridleRightBit (5X)</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleRightRein`

</td><td style="height: 47.2188px;">WesternBridleRightRein</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleRightRein1`

</td><td style="height: 47.2188px;">WesternBridleRightRein1</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > WesternBridle > WesternBridleRightRein2`

</td><td style="height: 47.2188px;">WesternBridleRightRein2</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">**<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> TBC: HEADPIECE </span>**

</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Bridle (English)</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Bridle (Adv)</td><td style="height: 29.7969px;">  
</td><td style="height: 29.7969px;">  
</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;"> </td><td style="height: 30.1094px;"> </td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;"> </td><td style="height: 30.1094px;"> </td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">Blanket</td><td style="height: 30.1094px;">`Middle > BlanketMiddle`</td><td style="height: 30.1094px;">Blanket Middle (2X)</td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">Saddle (Western)  
</td><td style="height: 30.1094px;">`Middle > WesternSaddle`</td><td style="height: 30.1094px;">WesternSaddle</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > WesternSaddle > WesternSaddleMiddle`</td><td style="height: 30.1094px;">WesternSaddleMiddle (10X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > WesternSaddle > WesternSaddleLeftSide`</td><td style="height: 30.1094px;">WesternSaddleLeftSide (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > WesternSaddle > WesternSaddleRightSide`</td><td style="height: 30.1094px;">WesternSaddleRightSide (3X)</td></tr><tr style="height: 30.1094px;"><td rowspan="3" style="height: 90.3282px;">Saddle (English)  
</td><td style="height: 30.1094px;">`Middle > EnglishSaddle > EnglishSaddleMiddle`</td><td style="height: 30.1094px;">EnglishSaddleMiddle (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > EnglishSaddle > EnglishSaddleRightSide`</td><td style="height: 30.1094px;">EnglishSaddleRightSide (4X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > EnglishSaddle > EnglishSaddleLeftSide`</td><td style="height: 30.1094px;">EnglishSaddleLeftSide (4X)</td></tr><tr style="height: 30.1094px;"><td rowspan="4" style="height: 120.438px;">Saddle (Adv)</td><td style="height: 30.1094px;">`Middle > AdventureSaddle`</td><td style="height: 30.1094px;">AdventureSaddle</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > AdventureSaddle > AdventureSaddleMiddle`</td><td style="height: 30.1094px;">AdventureSaddleMiddle (6X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > AdventureSaddle > AdventureSaddleLeftSide`</td><td style="height: 30.1094px;">AdventureSaddleLeftSide (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > AdventureSaddle > AdventureSaddleRightSide`</td><td style="height: 30.1094px;">AdventureSaddleRightSide (3X)</td></tr><tr style="height: 30.1094px;"><td rowspan="2" style="height: 60.2188px;">Girth Strap  
</td><td style="height: 30.1094px;">`Middle > Belly > GirthStrapBelly`</td><td style="height: 30.1094px;">GirthStrapBelly (2X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > GirthStrapMiddle`</td><td style="height: 30.1094px;">GirthStrapMiddle (2X)</td></tr><tr style="height: 30.1094px;"><td rowspan="7" style="height: 210.766px;">Breast Collar  
</td><td style="height: 30.1094px;">`Front > BaseFront > BreastCollarBase`</td><td style="height: 30.1094px;">BreastCollarBase (2X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > BaseFront > BreastRight > BreastCollarBreastRight`</td><td style="height: 30.1094px;">BreastCollarBreastRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > BaseFront > BreastLeft > BreastCollarBreastLeft`</td><td style="height: 30.1094px;">BreastCollarBreastLeft</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > BaseFront > FrontLeft > BreastCollarFrontLeft`</td><td style="height: 30.1094px;">BreastCollarFrontLeft (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > BaseFront > FrontRight > BreastCollarFrontRight`</td><td style="height: 30.1094px;">BreastCollarFrontRight (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > BreastCollarBelly`</td><td style="height: 30.1094px;">BreastCollarBelly</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > BreastCollarMiddle`</td><td style="height: 30.1094px;">BreastCollarMiddle</td></tr><tr style="height: 29.7969px;"><td rowspan="10" style="height: 299.844px;">Leg Wraps  
</td><td style="height: 29.7969px;">Front &gt; FrontLeft &gt; FrontLeftLeg &gt; .. &gt; .. &gt; LegWrapsFrontLeftHoof</td><td style="height: 29.7969px;">LegWrapsFrontLeftHoof</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Front &gt; FrontLeft &gt; FrontLeftLeg &gt; .. &gt; .. &gt; LegWrapsFrontLeft</td><td style="height: 29.7969px;">LegWrapsFrontLeft</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Front &gt; FrontRight &gt; FrontRightLeg &gt; .. &gt; .. &gt; LegWrapsFrontRightHoof</td><td style="height: 29.7969px;">LegWrapsFrontRightHoof</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Front &gt; FrontRight &gt; FrontRightLeg &gt; .. &gt; .. &gt; LegWrapsFrontRight</td><td style="height: 29.7969px;">LegWrapsFrontRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Back > BackLeft > .. > .. > .. > .. > LegWrapsBackLeftHoof`</td><td style="height: 30.1094px;">LegWrapsBackLeftHoof</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Back > BackLeft > Bone4 > KneeLeft > Bone6 > LegWrapsBackLeft`</td><td style="height: 30.1094px;">LegWrapsBackLeft</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Back > BackRight > .. > .. > .. > .. > LegWrapsBackRightHoof`  
</td><td style="height: 30.1094px;">LegWrapsBackRightHoof</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Back > BackRight > Bone7 > KneeRight > .. > LegWrapsBackRight`</td><td style="height: 30.1094px;">LegWrapsBackRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > Neck > NeckJoint1 > Head > Skull > LegWrapsSkull`</td><td style="height: 30.1094px;">LegWrapsSkull</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > . > . > . > Skull > BridgeOfNose > LegWrapsBridgeOfNose`</td><td style="height: 30.1094px;">LegWrapsBridgeOfNose</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">Saddle Bag</td><td style="height: 30.1094px;">`Back > Base > SaddleBag > SaddleBagLeft`</td><td style="height: 30.1094px;">SaddleBagLeft</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Back > Base > SaddleBag > SaddleBagRight`</td><td style="height: 30.1094px;">SaddleBagRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Back > Base > BedRoll`</td><td style="height: 30.1094px;">BedRoll (7X)</td></tr><tr style="height: 30.1094px;"><td rowspan="7" style="height: 210.766px;">Horse Armor  
</td><td style="height: 30.1094px;">`Front > FrontLeft > ArmorLeftShoulder`</td><td style="height: 30.1094px;">ArmorLeftShoulder (4X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > FrontRight > ArmorRightShoulder`</td><td style="height: 30.1094px;">ArmorRightShoulder (4X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > Neck > NeckJoint1> MainNeck1 > ArmorNeck > ArmorNeck1`</td><td style="height: 30.1094px;">ArmorNeck1 (3X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Front > Neck > NeckJoint1 > Head > ArmorHead > ArmorHead1`</td><td style="height: 30.1094px;">ArmorHead1 (8X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > ArmorCloth > ArmorClothLeft`</td><td style="height: 30.1094px;">ArmorClothLeft</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Middle > ArmorCloth > ArmorClothRight`  
</td><td style="height: 30.1094px;">ArmorClothRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">`Back > Base > ArmorButt > 10X`</td><td style="height: 30.1094px;">ArmorButt (10X)</td></tr><tr style="height: 47.2188px;"><td rowspan="10" style="height: 472.188px;">Wings  
</td><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > LeftGROUP > WingsScapularLeft`  
</td><td style="height: 47.2188px;">WingsScapularLeft</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > LeftGROUP > WingsMarginalLeft`  
</td><td style="height: 47.2188px;">WingsMarginalLeft</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > LeftGROUP > WingsMarginalLeft2`  
</td><td style="height: 47.2188px;">WingsMarginalLeft2</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > LeftGROUP > WingsMarginalLeft2 > WingsAlulaLeft`  
</td><td style="height: 47.2188px;">WingsAlulaLeft</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > LeftGROUP > WingsMarginalLeft2 > WingsAlulaLeft > WingsFlightFeathersLeft`  
</td><td style="height: 47.2188px;">WingsFlightFeathersLeft</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > RightGROUP > WingsScapularRight`  
</td><td style="height: 47.2188px;">WingsScapularRight</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > RightGROUP > WingsMarginalRight`  
</td><td style="height: 47.2188px;">WingsMarginalRight</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > RightGROUP > WingsMarginalRight2`  
</td><td style="height: 47.2188px;">WingsMarginalRight2</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > RightGROUP > WingsMarginalRight2 > WingsAlulaRight`  
</td><td style="height: 47.2188px;">WingsAlulaRight</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">`Front > BaseFront > WingsScapular > RightGROUP > WingsMarginalRight2 > WingsAlulaRight > WingsFlightFeathersRight`</td><td style="height: 47.2188px;">WingsFlightFeathersRight</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">Halter</td><td style="height: 30.1094px;">`Front > Neck > NeckJoint1 > Head > Skull > HalterSkull`  
</td><td style="height: 30.1094px;">HalterSkull</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > Skull > BridgeOfNose > HalterBridgeOfNose`  
</td><td style="height: 47.2188px;">HalterBridgeOfNose</td></tr><tr style="height: 47.2188px;"><td style="height: 47.2188px;">  
</td><td style="height: 47.2188px;">`Front > Neck > NeckJoint1 > Head > Skull > Cheeks > HalterCheeks`  
</td><td style="height: 47.2188px;">HalterCheeks</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Front > Neck > NeckJoint1 > Head > Mouth > HalterMouth`</td><td style="height: 30.1094px;">HalterMouth</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">Pasture Blanket</td><td style="height: 30.1094px;">`Front > FrontLeft > PBFrontLeft`  
</td><td style="height: 30.1094px;">PBFrontLeft (4X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Front > FrontRight > PBFrontRight`  
</td><td style="height: 30.1094px;">PBFrontRight (4X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Middle > PBMiddle`  
</td><td style="height: 30.1094px;">PBMiddle (5X)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">  
</td><td style="height: 30.1094px;">`Back > Base > PBBack`</td><td style="height: 30.1094px;">PBBack (6X)</td></tr></tbody></table>

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **TACK RACK TEXTURES** </span>

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **TACK ICON TEXTURES** </span>

1. Download / Open Blockbench
2. File &gt; New &gt; Image  
    → Set name as `name_type_icon` **✅** `midnight_blanket_icon`  
    → Set resolution as default 16x16 pixels
3. Confirm
4. Create an icon to represent your tack in inventory slots  
    → Alternatively, drag a default icon texture to use as a template  
    → Select `Add Image` from options  
     **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> Note: </span>** These are found in `assets > swem > textures > item [item_name]`
5. **<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> TBC </span><span style="color: rgb(255, 255, 255);"> </span>**Saving

</details>**<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> COMING SOON </span>**

---

#### Known Issues

---

#### Credits

Special thanks to the following contributors:

- Quarris for feature documentation, example pack and wiki information support
- Jenny for creator resources, testing and documentation
- Neehra for creator resources, testing and Mac information
- Legend for recommending JSON validation resources

# Coats [NEW]

<p class="callout info">This feature is available in **1.20.1-1.5+** and will **NOT** be backported to any outdated versions.</p>

#### Features

Community packs add NEW custom coats in-game without overriding the default variants.

- Supports simple breeding "color tags"
- Supports lapis / redstone cycling (if enabled)
- Supports summon command
- Supports natural spawning **via compatible community datapacks**

---

#### Important - Update Changes

This update has made changes to coat NBT data, summon commands as well as some smaller (less gameplay significant) changes.   
Expand the drop-down to read more about specific changes and how that might impact you as a player or creator.

<details id="bkmrk-changes-to-coat-data"><summary>\[EXPAND\] Changelog</summary>

<table border="1" id="bkmrk-features-changes-sum" style="border-collapse: collapse; width: 100%; height: 591.688px;"><colgroup><col style="width: 16.8155%;"></col><col style="width: 83.1845%;"></col></colgroup><tbody><tr style="background-color: rgb(52, 5, 93); height: 29.7969px;"><td class="align-center" style="height: 29.7969px;"><span style="color: rgb(255, 255, 255);">**Feature**</span></td><td class="align-center" style="height: 29.7969px;"><span style="color: rgb(255, 255, 255);">**Changes**</span></td></tr><tr style="height: 141.891px;"><td class="align-center" style="height: 141.891px;">Summon</td><td style="height: 141.891px;">Minecraft `/summon` spawns white horses only (cannot randomize).

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> NEW </span> SWEM SUMMON COMMANDS**

`/swem summon LEGACY swem:coat` Summon a default coat. **EX:** `swem:sweetboi`  
  
`/swem summon LEGACY pack_name:coat_artist` Summon a custom coat. **EX:** `kofi:hidalgo_arishant`  
  
`/swem summon random LEGACY` Summon a random coat

</td></tr><tr style="height: 367.25px;"><td class="align-center" style="height: 367.25px;">Coat Data</td><td style="height: 367.25px;">Removed `Variant: #` NBT and changed to `Behaviors[6].Coat`  
  
Data values for coat must set a value using `<id:coat>` (see below for info)

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> NEW </span> SWEM COAT CHANGE COMMANDS**

`/swem set coat` Displays a list of all valid choices

`/swem set coat swem:coat` Change to a default coat. **EX:** `swem:sweetboi`  
  
`/swem set coat pack_name:coat_artist` Change to a custom coat. **EX:** `kofi:hidalgo_arishant`

**MINECRAFT COMMANDS (OP)**

<p class="callout info">*MC Commands are exempt from role keys (ie swem:mod) - which may be useful to servers.*</p>

**Identify a coat (ID)**

<span style="color: rgb(224, 62, 45);"><span style="color: rgb(0, 0, 0);">`/data get entity @e[type=swem:swem_horse,sort=nearest,limit=1] Behaviors[6].Coat` </span></span>

**Change a coat**

`/data modify entity @e[type=swem:swem_horse,limit=1,sort=nearest] Behaviors[6].Coat set value <"id:coat">`

</td></tr><tr style="height: 52.75px;"><td class="align-center" style="height: 52.75px;">Model</td><td style="height: 52.75px;">Coats and commands must state a supported model - this will be expanded in future.

`LEGACY` Default model and the only one currently implemented.

</td></tr></tbody></table>

</details>---

#### Frequently Asked Questions

This section has drop-downs for FAQs and expanded information about Community Pack Coats.  
If your question is not answered here, check out [General Information.](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip)

<details id="bkmrk-%5B3%5D-multiplayer-use-"><summary>\[EXPAND\] FAQs</summary>

**⮞ CAN COMMUNITY PACKS ADD NEW FOAL VARIANTS?** No. The current system allows for 1 foal per color tag; support for additional foals will require an expanded breeding system.

⮞ **CAN COMMUNITY PACKS MODIFY DEFAULT SWEM COATS?**  
No. Information such as obtainable by breeding, color tags, lapis cycling is hard coded for default coats (included in SWEM).  
You can use a resource pack to override any coat texture if you want to replace it.

**⮞ CAN COMMUNITY PACKS ADD NEW MODELS?** No. It should continue to work with resource packs that override the SWEM model.  
This feature will support the new Destrier model (and any others) when it is released in future.

⮞ **CAN CUSTOM COATS APPEAR NATURALLY ON HORSES?**  
Yes. If the coat information (json) file allows breeding and cycling, it can occur when a horse is summoned or converted.

⮞ **CAN CUSTOM COATS NATURALLY SPAWN?**  
No. Neither default nor custom coats naturally spawn in the wild (replace MC horses) unless you use a custom datapack.

<p class="callout info">This update has been modified to continue support for Ace's Datapack found [**HERE**](https://discord.com/channels/715626418893095012/840972393153691738/1022973584181841981) in our Discord.</p>

⮞ **CAN CUSTOM COATS SUPPORT LAPIS / REDSTONE CYCLING?** Yes. This must be set to true for `lapis_cycling` in the coat json file, and `allowCoatCycling` in the [server config](https://wiki.swequestrian.com/books/swequestrian-mod/page/server-config) file.

⮞ **CAN CUSTOM COATS APPEAR FROM BREEDING DEFAULT +/- CUSTOM COATS?**  
Yes. This must be set to true for `obtainable_by_breeding` in the coat json file. You must set at least one `base_colors` tag - this will determine which color tags your horse can pass on if bred, as well as which foal color(s) can grow up into this coat.

⮞ **CAN I MAKE A CUSTOM COAT 'SECRET'?** Yes, but not in the same way as special default coats. You can set `lapis_cycling` and `obtainable_by_breeding` to **false** in the coat json file, which will prevent cycling and appearance by breeding or converting. **The coat will only appear if summoned via command.** If you have the right kind of knowledge, you could probably create a custom datapack or redstone system loop to check for and convert horses that meet 'secret coat criteria' (ie height and name), or other crafty ways to achieve this result.

</details>---

#### Using A Community Pack

To install a Content Pack or **PREMADE** Community Pack, see [General Information](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip).

<details id="bkmrk-read-more-%E2%AE%9E-what-is-"><summary>\[EXPAND\] Community Pack vs Content Pack</summary>

**⮞ WHAT IS A COMMUNITY PACK?** Community Packs are folders that include all the files necessary to add NEW assets and are ready to play once installed.

**⮞ WHAT IS A CONTENT PACK?** Content Packs is also a Community Pack, but usually with less content. It will merge into any Community Packs with the same name, like an 'expansion' pack or add-on.

</details>---

#### Creating A Community Pack Coat

To create or modify a Content Pack or Community pack, see [Creators' Corner](https://wiki.swequestrian.com/books/swequestrian-mod/page/creators-corner-wip).

---

#### Troubleshooting

If you experience an issue with content packs in game, please follow this troubleshooting guide.

<details id="bkmrk-%5Bexpand%5D-troubleshoo"><summary>\[EXPAND\] Troubleshooting Errors</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMMUNITY PACK TROUBLESHOOTING </span>  
FOLLOW <span style="text-decoration: underline;">EACH STEP</span> CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP <span style="text-decoration: underline;">AFTER</span> USING THIS!**

**⮞ \[1\] MOD VERSION**

- **Double check** you are using the latest 1.20.1 Beta version.  
    **→** Even if you feel sure, go and check it. It's the most common error!  
    **→** `Curseforge App` Will not auto-install beta files, go to `mod's page > versions > install`  
    **→** `Multiplayer Servers` Check server is on latest release  
    **→** `Multiplayer Users` Check client + server use same version  
    ⚠️ **Community Packs are for 1.20.1-1.5 and above only.**

⮞ **\[2\] OFFICIAL COMMUNITY PACK VERSION**

- Skip this step if you are not using the official Community Pack.  
    **→** Check you have `swem_community_pack_beta_5` or above.  
    **→** Check this is the latest version posted - it may have a new release!  
    **→** `Multiplayer Servers` Check server has the correct pack  
    **→** `Multiplayer Users` Check clients have the same pack name + contents as server

**⮞ \[3\] COMMUNITY PACK LOADING**

- Open the game and load into a world
- Type `/swem summon LEGACY`  
    **→** Is the pack listed?   
    **→** Is **any** pack listed (excluding `swem:`)  
      
    ✅ Pack(s) are recognized  
    **❌** Pack(s) are not recognized, specific packs are invalid or have no valid files. **Go to solutions \[3\].**

**⮞ \[4\] COAT REGISTERED**

- Type `/swem summon LEGACY packname:`  
    **→** Is the coat(s) you expect to see listed? **Example** `kofi_coats:spirit_arishant_legacy`  
      
    ✅ Coat(s) have registered.  
    **❌** Coats have not registered OR specific coat(s) are invalid. **Go to solutions \[4\].**

**⮞ \[5\] JSON -&gt; TEXTURE PATH**

- Summon coat(s) from the pack  
    **→** Do coat(s) have a texture that is correct for that horse?  
      
    ✅ Coat(s) have the correct texture  
    **❌** `Black Texture` Texture path or file name is invalid or missing. **Go to solutions \[5\].  `Multiplayer` Player is missing the pack or no texture for that coat path. **Go to solutions \[5\].**  
    **❌** `Wrong Coat` Texture path or file name is incorrect. **Go to solutions \[4\]. ❌** `Looks Wrong` Texture or UV map error. **Contact Coat Artist or request help.**

**⮞ \[6\] OTHER**

- `Lapis Cycling`   
    **→** If you cannot cycle **any** coats using lapis or redstone, it is disabled in server config.  
    **→** If you can cycle coats, but some options are missing, it is disabled in the coat **.json** file.
- `White Texture`   
    **→** If a coat is white, the pack or coat .json files were removed or renamed  
    **→** If that is not the case, information in .json may have an error (invalid format) **Go to solutions \[5\].**
- `Texture Error`  
    **→** If a coat appears broken (color in wrong places, missing pixels, marker blocks) it needs a texture or UV fix.  
    **→** If you are not the coat artist, contact the original creator.
- `Error On Load / Crashing`   
    **→** Too many potential causes **→** Paste your **latest.log** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord with a description of the issue(s).

  
<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **SOLUTIONS &amp; SUGGESTIONS** </span>**ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES**

<p class="callout warning">**It is not recommended to modify packs from a Creator <span style="text-decoration: underline;">unless</span> you intend to customize it and solve any issues.**  
✅ You should follow this troubleshooting guide to identify your likely issue first.  
✅ You should notify Creator's of potential problems with the **default pack** (might need a fix or update).  
**❌** You should NOT expect Creator's to investigate issues you might have caused by altering their original files!</p>

**⮞ ISSUE \[3\]**

- Check the community pack:  
    → Pack is directly in `config > swem > community-packs`   
    → Pack is a **folder** and not a zip file! **→** Pack has a valid **lowercase** name with **no spaces** ✅`artist_kofi` **❌** `Artist Kofi Coats`  
    **→** Pack includes at least one `.json` and `.png` file in the **correct folder**  📁 jsons &gt; 📁 coats &gt; `JSON FILES HERE`  
     📁 textures &gt; 📁 coats &gt; 📁 legacy &gt; `PNG FILES HERE`  
      
    If this is **ALL** correct the issue is not the community pack structure. **Go back to Step \[4\] above.**

**⮞ ISSUE \[4\]**

- Identify a coat that is missing in game
- Check the **.json** file for the coat  
    → File is listed as a `JSON File` type  
    → File is directly in `community-packs > artist_packname > jsons > coats`  
    → File has a valid **lowercase** name with **no spaces** ✅`coatname_artist` **❌** `Coat - Artist`  
    → File texture path uses ✅ `"legacy": "legacy/coatname_artist.png"` **❌** `"legacy": "default:legacy/`  
      
    If this is correct, the most likely issue is formatting (invalid json).  
    → Compare your json to the template and note any missing `"` `,` or `{ }` or different indentation  
    → If unsure, delete and rewrite the .json file using a blank template  
    → Reload the game and repeat **Step \[4\]** above.  
      
    If this is **ALL** correct or changes did not work, paste your **.json** file in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord

**⮞ ISSUE \[5\]**

- Identify a coat with a black (missing) texture
- Check the **.json** file for the coat  
    → File uses `legacy` model line (not any for future models)  
    → File texture path uses ✅ `"legacy": "legacy/coatname_artist.png"` **❌** `"legacy": "<strong>default:</strong>legacy/`  
    → File texture path has the **exact** name used by the coat texture **.png** file
- Check the .png file for the coat  
    → File is listed as a `PNG File` type  
    → File is directly in `community-packs > artist_packname > textures > coats > legacy`  
    → File has a valid **lowercase** name with **no spaces** ✅`coatname_artist` **❌** `Coat - Artist`
- `MULTIPLAYER SERVERS`  
    → Client (player) has community pack(s) with the same name (ID) as those on the server.   
    → Client (player) has **.png** files with the same names as those in the server pack.  
      
    If you cannot check this due to permissions, you will need to contact server admins.

**⮞ \[6\] OTHER <span style="text-decoration: underline;">OR</span> NOTHING WORKED**

- Create a post in [Tech Help](https://discord.com/channels/715626418893095012/997404105704210432) in our Discord  
    → Describe your issue(s) and **what you have tried** → Upload your latest.log file to provide info that may help others assist you  
     **<span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> DO NOT UPLOAD PAID/PRIVATE PACKS WITH TEXTURES FROM CREATORS WITHOUT CONSENT </span>**

</details>

# Tack [WIP]

<p class="callout info">This feature is available in **1.20.1-1.5+** and will **NOT** be backported to any outdated versions.</p>

#### Features

Community packs add NEW custom tack in-game without overriding the default variants.

- Supports in-game purchase via tokens at an EQ Shop
- Supports use on storage items such as tack racks (compatible items)
- Supports buffs on armor items, including tier-specific perks and flight

---

#### Important - Update Changes

This update has not made any significant changes to default tack obtaining or use.

Custom tack can be purchased via the <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> **EQ Shop Block** </span><span style="color: rgb(255, 255, 255);"> </span>using craftable <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> **coins** </span>.


---

#### Frequently Asked Questions 


This section has drop-downs for FAQs and expanded information about Community Pack Tack.  
If your question is not answered here, check out [General Information.](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip)

<details id="bkmrk-%5B3%5D-multiplayer-use-"><summary>\[EXPAND\] FAQs</summary>

**⮞ CAN COMMUNITY PACKS ADD NEW TACK SLOTS AND TYPES?** No. Creators must use the same default tack types and slots, but with some creative effort they can expand on the limited set to suit almost any need.

⮞ **CAN COMMUNITY PACKS MODIFY OR REMOVE DEFAULT SWEM TACK?**  
No. Default tack sets are hard coded.  
You can use a resource pack to retexture, rename or modify the crafting requirements of core tack items.

⮞ **CAN COMMUNITY PACK TACK SUPPORT REDYING FEATURES?** No. This only works for core tack which has one type per discipline (English, Western) and all 16 color variants.

⮞ **CAN THE EQ SHOP SUPPORT TOKEN PURCHASING OF CORE TACK?** No.

⮞ **CAN THE EQ SHOP EXCHANGE UNWANTED TACK FOR TOKENS (REFUND)?** No.

⮞ **CAN THE EQ SHOP EXCHANGE TOKENS FOR MATERIALS?** No, however 4 tokens can be uncrafted into (most of) the original items in a crafting table or player inventory.

</details>---

#### Using A Community Pack

To install a Content Pack or **PREMADE** Community Pack, see [General Information](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip).

<details id="bkmrk-read-more-%E2%AE%9E-what-is-"><summary>\[EXPAND\] Community Pack vs Content Pack</summary>

**⮞ WHAT IS A COMMUNITY PACK?** Community Packs are folders that include all the files necessary to add NEW assets and are ready to play once installed.

**⮞ WHAT IS A CONTENT PACK?** Content Packs is also a Community Pack, but usually with less content. It will merge into any Community Packs with the same name, like an 'expansion' pack or add-on.

</details>---

#### Creating A Community Pack Tack Set

To create or modify a Content Pack or Community pack, see [Creators' Corner](https://wiki.swequestrian.com/books/swequestrian-mod/page/creators-corner-wip).

---

#### Troubleshooting **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMING SOON </span>**

If you experience an issue with community packs in game, please follow this troubleshooting guide.

<details id="bkmrk-%5Bexpand%5D-troubleshoo"><summary>\[EXPAND\] Troubleshooting Errors</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMMUNITY PACK TROUBLESHOOTING </span>  
FOLLOW <span style="text-decoration: underline;">EACH STEP</span> CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP <span style="text-decoration: underline;">AFTER</span> USING THIS!**

**⮞ COMING SOON  <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> DO NOT UPLOAD PAID/PRIVATE PACKS WITH TEXTURES FROM CREATORS WITHOUT CONSENT </span>**

</details>

# Animations [WIP]

<p class="callout info">This feature is available in **1.20.1-1.5+** and will **NOT** be backported to any outdated versions.</p>

#### Features

This update can support adding custom animations with or without overriding the default variants.  
It was not possible to add animations via community pack, **they require a resource pack.**

- Animations must be triggered via the command `/swem rrp anim <Animation>`
- Animations will loop (repeat) until the command is repeated
- Animations will not auto-fill (list possible options), creators should provide the valid options
- Animations will be seen by any player with the animation pack installed

---

#### Important - Update Changes

This update has not made any significant changes to default animations.


---

#### Frequently Asked Questions 


This section has drop-downs for FAQs and expanded information about Animation Resource Packs.  
If your question is not answered here, check out [General Information.](https://wiki.swequestrian.com/books/swequestrian-mod/page/general-information-wip)

<details id="bkmrk-%5B3%5D-multiplayer-use-"><summary>\[EXPAND\] FAQs</summary>

**⮞ CAN ANIMATIONS BE TRIGGERED WITHOUT COMMANDS?** No. While this is not ideal for discipline specific commands (ie dressage moves), there is currently no way to support keybind(s) to trigger custom animations.

**⮞ CAN ANIMATION PACKS MODIFY DEFAULT ANIMATIONS?** Yes, this was already possible and several packs exist to override specific default animations.

**⮞ CAN I INSTALL MULTIPLE ANIMATION PACKS AT ONCE?  
<span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> \[TBC\] </span>** Yes. Animation packs must include both the default animations **and** any custom animations, so if you install more than one pack, you should load any that override default animations at the top.

**Example** If you have an animation pack that adds new dressage moves **and** modifies default gait or jump animations, you should load this **above** any other packs that only add new animations. Since they include the unaltered default animations, they will override your modified defaults unless lower in the list.

**⮞ WHERE CAN I SEE A LIST OF ANIMATION NAMES FOR THE TRIGGER COMMAND?** Animation names will not auto-fill when using the command. Short of opening up the files, it is recommended to confirm valid options with the creator. Check their content or site(s) for a list of valid commands before contacting them directly.

**⮞ CAN I INSTALL ANIMATION PACKS IN A MULTIPLAYER SERVER? <span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> \[TBC\] </span>** Animation packs should work on multiplayer servers, but all players require the resource pack to view the triggered animations. This should all work client-side, servers should not need to make any alterations to support custom animations (ie not required on the server).

**⮞ HOW DO ANIMATION PACKS WORK ON MULTIPLAYER SERVERS WITH KEYS / PERMISSIONS? <span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> \[TBC\] </span>**

**⮞ HOW DO ANIMATION PACKS APPEAR IF A PLAYER IS MISSING THE RESOURCE PACK?  
<span style="color: rgb(255, 255, 255); background-color: rgb(224, 62, 45);"> \[TBC\] </span>**

</details>---

#### Using An Animation Resource Pack

To install an animation resource pack, paste it into the `resourcepack` folder.  
If you have multiple animation packs, put any packs that override **default** animations at the top.

---

#### Creating A Community Pack Tack Set

To create an animation resource pack, see [Creators' Corner](https://wiki.swequestrian.com/books/swequestrian-mod/page/creators-corner-wip#bkmrk-adding-custom-animat).

---

#### Troubleshooting **<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> COMING SOON </span>**

If you experience an issue with animation packs in game, please follow this troubleshooting guide.

<details id="bkmrk-%5Bexpand%5D-troubleshoo"><summary>\[EXPAND\] Troubleshooting Errors</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> ANIMATION PACK TROUBLESHOOTING </span>  
FOLLOW <span style="text-decoration: underline;">EACH STEP</span> CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP <span style="text-decoration: underline;">AFTER</span> USING THIS!**

**⮞ COMING SOON  <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> DO NOT UPLOAD PAID/PRIVATE PACKS WITH FILES FROM CREATORS WITHOUT CONSENT </span>**

</details>

# Community Packs [OLD]

## <span style="color: rgb(255, 255, 255);">**<span style="background-color: rgb(224, 62, 45);"> READ ME </span>**</span>

This page is **OUTDATED** and information is relevant to 1.20.1-1.5 **Beta 7**.  
For 1.20.1-1.5 Public Release, please see [the community pack category](https://wiki.swequestrian.com/books/swequestrian-mod/chapter/community-packs) for updated pages.  
It is public to accept feedback and external input from creators prior to final additions and corrections.  
**This page will remain public until the new category is completed.**

---

<p class="callout info">Community Packs are available for SWEM **1.20.1-1.5+**. This feature will not be backported to older releases!</p>

#### Update Changes - Important  


The community pack feature allows users to add NEW coats to the game instead of overriding existing coats (texture pack).   
To support this feature, the following changes were made:

<table border="1" id="bkmrk-change-information-c" style="border-collapse: collapse; width: 100%; height: 199.359px;"><colgroup><col style="width: 32.013%;"></col><col style="width: 67.987%;"></col></colgroup><tbody><tr style="height: 29.7969px; background-color: rgb(236, 240, 241);"><td style="height: 29.7969px;">**Change**</td><td style="height: 29.7969px;">**Information**</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Coats are named, not numbered</td><td style="height: 29.7969px;">Coats cannot be altered via Variant NBT  
**New Command:** `/swem set coat <id:coat>`

</td></tr><tr style="height: 80.1719px;"><td style="height: 80.1719px;">Coats appear white via /summon</td><td style="height: 80.1719px;">Coats cannot be summoned via Minecraft's /summon.  
**New Command:** `/swem summon LEGACY swem:sweetboi` Default coats  
 `/swem summon LEGACY pack_name:coat_artist` Custom coats  
 `/swem summon random LEGACY` Random coat

</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">Coats apply to a specific model</td><td style="height: 29.7969px;">Continue to use legacy (original) until new models are supported.</td></tr></tbody></table>

---

#### Updating An Existing World

<p class="callout danger">Please read this information carefully and **backup your save** (recommended) **before** updating to 1.20.1-1.5.0+. </p>

- Existing coats should be unaffected.
- Texture packs (swem override) should be unaffected.
- Datapack (fan-made) for [naturally spawning horses](https://discord.com/channels/715626418893095012/840972393153691738/1022973584181841981) is patched to work as normal!
- Config will need to be copied (or edited again) in new folders to keep settings:  
    → Common, Client and Recipe configs now generate in `config/swem`
- **THIS UPDATE WILL PROBABLY BREAK ADD-ONS: PLEASE BE PATIENT AS CREATORS UPDATE THEIR MODS!  
    →** Reported: Tre's Tackshop, Bagek's, Blossom EQ

---

#### Frequently Asked Questions (Dropdown)

<details id="bkmrk-faqs-can-community-p"><summary>FAQs</summary>

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **SUPPORT &amp; FEATURES** </span>

**⮞ NEW MODELS?** It is planned to expand on the models as part of development, but breeds will not be added.  
This update will not break texture packs that override the SWEM model.

⮞ **NEW ANIMATIONS?** Support for new animations is planned for a later date.

⮞ **NEW TACK?** Support for new tack is in progress and will be released in the near future.

⮞ **NEW FOALS?** Foals are limited to 7 variants, one per possible color tag inherited from breeding.   
Support for additional foals will require an expanded genetics system - this is planned for future development.

⮞ **MODIFYING DEFAULT COAT INFO?** Information such as obtainable by breeding, color tags, lapis cycling cannot be edited for default coats, only custom coats.

⮞ **NATURALLY SPAWNING HORSES?** Custom coats can appear on converted vanilla or RHG horses, but default **or** custom coats do not naturally spawn in the wild.  
This update supports the community creation [datapack](https://discord.com/channels/715626418893095012/840972393153691738/1022973584181841981) for naturally spawning horses.

⮞ **BREEDING AND LAPIS CYCLING?** Custom coats can be obtained from lapis cycling or breeding if set to enabled in the coat json file.  
Coat cycling must be enabled in serverconfig to allow the use of lapis or redstone cycling coats.

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **USE ON SAVES &amp; SERVERS** </span>

**⮞ EXISTING SAVES?** Community packs should be safe to use with existing save files.

**⮞ DIFFERENT SAVE FILES?** Community packs apply to **all** saves for that instance or profile. It is not possible to have save-specific community packs without manually changing switching them each time.

**⮞ MULTIPLAYER SERVERS?** Community packs should work on servers, provided all players have the community pack.  
<span style="color: rgb(132, 63, 161);">Please be mindful of creators and do not distribute or use content in a way that is not explicitly permitted!</span>

**⮞ MULTIPLAYER SERVERS (SERVER SIDE ONLY)?** Community packs on server only may not be possible and would likely<span style="color: rgb(132, 63, 161);"> violate the terms of use for custom content.</span>

**⮞ OVERRIDE MULTIPLAYER SERVER COATS?** Community packs are essentially a resource pack when you are a client. You can replace png(s) with different textures, provided they are named the same. This will only be visible to you.  
  
**⮞ MODIFY THE JSON INFO OF A CUSTOM COAT ON MULTIPLAYER SERVERS?** Community packs use the data of the server or host - client side edits will only apply to your singleplayer saves.

**⮞ PLAY SERVERS (NO CUSTOM COATS) WITH A COMMUNITY PACK INSTALLED?** <span style="color: rgb(224, 62, 45);">TBC. </span>Probably fine.

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **MODIFYING A COMMUNITY PACK** </span>

**⮞ ADD NEW COATS (EXISTING SAVE)** You can add a new coat at any time, but need to close and reload the game to apply the new coats.

**⮞ MODIFY COATS (EXISTING SAVE)** You can modify coats at any time, but need to close and reload the game for changes to apply.  
 → If you rename a coat, it will be registered as a NEW coat and any horses using it will turn white.  
 → If you modify the model path, any horses using it will appear fully black unless a valid texture is provided.  
 → If you alter json information, it will only apply to future instances (ie breeding colors to pass on).  
 → <span style="color: rgb(132, 63, 161);">**DO NOT REMOVE CREDITS**</span> (original creator) or falsely claim ownership (plagiarism / art theft).

**⮞ REMOVE COATS (EXISTING SAVE)** You can remove coats at any time, but need to close and reload the game for changes to apply.  
 → If you remove a coat, any horses using retains their coat ID but becomes white unless a new coat is assigned.  
 → If you only remove the PNG, any horses using it will appear fully black unless a texture is provided.

**⮞ FIX ACCIDENTALLY REMOVED COATS (EXISTING SAVE)** You can fix white horses (default coat) by re-adding community packs or coat file(s) to restore them on next reload.

**⮞ REASSIGN REMOVED COATS (EXISTING SAVE)** You can change coats easily with `/swem set coat <id:coat>` or cycle with lapis (if enabled). An alternative command is:  
`/data modify entity @e[type=swem:swem_horse,limit=1,sort=nearest] Behaviors[6].Coat set value <id:coat>`

<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **OTHER** </span>

**⮞ SEE COAT NAME?** It is not currently possible to find out the name or artist for a coat in-game without using a command:  
<span style="color: rgb(224, 62, 45);"><span style="color: rgb(0, 0, 0);">`/data get entity @e[type=swem:swem_horse,sort=nearest,limit=1] Behaviors[6].Coat`</span></span>

</details>---

#### Using Community Packs

To add a **prepared** (ready to use) community pack:

**STEP ONE: GENERATE THE NEW FOLDERS (FIRST TIME LOAD)**

1. Install the mod update.
2. Load the game to the menu screen.
3. **Exit the game.**

**STEP TWO: DOWNLOAD A COMMUNITY PACK**

1. Download a community pack.  
    → A prepared community pack including FREE coat donations can be found [here](https://discord.com/channels/715626418893095012/737144919717707896/1266908931423469609)!
2. Unzip (if necessary) so the file is a folder.  
    → You should have a folder with `pack_name > json / textures etc`   
    → Check the folder is NOT embedded inside another ie `pack_name <em>> </em>pack_name`
3. Cut or copy the `pack_name` folder.
4. Go to `config > swem > community-packs` and paste it.  
    → It should look like: `config > swem > community-packs > pack_name > json / textures etc`

**OTHER INFORMATION**

- You can have multiple packs but they must have a **unique** name ie `pack_1` and `pack_2`
- You can rename a texture pack, but you should not if it is already **in use**.  
    → Community packs must be in lowercase with underscores for any spaces.  
    → ✅ `kofi_coats` **❌** `Kofi Coats`
- You can add, alter or remove from community packs - see **FAQ** above.
- You can access coats in game by the following methods:  
    → Converting vanilla or RHG horses **if** `breeding tokens` config is **FALSE.** → Cycling coats **if** `cycle coat` in config **and** `lapis_cyclable` in json is **TRUE**.  
    → Breeding **if** `obtainable_by_breeding` in json is **TRUE.**  
    → Summon via `/swem summon LEGACY pack_name:coat_artist`

<p class="callout info">If you have not altered configs already, you probably do not need to do so, these should all be DEFAULT settings.</p>

---

#### Creating &amp; Modifying Custom Community Packs

To create a **new** community pack:

**OPTION A: DOWNLOAD THE TEMPLATES (DISCORD)**

- A downloadable (blank) Community Pack and JSON can be found [HERE](https://discord.com/channels/715626418893095012/748632231257440336/1266941242630209589).

**OPTION B: CREATE A COMMUNITY PACK**

1. Inside `config > swem > community-packs`:  
    → Create a folder with the pack name ✅ `kofi_coats` **❌** `Kofi Coats`
2. Inside `pack_name`:  
    → Create a folder called `jsons`  
    → Create a folder called `textures`
3. Inside `jsons`:  
    → Create a folder called `coats`
4. Inside `textures`:  
    → Create a folder called `coats`
5. Inside `textures > coats`:  
    → Create a folder called `legacy`

To add content to a new or existing community pack:

1. Create or download the coat **.png** file  
    → Name it using `coat_artist_model` format ✅ `hidalgo_arishant_legacy` **❌** `Hidalgo Arishant-legacy`   
    → Put this in `community-packs > pack_name > textures > coats > legacy`
2. Create or download a **.json** file with the coat credits and information  
    → Name it the same as the coat .png!  
    → Put this in `community-packs > pack_name > jsons > coats`

<table border="1" id="bkmrk-%F0%9F%93%82-config-%F0%9F%93%82swem-%F0%9F%93%82comm" style="border-collapse: collapse; width: 100%; height: 249.359px;"><colgroup><col style="width: 9.76514%;"></col><col style="width: 8.89988%;"></col><col style="width: 18.2942%;"></col><col style="width: 10.0124%;"></col><col style="width: 10.6304%;"></col><col style="width: 8.65266%;"></col><col style="width: 16.8109%;"></col><col style="width: 16.9345%;"></col></colgroup><tbody><tr style="height: 35.3906px;"><td class="align-center" rowspan="6" style="height: 189.969px;">📂 config  
</td><td class="align-center" rowspan="6" style="height: 189.969px;">📂swem  
</td><td class="align-left" rowspan="6" style="height: 189.969px;">📂community-packs  
</td><td class="align-left" rowspan="2" style="height: 70.7812px;">📂pack\_1  
</td><td class="align-left" style="height: 35.3906px;">📂jsons</td><td class="align-left" style="height: 35.3906px;">📂coats

</td><td style="height: 35.3906px;">🗒️coat1\_artist.json</td><td class="align-left" style="height: 35.3906px;">  
</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px;">📂textures</td><td style="height: 35.3906px;">📂coats</td><td style="height: 35.3906px;">📂legacy

</td><td style="height: 35.3906px;">🖼️coat1\_artist.png

</td></tr><tr style="height: 29.7969px;"><td rowspan="4" style="height: 119.188px;">📂pack\_2  
</td><td class="align-left" rowspan="2" style="height: 59.5938px;">📂jsons  
</td><td rowspan="2" style="height: 59.5938px;">📂coats  
</td><td style="height: 29.7969px;">🗒️coat2\_artist.json</td><td style="height: 29.7969px;"> </td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🗒️coat3\_artist.json</td><td style="height: 29.7969px;"> </td></tr><tr style="height: 29.7969px;"><td rowspan="2" style="height: 59.5938px;">📂textures  
</td><td rowspan="2" style="height: 59.5938px;">📂coats  
</td><td rowspan="2" style="height: 59.5938px;">📂legacy</td><td style="height: 29.7969px;">🖼️coat2\_artist.png</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🖼️coat3\_artist.png</td></tr><tr style="height: 59.3906px;"><td colspan="8" style="height: 59.3906px;"><p class="callout info">Shown: The file structure for community packs, this example shows 2 packs (1 + 2) with 3 total coats.</p>

</td></tr></tbody></table>

<table border="1" id="bkmrk-file-type-location-d" style="border-collapse: collapse; width: 100%; height: 149.609px;"><colgroup><col style="width: 9.39431%;"></col><col style="width: 55.3759%;"></col><col style="width: 35.2297%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px;">**File Type**</td><td style="height: 29.7969px;">**Location**</td><td style="height: 29.7969px;">**Description**</td></tr><tr><td>🖼️ .png</td><td style="height: 30.1094px;">`config > swem > community-packs > textures > coats > legacy`</td><td style="height: 30.1094px;">Texture to be used for the custom coat.</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">🗒️ .json</td><td style="height: 30.1094px;">`config > swem > community-packs > jsons > coats`</td><td style="height: 30.1094px;">Information on artist(s) and obtaining.</td></tr></tbody></table>

---

#### JSON files  


JSON is a file that contains the important information SWEM needs to integrate a custom asset into the game and systems such as coat cycling or breeding. This is essentially **code** and needs to be filled out carefully to avoid causing errors!

- Type within the quotations `" "` unless directed to do otherwise.
- Keep all formatting including brackets `( ) { } [ ]`
- Separate coat tags by a comma (delete as applicable) **until the final variable.** ✅`["white","chestnut"]` **❌** `["white","chestnut",]`
- `lapis_cyclable` and `obtainable_by_breeding` must be `true` or `false`
- `base_colors` must use valid color tags options  
    ✅ `["black","gray","white","creamy","brown","dark_brown","chestnut"]` **❌** `["buckskin","dun"]`

<table border="1" id="bkmrk-credits-the-artist%28s" style="border-collapse: collapse; width: 100%; height: 178.781px;"><colgroup><col style="width: 21.7548%;"></col><col style="width: 78.2452%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Credits**</td><td style="height: 29.7969px;">The artist(s) to credit. This can be one, or multiple separated by a comma.</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Inspiration**</td><td style="height: 29.7969px;">The inspiration or reference, ie *"Secretariat"* or *"Bay Roan Sabino"*</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Models**</td><td style="height: 29.7969px;">The horse model it uses, this should use **legacy model (original)** until Destrier+ is added!</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Lapis Cyclable**</td><td style="height: 29.7969px;">Obtainable by cycling with lapis and redstone, if enabled.</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Obtainable By Breeding**</td><td style="height: 29.7969px;">Obtained by breeding, using color tags (below).</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px; background-color: rgb(206, 212, 217);">**Base Colors**</td><td style="height: 29.7969px;">Determines 'genetics' to pass on to foal, and selection of adult coats on growing up.</td></tr><tr><td colspan="2"><p class="callout info">Set tags you would expect to **get a coat from** (**IE:** black foal -&gt; black horse) and **NOT** the genetics the horse might **pass on**. Color tags and breeding outcomes are very basic and realism (**IE:** bay = red + black will result in unrealistic breeding and coat selection outcomes such as chestnut foal -&gt; bay horse). </p>

</td></tr></tbody></table>

<details id="bkmrk-default-json-%7B%C2%A0-%22cre"><summary>Default JSON</summary>

{  
 "credits": "Artist(s)",  
 "inspiration": "N/A",  
 "models": {  
 "legacy": "default:coats/legacy/coatname\_artist\_legacy.png",  
 "destrier": "",  
 "heavy\_draft": "",  
 "western\_sport": "",  
 "english\_sport": "",  
 "riding\_pony": ""  
 },  
 "lapis\_cyclable": true,  
 "obtainable\_by\_breeding": true,  
 "base\_colors": \["black","gray","white","creamy","brown","dark\_brown","chestnut"\]  
}

</details><details id="bkmrk-example-json-%7B%C2%A0-%22cre"><summary>Example JSON</summary>

{  
 "credits": "Bob Jones, Jon Bobs",  
 "inspiration": "Inspired by Valegro (Dressage Horse)",  
 "models": {  
 "legacy": "default:coats/legacy/valegro\_bobjones\_legacy.png",  
 "destrier": "",  
 "heavy\_draft": "",  
 "western\_sport": "",  
 "english\_sport": "",  
 "riding\_pony": ""  
 },  
 "lapis\_cyclable": false,  
 "obtainable\_by\_breeding": true,  
 "base\_colors": \["brown","dark\_brown"\]  
}

</details>---

#### PNG files

To create a new coat, or edit and existing one for the SWEM horse model you will need to use a program like Blockbench. The resources for this are pinned in our blockbench channel on [Discord](https://discord.com/channels/715626418893095012/748632231257440336/1117996750842630194).

---

#### Overriding Default Coats

You will still need to use a texture pack to override **default** SWEM coats. This has not changed with this update.

<details id="bkmrk-swem-coat-overrides-"><summary>Texturepack: Coat Overrides</summary>

<table border="1" style="width: 100%; height: 89.3907px;"><colgroup><col style="width: 13.6072%;"></col><col style="width: 16.303%;"></col><col style="width: 10.0128%;"></col><col style="width: 11.5533%;"></col><col style="width: 10.0128%;"></col><col style="width: 9.62773%;"></col><col style="width: 9.62773%;"></col><col style="width: 19.3838%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td rowspan="3" style="height: 29.7969px;">📂 TXP\_name  
</td><td style="height: 29.7969px;">📂 assets</td><td rowspan="3" style="height: 29.7969px;">📂 swem  
</td><td rowspan="3" style="height: 29.7969px;">📂 textures  
</td><td rowspan="3">📂 entity  
</td><td rowspan="3" style="height: 29.7969px;">📂 horse  
</td><td rowspan="3">📂 coats  
</td><td>🖼️ coat\_name.png</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🖼️ pack.png</td><td>🖼️ coat\_name.png</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🗒️ pack.mcmeta</td><td>📂 foal **(optional)**</td></tr><tr><td colspan="8"><p class="callout info">Shown: The file structure for texture packs overriding default horse +/- foal coats.</p>

</td></tr></tbody></table>

<table border="1" id="bkmrk-file-type-descriptio" style="border-collapse: collapse; width: 100%; height: 149.609px;"><colgroup><col style="width: 17.4583%;"></col><col style="width: 44.8%;"></col><col style="width: 37.7417%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px;">**File Type**</td><td style="height: 29.7969px;">**Description**</td><td style="height: 29.7969px;">**Note**</td></tr><tr><td>📂 TXP\_name</td><td>A folder with the name of your texture pack</td><td>  
</td></tr><tr><td>🖼️ pack.png</td><td>PNG image for your pack - displayed in game.</td><td>This must remain named `pack.png`</td></tr><tr><td>🗒️ pack.mcmeta</td><td style="height: 30.1094px;">Info on your pack's credits, description and version(s)</td><td style="height: 30.1094px;">This is a text-type document (ie notepad)</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">🖼️ coat\_name.png</td><td style="height: 30.1094px;">PNG for the coat to override.</td><td style="height: 30.1094px;">This must be named as in swem files</td></tr></tbody></table>

<p class="callout info">Coat names in SWEM files might not accurately align to in-game values. Example: `swem:sweetboi` = `13_m_sweetboi`</p>

[![image.png](https://wiki.swequestrian.com/uploads/images/gallery/2024-07/scaled-1680-/image.png)](https://wiki.swequestrian.com/uploads/images/gallery/2024-07/image.png)

<span style="color: rgb(126, 140, 141);">**Shown:**</span> Coat file names for all default SWEM coats in 1.20.1-1.5.0

</details>---

#### Note To Content Creators

This update will support you in sharing your content to a wider audience, as players no longer have to carefully pick and choose for a limited number of coats to override, and your coats can integrated into breeding and coat cycling (if enabled). To transition properly away from texture packs, we recommend:

- Upload your content in an appropriate format, such as a pack or individual json and png files.  
    → Continuing to provide texture packs is up to you!
- Set **simple, clear and easy to follow** terms of use (TOU) **or** fair-use guidelines.

<details id="bkmrk-terms-of-use-%28tou%29-y"><summary>TOU Info + Example</summary>

##### **WARNING**

By sharing your content publicly, you should acknowledge that **there is very limited legal recourse to enforce appropriate use of your content, license or not.** Using a highly restrictive terms of use is setting yourself up for frustration when it is inevitably violated, so for your sake and enjoyment of players we encourage sharing in a similar way to mods; allow anyone to use it for public or private use **provided downloads or support goes directly to the creator** (ie via Kofi).

##### **RECOMMENDATIONS**

<p class="callout warning">Avoid **editing** an agreement or expecting users to remain informed of any minor (or major) alterations.</p>

<p class="callout warning">Post your agreement where it can be **easily referenced** when browsing or downloading your content.  
→ It is ideal to have a public reference (ie Kofi post) and provide it with files or included in descriptions.  
→ It is not recommended to require access to an external source (ie Discord server) **unless you host files there!**  
</p>

<p class="callout info">Avoid **requiring** credit for use in media; it should be encouraged but **no credits does not equal insult!**  
→ **It is not standard practice to credit every creation (ie mods!)** in images you upload; nice if you do, but optional!  
→ It should only be "required" that users **credit where appropriate** (inspiration or reference), and **not falsely claim.**  
</p>

<p class="callout info">Avoid **prohibiting** inspiration or reference; **similarity is not proof of plagiarism!**  
→ It is possible for users to have the same idea, share the same reference, or take respectful inspiration!  
→ It should be expected that any work **clearly and** **directly** referenced or inspired by your creation is credited.</p>

<p class="callout info">Avoid **restrictive** use policies that are difficult to monitor and enforce.  
→ It is an unfortunate reality that players +/- servers will violate agreements, especially if they are restrictive.  
→ There is limited legal recourse to address this; so state what you are **willing and able to action if necessary!**  
</p>

<p class="callout info">Consider providing content in a compact format with **minimal individual downloads**!  
→ It is your choice, but players and servers will be less likely to distribute (or more likely to use) **easily** accessible files.  
→ It is suggested to provide creator pack(s) in bundles such as 'Bays', 'Pintos', '2023 Coats'  
</p>

<p class="callout info">Avoid uploading to **unsafe file hosting sites** or encouraging users to engage in **unsafe internet habits**.  
→ It is recommended to use popular sites such as Kofi, Google Drive.</p>

##### **EXAMPLE TERMS OF USE <span style="color: rgb(230, 126, 35);">(NOT A LEGAL CONTRACT OR LICENSE)</span>**

- `OWNERSHIP & AGREEMENT`  
    → The creator (name) retains all rights of ownership to this content  
    → The right to use this content is granted to you (player) in accordance with this agreement
- `USE`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used in content (images, videos) - credits are optional but appreciated.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used privately in singleplayer or a small private group.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used publicly in multiplayer.  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be used in reasonable commercial services `with/without` consent.  
     ✅🚫 Offered as part of a service (ie random / selected coat change) requiring real money  
     ✅🚫 Offered as a prize or reward for activity or events requiring real money  
     ✅🚫 Offered as an unlock via crowdfunding or engagement (ie server cost covered -&gt; unlock)  
     **NOTE: Commercial services must abide by Minecraft's EULA**
- `DISTRIBUTION`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be reuploaded `<span style="color: rgb(45, 194, 107);">with</span>/without` consent `<span style="color: rgb(45, 194, 107);">and</span>/or` credits `and/or` payment.  
     ✅🚫 Limited private use by friends or small groups  
     ✅🚫 Custom Community Packs (folder)   
     ✅🚫 Custom Modpacks (zip)  
     ✅🚫 Exceptions: Paid vs Free, Commissions (paid) or Gifts (prizes)  
     ✅🚫 Other: File Hosting Sites, Discord Servers etc
- `ALTERATIONS`  
    → This creation `<span style="color: rgb(45, 194, 107);">can</span>/not` be altered `with/<span style="color: rgb(45, 194, 107);">without</span>` consent and `<span style="color: rgb(45, 194, 107);">with</span>/without` credits for `<span style="color: rgb(45, 194, 107);">public/private</span>` use.  
     ✅🚫 Texture  
     ✅🚫 Information (json: name, description, color tags etc)  
     ✅🚫 Other conditions

</details>---

#### Known Issues

If you find an issue, please report it to our bugs channel on [Discord](https://discord.com/channels/715626418893095012/898242623716855868). We ask that you look to see if your issue was reported first!

- Community Packs not loading - fixed in swem-1.20.1-1.5-beta-5 **(COMING ASAP)**

---

#### Changelog

<details id="bkmrk-this-is-not-a-comple"><summary>View Changes</summary>

<p class="callout info">This is not a complete list of version changes / fixes. It is a changelog of relevant wiki-related version information.</p>

<table border="1" style="border-collapse: collapse; width: 100%; height: 121.781px;"><tbody><tr style="height: 29.7969px;"><td class="align-center" style="width: 13.3504%; height: 29.7969px;">**MC Version**</td><td class="align-center" style="width: 20.0257%; height: 29.7969px;">**Release**</td><td class="align-center" style="width: 66.6239%; height: 29.7969px;">**Notes**</td></tr><tr><td style="width: 13.3504%;">  
</td><td style="width: 20.0257%;">  
</td><td style="width: 66.6239%;">  
</td></tr></tbody></table>

</details>

# Resource Packs [WIP]

# Resource Packs

<p class="callout info">Resource Packs enable you to modify certain assets of Minecraft or Mods, like SWEM.</p>

#### Purpose

You can use Resource Packs to:

- Modify **default** horse coats
- Modify entity animations
- <span style="color: rgb(149, 165, 166);">**1.20.1-1.5+**</span> Add new animations
- Modify default horse model
- Modify item inventory or block textures

---

#### Limitations

Resource packs are an **override**, meaning the content a resource pack contains will **replace** the default asset.

You cannot\* use Resource Packs to:

- Add new coats\*
- Add new entities or breeds (see section on model overrides)

\* *There are some clever Resource Packs out there with entity variations, but this is not straightforward or simple!*

<details id="bkmrk-%5Bexpand%5D-model-overr"><summary>\[EXPAND\] Model Overrides</summary>

Several talented Creators have created "Add On" Resource Packs with "breed" models, or custom features (ie mane variations).

- Packs may include one option (ie Arabian or Fjord)
- Packs may support multiple breeds +/- features
- Packs may support the default model coats (ideally) or override it entirely

**RELEVANT INFORMATION (USERS / SERVERS)**

<p class="callout info">Model Overrides are used at your own "risk" and support for issues should be sought via the **Pack** **Creator** <span style="text-decoration: underline;">not</span> SWEM.</p>

**How do they work?**

- In simple terms, it works by adding extra blocks to the default model
- If a coat artist leaves the blocks uncolored (invisible) you will see all / some of the default horse
- If a coat artist colors the blocks in, you will see those additional blocks on the default horse  
    `EXAMPLE` If a coat texture color in blocks added around the hoof, a horse would have "feathers"

**Can I use more than one model?**

- If you install multiple model override packs, only the **highest in load order will apply**
- If you want models from different Creators, they would have to merge their packs

**Can I use model overrides with a community pack or coat replacement resource pack?**

- If the model does not modify (only add on to) the default model, custom coats should work fine
- If not, this may 'break' default or custom coats `Example:` Horses with no mane or tail using some models
- It might be rare to get a 'custom model coat' if you are mostly using ones designed for the default model

**Can I use model overrides with an animation pack (ie Dressage animations)?**

- <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> **TBC** </span> It is unlikely custom models will support all animation packs
- If you load a model pack **above** an animation pack, it will override any animations they both share
- If you load a model pack **below** an animation pack, it may not correctly animate the custom model

**Can I use model overrides on a server?**

- `SERVER` You may be able to install a model resource pack server-side
- `CLIENT (PLAYER)` If you install a model override in multiplayer, only you will see it  
    → Read the section about community packs + coat replacements above (may affect what you see in game)  
    → <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> **TBC** </span> Server packs may override client side unless you can opt out of using it

**RELEVANT INFORMATION (CREATORS)**

<p class="callout warning">Model overrides use copyrighted SW assets and must be **FREE USE ONLY**   
→ You can accept **optional** donations  
→ You can sell coat textures that require your add on, provided it is 100% your own work (no SW coat edits)  
</p>

- You should not modify any of the core blocks involved in tack rendering
- You should **add to** (not modify where possible) the model to avoid breaking default + custom coats
- You will need to adjust the default animations for any additional blocks added
- You should be able to (optional) add support for custom animations in animation packs  
    → Consent may be required to include a modified animation from other Creators  
    → <span style="background-color: rgb(224, 62, 45); color: rgb(255, 255, 255);"> **TBC** </span> If add on models can support "new" custom animations via 1.20.1-1.5+ features

</details>---

#### Creating Basic Resource Pack Files

This guide covers how to create a basic resource pack folder. Alternatively, download the premade <span style="color: rgb(255, 255, 255);">**<span style="background-color: rgb(224, 62, 45);"> \[TEMPLATE\] </span>**</span> on Discord.

<details id="bkmrk-%5Bexpand%5D-instruction"><summary>\[EXPAND\] Instructions</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> CREATE YOUR RESOURCE PACK FOLDER**

1. Create a new folder   
    → It can be anywhere for now (ie Documents)
2. Name your resource pack  
    → This can include capitals, some symbols and spaces
3. Go inside the folder
4. Create a new folder here
5. Name it `assets`  
    → This must be in lowercase exactly as shown

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> CREATE YOUR PACK.MCMETA FILE**

1. Open a blank text editor file using Notepad (Windows) or TextEdit (Mac)
2. Paste in the pack template (below)
3. Edit the template to your pack  
    → `description` Any information to display **in game** **✅** `"description": "Pack Name V1.0 By Creator Name"`   
     <span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **Note:** </span> Supports [color + format](https://minecraftitemids.com/color-codes) `&l&9Pack Name V1.0 &0By &dCreator` = `<strong><span style="color: rgb(35, 111, 161);">Pack Name  V1.0</span></strong> By <span style="color: rgb(185, 106, 217);">Creator</span>`  
    → `pack_format` Which [format](https://minecraft.wiki/w/Pack_format) (MC version) is supported **✅** `"pack_format": 15` = `MC 1.20 - 1.20.1`  
     <span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> **Note:** </span> Format gives a harmless warning when a resource pack is used in other versions (even if it works fine)
4. Select `file > save as`
5. Select the resource pack folder (not assets)
6. Name the file `pack.mcmeta` in lowercase
7. Save as the correct file type:  
    → **Windows:** `Save As Type: All Files` (Drop down menu, change from .txt)  
    → **Mac:**
8. Check it displays as a `MCMETA` file type in your folder

<details><summary>\[EXPAND\] pack.mcmeta Template</summary>

{  
 "pack": {  
 "description": "Text Here",  
 "pack\_format": 15  
 }  
}

</details>**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> CREATE YOUR PACK ICON**

1. Choose or create an icon for your pack
2. Name it `pack` and save it as a `.png`
3. Paste it in your resource pack folder (not assets)

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP FOUR: </span> ADD YOUR CONTENT**

Go to the section(s) below for the content you want to add.

</details>---

#### Custom Coat Overrides

<p class="callout info">This is to **override one or more default coats** - to add **new** coats use a [Community Pack](https://wiki.swequestrian.com/books/swequestrian-mod/page/creators-corner-wip)!</p>

This guide will not cover how to create a coat, for information please read our [resources](https://discord.com/channels/715626418893095012/748632231257440336/1117996750842630194) on Discord.

<details id="bkmrk-%5Bexpand%5D-instruction-1"><summary>\[EXPAND\] Instructions</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE: </span> CREATE A COAT TEXTURE**

1. Create your coat texture in Blockbench
2. Choose a coat to override from the list of default coats
3. Save the texture as a `.png` file
4. Name the texture to match the coat it will replace

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP TWO: </span> CREATE ASSETS SUB-FOLDERS FOR YOUR COAT**

1. Go inside `assets`
2. Create a folder called `swem`
3. Inside that, create a folder called `textures`
4. Inside that, create a folder called `entity`
5. Inside that, create a folder called `horse`
6. Inside that, create a folder called `coats`
7. Paste your texture file here  
    → If you have more than one override you can add them also

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> FINAL STEPS**

1. Your pack is ready and may work unzipped
2. You can zip it so it is easier to share or keep it unzipped to add new files  
    → If your zip does not show up in game, check your files are not too deep  
    → **✅Pack Name (Zip)** &gt; assets / pack.mcmeta / pack  
    → **❌Pack Name (Zip)** &gt; Pack Folder &gt; assets / pack.mcmeta / pack
3. Load into Minecraft
4. Open the Resource Pack menu
5. Open the folder (button)
6. Paste in your Resource Pack
7. Enable the Resource Pack
8. Check it is working in game  
    → Summon the coat you chose to override  
    → Confirm it uses the replacement coat, not original  
    → Check there are no texture errors and it looks correct on the horse

This page will not provide any resources for troubleshooting errors with texture files.   
You can look up a tutorial for texturing entities or ask for assistance with details on your issue in our Tech Help channels.

</details><details id="bkmrk-%5Bexpand%5D-default-coa"><summary>\[EXPAND\] Default Coat Names</summary>

![image.png](https://wiki.swequestrian.com/uploads/images/gallery/2024-07/scaled-1680-/image.png)

</details><table border="1" id="bkmrk-%F0%9F%93%82-txp_name-%F0%9F%93%82-assets-" style="width: 100%; height: 143.188px;"><colgroup><col style="width: 13.6072%;"></col><col style="width: 16.303%;"></col><col style="width: 10.0128%;"></col><col style="width: 11.5533%;"></col><col style="width: 10.0128%;"></col><col style="width: 9.62773%;"></col><col style="width: 9.62773%;"></col><col style="width: 19.3838%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td rowspan="3" style="height: 89.3907px;">📂 TXP\_name  
</td><td style="height: 29.7969px;">📂 assets</td><td rowspan="3" style="height: 89.3907px;">📂 swem  
</td><td rowspan="3" style="height: 89.3907px;">📂 textures  
</td><td rowspan="3" style="height: 89.3907px;">📂 entity  
</td><td rowspan="3" style="height: 89.3907px;">📂 horse  
</td><td rowspan="3" style="height: 89.3907px;">📂 coats  
</td><td style="height: 29.7969px;">🖼️ coat\_name.png</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🖼️ pack.png</td><td style="height: 29.7969px;">🖼️ coat\_name.png</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🗒️ pack.mcmeta</td><td style="height: 29.7969px;">📂 foal **(optional)**</td></tr><tr style="height: 53.7969px;"><td colspan="8" style="height: 53.7969px;"><p class="callout info">Shown: The file structure for texture packs overriding default horse +/- foal coats.</p>

</td></tr></tbody></table>

<table border="1" id="bkmrk-file-type-descriptio" style="border-collapse: collapse; width: 100%; height: 149.609px;"><colgroup><col style="width: 17.4017%;"></col><col style="width: 44.8153%;"></col><col style="width: 37.7831%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px;">**File Type**</td><td style="height: 29.7969px;">**Description**</td><td style="height: 29.7969px;">**Note**</td></tr><tr><td>📂 Pack Name</td><td>A folder with the name of your resource pack</td><td>  
</td></tr><tr><td>🖼️ pack.png</td><td>PNG image for your pack - displayed in game.</td><td>This must remain named `pack.png`</td></tr><tr><td>🗒️ pack.mcmeta</td><td style="height: 30.1094px;">MCMETA file with your pack's description and version(s)</td><td style="height: 30.1094px;">This must remain named `pack.mcmeta`</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">🖼️ coat\_name.png</td><td style="height: 30.1094px;">PNG for the coat to override.</td><td style="height: 30.1094px;">This must be the name of a valid swem coat</td></tr></tbody></table>

<p class="callout info">Coat names in files might not be identical to in-game names or values. **Example** `swem:sweetboi` = `13_m_sweetboi`  
→ You must use the **file** names, a list of valid names can be found above  
</p>

---

#### Custom Animation Overrides / Additions

This guide will not cover how to create animations, for information please read our <span style="color: rgb(255, 255, 255);">**<span style="background-color: rgb(224, 62, 45);"> \[RESOURCES\] </span>**</span> on Discord.

<details id="bkmrk-%5Bexpand%5D-instruction-2"><summary>\[EXPAND\] Instructions</summary>

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE \[A\]: </span> CREATE A NEW ANIMATION**

1. Create an animation in Blockbench
2. Save the `swem_horse.json` file  
    → This should include your animation(s) **and** all default animations

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE \[B\]: </span> MODIFY AN EXISTING ANIMATION**

1. Modify one or more default animation in Blockbench
2. Save the `swem_horse.json` file

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP ONE \[B\]: </span> CREATE ASSETS SUB-FOLDERS FOR YOUR COAT**

1. Go inside `assets`
2. Create a folder called `swem`
3. Inside that, create a folder called `animations`
4. Paste your `swem_horse.json` file here

**<span style="background-color: rgb(132, 63, 161); color: rgb(255, 255, 255);"> STEP THREE: </span> FINAL STEPS**

1. Your pack is ready and may work unzipped
2. You can zip it so it is easier to share or keep it unzipped to add new files  
    → If your zip does not show up in game, check your files are not too deep  
    → **✅Pack Name (Zip)** &gt; assets / pack.mcmeta / pack  
    → **❌Pack Name (Zip)** &gt; Pack Folder &gt; assets / pack.mcmeta / pack
3. Load into Minecraft
4. Open the Resource Pack menu
5. Open the folder (button)
6. Paste in your Resource Pack
7. Enable the Resource Pack
8. Check it is working in game  
    → Tame and mount a horse  
    → Use `/swem rrp anim <Animation Name>` to trigger the animation  
    → Confirm the animation works as expected

This page will not provide any resources for troubleshooting errors with animations.   
You can look up a tutorial for animating or ask for assistance with details on your issue in our Tech Help channels.

</details><table border="1" id="bkmrk-%F0%9F%93%82-pack-name-%F0%9F%93%82-assets" style="width: 100%; height: 132.984px;"><colgroup><col style="width: 12.8725%;"></col><col style="width: 14.7795%;"></col><col style="width: 9.89273%;"></col><col style="width: 13.23%;"></col><col style="width: 49.2253%;"></col></colgroup><tbody><tr style="height: 19.5938px;"><td rowspan="3" style="height: 79.1876px;">📂 Pack Name  
</td><td style="height: 19.5938px;">📂 assets</td><td rowspan="3" style="height: 79.1876px;">📂 swem  
</td><td rowspan="3" style="height: 79.1876px;">📂 animations  
</td><td style="height: 19.5938px;">🗒️ swem\_horse.json

</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🖼️ pack.png</td><td rowspan="2" style="height: 59.5938px;">🗒️ swem\_horse\_foal.json

</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">🗒️ pack.mcmeta</td></tr><tr style="height: 53.7969px;"><td colspan="5" style="height: 53.7969px;"><p class="callout info">Shown: The file structure for animation packs overriding default horse +/- foal coats.</p>

</td></tr></tbody></table>

<table border="1" id="bkmrk-file-type-descriptio-1" style="border-collapse: collapse; width: 100%; height: 149.609px;"><colgroup><col style="width: 17.4017%;"></col><col style="width: 44.8153%;"></col><col style="width: 37.7831%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px;">**File Type**</td><td style="height: 29.7969px;">**Description**</td><td style="height: 29.7969px;">**Note**</td></tr><tr><td>📂 Pack Name</td><td>A folder with the name of your resource pack</td><td>  
</td></tr><tr><td>🖼️ pack.png</td><td>PNG image for your pack - displayed in game.</td><td>This must remain named `pack.png`</td></tr><tr><td>🗒️ pack.mcmeta</td><td style="height: 30.1094px;">MCMETA file with your pack's description and version(s)</td><td style="height: 30.1094px;">This must remain named `pack.mcmeta`</td></tr><tr style="height: 30.1094px;"><td style="height: 30.1094px;">🗒️ swem\_horse.json</td><td style="height: 30.1094px;">JSON file with your new / modified animations</td><td style="height: 30.1094px;">This must remain named `swem_horse.json`</td></tr></tbody></table>