# 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

General Information

Community Packs -> Whole Packs (ex. a completed pack with all textures, names, and coins)

Content Packs -> Sets of Content able to be put into Community Packs (ex. a few peices of tack textures with their matching jsons)

# Community Packs

<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

---

#### 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>

# Coats [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>

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

---

#### Important - Update Changes

<table border="1" id="bkmrk-features-changes-sum" style="border-collapse: collapse; width: 100%; height: 633.719px;"><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);">**Features**</span></td><td class="align-center" style="height: 29.7969px;"><span style="color: rgb(255, 255, 255);">**Changes**</span></td></tr><tr style="height: 150.891px;"><td class="align-center" style="height: 150.891px;">**Summon**</td><td style="height: 150.891px;">Minecraft `/summon` results in 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: 395.25px;"><td class="align-center" style="height: 395.25px;">**Coat Data**</td><td style="height: 395.25px;">NBT no longer uses `Variant: #` and instead uses `Behaviors[6].Coat`

Data modify commands must set a valid 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 key restrictions - which may be useful to some servers.*</p>

**Get the value (id + name) of a Horse's coat**

<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 the value of a Horse's 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: 57.7812px;"><td class="align-center" style="height: 57.7812px;">**Model**</td><td style="height: 57.7812px;">Coats and commands must specify model - this is to support **future** options.

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

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

---

#### Frequently Asked Questions &amp; Fundamentals

This section has drop-downs for FAQs and expanded information about Community Packs.

<details id="bkmrk-%5B1%5D-community-pack-%26"><summary>\[1\] Community Pack &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 another name for a Community Pack. Content Packs generally have less content, or even a single file. On pasting, it will merge into any Community Pack with the same name.

- Creators can use a single (or multiple) consistent pack names
- Creators can provide updates and fixes to their pack for select or individual files
- Players require fewer overall Community Packs
- Players can easily search in-game by Creator **Example:** `arishant_kofi:`
- \[OR\] Players can easily search in-game by Theme **Example:** `fantasy_mounts:` or `bays:`

**⮞ HOW DO I KNOW IF A PACK IS PREMADE (READY TO USE)?** Community Packs should clearly state if they are a ready to use folder, or individual files. If that is not the case:

- Look at the file contents (unzip the file if it comes zipped)  
      
    ✅ Must be a folder with a lowercase name. **Example:** `arishant_kofi`  
    ✅ Must have two folders inside it: `json` and `textures`  
    ✅ Must have `coats` inside json and `coats > legacy` inside textures  
    ✅ Must have at least one file inside each folder - only jsons (text file) and png (texture file) in relevant folders  
      
    **❌** 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 set up correctly!</p>

**⮞ WHAT IF PACKS HAVE AN IDENTICAL NAME?** Community Packs could share a generic name like `free_coats` or `kofi_coats`.   
Generally, this is not an issue, but you should be aware:

- Folders will merge into one that includes the files of each
- File will not override or replace unless they have an identical name  
    This is **unlikely** if Creators use the recommended format of `coatname_artist`  
    This could replace updated (fixed) files with outdated ones that share the same name  
    This could replace optional variant files with alternatives (ie coat with shoes vs coat without

<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 fine.
- 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!

</details><details id="bkmrk-%5B2%5D-modified-packs-%26"><summary>\[2\] Modified Packs &amp; Files</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 UPLOAD A COMMUNITY PACK +/- MODIFIED?** `PNG FILES` The Creator has the right to set and enforce appropriate use of their content.

- You should not modify, distribute or monetize their work without explicit consent
- This includes uploading their work in any public platform (ie Discord, for use by a MP server)

`JSON FILES` These files are an asset under SWEM and not the property of Creator(s).

- You can re-upload them for **free.**
- You can provide JSON override packs.  
    This **excludes** any modification with **false credits**, **removed credits** or unreasonable modification to inspiration.  
    This **excludes** any uploads that includes PNG files without Creator' consent.  
    This must comply with any platform or community guidelines (ie no unapproved uploads).

**⮞ CAN I RENAME A PACK?  
<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 be useful to organize your custom content or use simpler in-game pack IDs.   
You must set a unique **lowercase** name with no spaces or symbols for the pack to remain valid.

**⮞ CAN I RENAME A COAT? <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, though this is **not recommended**.

- Changes must be updated for json and png file, as well as the json texture path.
- The coat will appear white on reload unless provided with alternative files for the previous ID + name.

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

**⮞ CAN I EDIT COAT 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, however:</span>

- <span style="color: rgb(0, 0, 0);">Client-side edits will only apply to 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 replicate this to avoid seeing 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, it is generally safe to modify coat info.

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

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

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

</details>---

#### Using A Community Pack

This section has a step-by-step guide for installing **premade** Community Packs. To learn

#### \[?\] Features

#### Troubleshooting / Common Issues

# Tack

Tack

# Animations

Animations