⮞ 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

There can still be other errors that prevent a pack working, but this criteria means the pack is structured correctly!

⮞ 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
  

 Creators 

• 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.

Always check that merged files maintain the correct folder structure and file names are valid (ie not coat_name_copy)

⮞ 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.

Always read the Creator's Terms Of Use (TOU) as significant non-private alterations or reupload may be prohibited!

⮞ 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 -> ✅ Palomino (Dreamwork's Spirit: "Esperanza") ❌ N/A

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

 Multiplayer  No. This may prevent you from seeing any custom coats, even if you have all the correct files.

 Singleplayer  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?

 Multiplayer  No. This may prevent you from seeing any custom coats or tack, even if you have all the correct files.

 Singleplayer  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).

You should use standard naming format coatname_artist with appropriate artist credit by name!

⮞ CAN I EDIT CUSTOM CONTENT INFORMATION (JSON)?

 Multiplayer  Yes. Important information:

• Client-side (player) edits will only apply to your singleplayer worlds.
• 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)
  

 Singleplayer  Yes, depending on type:

You must not remove or (unreasonably) modify Artist credits +/- reference and inspiration comments.

⮞ HOW TO ADD COMMUNITY PACKS TO A SERVER?

 Multiplayer  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.

See individual pages for troubleshooting common issues for each feature.

⮞ 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?

Always read the Creator's Terms Of Use (TOU) as public multiplayer use, alterations or reupload may be prohibited!

⮞ 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.

PCs with limited resources or low performance may have a limit on how much custom content it can realistically support.

This is not a complete list of version changes / fixes. It is a changelog of relevant wiki-related version information.

⮞ YOU MUST NOT 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 MUST NOT 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 FREE CONTENT THAT ACCEPTS AN OPTIONAL 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 90%* 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 90%* your own work
  → 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 
  

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.

⮞ YOU MUST NOT SELL, PROMOTE OR FEATURE SWEM IN ANY CONTENT OR MEDIA THAT INCLUDES:

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

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

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.

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.

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!

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'

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.

EXAMPLE TERMS OF USE (NOT A LEGAL CONTRACT OR LICENSE)

• 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 can/not be used in content (images, videos) - credits are optional but appreciated.
  → This creation can/not be used privately in singleplayer or a small private group.
  → This creation can/not be used publicly in multiplayer.
  → This creation can/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 -> unlock)
      NOTE: Commercial services must abide by Minecraft's EULA
  
  
• DISTRIBUTION
  → This creation can/not be reuploaded with/without consent and/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 can/not be altered with/without consent and with/without credits for public/private use.
      ✅🚫 Texture
      ✅🚫 Information (json: name, description, color tags etc)
      ✅🚫 Other conditions 

Beta 5 "legacy": "default:coats/legacy/coat_artist.png"

Beta 7 "legacy": "default:legacy/coat_artist.png"

1.5.x "legacy": "legacy/coat_artist.png"

⮞ 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.
 PACKS  artist_packname Example: arishant_freecoats
 COATS  coatname_artist Example: maple_arishant
 TACK  See naming format resources below.

You might notice some items recommend credits before or after the name, this is for a few reasons!
 PACKS  Sorted alphabetically in folder and in-game, so packs group by artist instead of pack name
 COATS  Listed alphabetically in game once filtered by pack. Example: apple_artist / banana_artist / coconut_artist
 TACK  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.

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.

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.

{
  "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"]
}

⮞ 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 & 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.

 RECOMMENDATION
→ Set one or two tag(s) for a foal color you would expect to get the coat from Example: Black Foal -> Black Horse 

   COMMUNITY PACK TROUBLESHOOTING   
FOLLOW EACH STEP CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP AFTER 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 -> 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 in our Discord with a description of the issue(s).
  
• All files correct but some do not load
  → Invalid files prevent others from being registered on load.
  → Files are suspected to load in alphanumerical order (A-Z)
  → Note the names of coats you CAN summon or change coats of, then find the first letter you cannot.
  → Sort your community pack folder by ascending name - identify the file AFTER the last one visible in game.
  → Use the 
  

   SOLUTIONS & SUGGESTIONS   
ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES

It is not recommended to modify packs from a Creator unless 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!

⮞ 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 or symbols ✅artist_kofi ❌ Artist Kofi Coats (1)
  → Pack includes at least one .json and .png file in the correct folder
      📁 jsons > 📁 coats > JSON FILES HERE
      📁 textures > 📁 coats > 📁 legacy > 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).
  → Paste the text here and validate to check it has no errors.
  → 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 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": "default: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 OR NOTHING WORKED

• Create a post in Tech Help 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
  

This is the standard format used in the Beta pack. It is recommended to use a consistent naming format as shown here.

{
  "display": {
    "name": "Name Bridle",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "iron",
    "amount": 2
  },
  "meta": {
    "name": "name_bridle",
    "icon": "bridle/name_bridle_icon.png",
    "type": "bridle",
    "data": {
      "model_type": "western / english (select one)",
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "bridle": "bridle/name_bridle_bit_legacy.png",
          "halter": "bridle/name_bridle_legacy.png"
        }
      },
      "rack": {
        "bridle": "bridle/rack_bridle_name_bridle.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Blanket",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "iron",
    "amount": 2
  },
  "meta": {
    "name": "name_blanket",
    "icon": "blanket/name_blanket_icon.png",
    "type": "blanket",
    "data": {
      "color": [255, 190, 0],
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "blanket": "blanket/name_blanket_legacy.png"
        }
      },
      "rack": {
        "saddle": "blanket/rack_saddle_name_blanket.png",
        "blanket_5": "blanket/rack_blanket_5_name_blanket.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Saddle",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "gold",
    "amount": 4
  },
  "meta": {
    "name": "name_saddle",
    "icon": "saddle/name_saddle_icon.png",
    "type": "saddle",
    "data": {
      "model_type": "western / english (select one)",
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "saddle": "saddle/name_saddle_legacy.png"
        }
      },
      "rack": {
        "saddle": "saddle/rack_saddle_name_saddle.png",
        "horse_armor": "saddle/rack_horse_armor_name_saddle.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Girth Strap",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "copper",
    "amount": 3
  },
  "meta": {
    "name": "name_girth_strap",
    "icon": "girth_strap/name_girth_strap_icon.png",
    "type": "girth_strap",
    "data": {
      "color": [255, 190, 0],
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "girth_strap": "girth_strap/name_girth_strap_legacy.png"
        }
      },
      "rack": {
        "saddle": "girth_strap/rack_saddle_name_girth_strap.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Breast Collar",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "copper",
    "amount": 5
  },
  "meta": {
    "name": "name_breast_collar",
    "icon": "breast_collar/name_breast_collar_icon.png",
    "type": "breast_collar",
    "data": {
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "breast_collar": "breast_collar/name_breast_collar_legacy.png"
        }
      },
      "rack": {
        "blanket": ""
      }
    }
  }
}

{
  "display": {
    "name": "Name Wraps",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "iron",
    "amount": 1
  },
  "meta": {
    "name": "name_leg_wraps",
    "icon": "leg_wraps/name_leg_wraps_icon.png",
    "type": "leg_wraps",
    "data": {
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "leg_wraps": "leg_wraps/name_leg_wraps_legacy.png",
          "hoof": "leg_wraps/name_leg_wraps_hoof_legacy.png"
        }
      },
      "rack": {
        "blanket": ""
      }
    }
  }
}

{
  "display": {
    "name": "Name Saddle Bag",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "gold",
    "amount": 1
  },
  "meta": {
    "name": "name_saddle_bag",
    "icon": "saddle_bag/name_saddle_bag_icon.png",
    "type": "saddle_bag",
    "data": {
      "color": [255, 190, 0]
    },
    "textures": {
      "horse": {
        "legacy": {
          "saddle_bag": "saddle_bag/name_saddle_bag_legacy.png"
        }
      },
      "rack": {

      }
    }
  }
}

{
  "display": {
    "name": "Name Horse Armor",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "amethyst",
    "amount": 4
  },
  "meta": {
    "name": "name_horse_armor",
    "icon": "horse_armor/name_horse_armor_icon.png",
    "type": "horse_armor",
    "data": {
      "tier": "amethyst"
    },
    "textures": {
      "horse": {
        "legacy": {
          "armor": "horse_armor/name_horse_armor_legacy.png",
          "wings": "horse_armor/name_horse_armor_wings_legacy.png"
        }
      },
      "rack": {
        "horse_armor": "horse_armor/rack_horse_armor_name_horse_armor.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Halter",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "emerald",
    "amount": 4
  },
  "meta": {
    "name": "name_halter",
    "icon": "halter/name_halter_icon.png",
    "type": "halter",
    "data": {
      "color": [255, 190, 0],
      "can_wear_armor": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "halter": "halter/name_halter_legacy.png"
        }
      },
      "rack": {
        "halter_lead": "halter/rack_halter_lead_name_halter.png"
      }
    }
  }
}

{
  "display": {
    "name": "Name Pasture Blanket",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "emerald",
    "amount": 4
  },
  "meta": {
    "name": "name_pasture_blanket",
    "icon": "pasture_blanket/name_pasture_blanket_icon.png",
    "type": "pasture_blanket",
    "data": {
      "color": [255, 190, 0]
    },
    "textures": {
      "horse": {
        "legacy": {
          "pasture_blanket": "pasture_blanket/name_pasture_blanket_legacy.png"
        }
      },
      "rack": {
        "pasture_blanket_long_5": "pasture_blanket/rack_pasture_blanket_5_long_name.png",
        "pasture_blanket_short_3": "pasture_blanket/rack_pasture_blanket_3_short_name.png"
      }
    }
  }
}

{
  "display": {
    "name": "Armored Name Pasture Blanket",
    "credits": "Artist(s)",
    "inspiration": "N/A"
  },
  "cost": {
    "coin": "diamond",
    "amount": 2
  },
  "meta": {
    "name": "name_pasture_blanket_armored",
    "icon": "pasture_blanket/name_pasture_blanket_armored_icon.png",
    "type": "pasture_blanket",
    "data": {
      "color": [255, 190, 0],
      "is_armored": true
    },
    "textures": {
      "horse": {
        "legacy": {
          "pasture_blanket": "pasture_blanket/name_pasture_blanket_armored_legacy.png"
        }
      },
      "rack": {
        "pasture_blanket_long_5": "pasture_blanket/rack_pasture_blanket_5_long_name.png",
        "pasture_blanket_short_3": "pasture_blanket/rack_pasture_blanket_3_short_name.png"
      }
    }
  }
}

   COMMUNITY PACK TROUBLESHOOTING   
FOLLOW EACH STEP CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP AFTER 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 -> 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 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.

   SOLUTIONS & SUGGESTIONS   
ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES

It is not recommended to modify packs from a Creator unless 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!

⮞ 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 > 📁 tack > 📁 [type]  > JSON FILES HERE
      📁 textures > 📁 tack > 📁 [type] > 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] <- 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).
  → Paste the text here and validate to check it has no errors.
  → 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.
  
   KNOWN ISSUE  Opening or modifying a pack on a Mac creates a .DS_store file. Should be fixed in 1.5.x.
  → This is usually invisible to Mac users and prevents the pack from working. Discord: Bug Report
  
  If this is ALL correct or changes did not work, paste your .json file in Tech Help 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 
      Note:   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 & 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 OR NOTHING WORKED

• Create a post in Tech Help 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

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
2. Paste in the contents of your JSON file
3. Click Validate JSON to check the file
4. View the output below

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.

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.

Credits: Jenny

  HORSE TACK TEXTURES  

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 > 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.  TBC  Create a new texture that is 512 x 512 pixels (16x)
   → Alternatively, import a base texture to use as a template
        Note:  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 > 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
    

  TACK RACK TEXTURES  

  TACK ICON TEXTURES  

1. Download / Open Blockbench
2. File > New > 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
        Note:  These are found in assets > swem > textures > item [item_name]
5.  TBC  Saving

⮞ 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.

This update has been modified to continue support for Ace's Datapack found HERE in our Discord.

⮞ 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 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. 

⮞ 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.

⮞ WHAT IS A COLOR TAG?
Color tags determine which coat a horse receives when it is converted from a vanilla horse, or grows up from a foal.
There are seven possible tags: black, gray, white, creamy, brown, dark_brown, chestnut

⮞ HOW DOES CONVERTING VANILLA -> SWEM HORSES WORK?
Vanilla horses are categorized so you should receive a similar coat color, ie a black horse stays black on conversion.

⮞ HOW DOES BREEDING SWEM HORSES WORK?
The coat your horse has will have one or more color tags assigned in code. 
Example If your horse is a black tobiano horse they may (depending on info file) have black and white color tags. 

When breeding two horses together, the foal will be randomly assigned one tag from its parents and use that color foal coat.
Example If the mare has white and black and the stallion has chestnut, the foal could be black, white or chestnut only.

When the foal grows up, they will randomly roll for ALL adult coats that include their foal color.
Example If the foal is brown it will choose from any coat that includes the brown tag.

If you change a horse's coat via lapis/redstone or command, any future breeding will use the new coat's tag(s).

⮞ THESE ARE NOT REAL GENETICS - YOU DON'T GET REALISTIC RESULTS FROM BREEDING!
The color tags are very simple with just seven total tags. You may get coats that make no sense for genetics such as a pure white foal growing up into a leopard appaloosa because the coat tag includes white. This system is in no way trying to be accurate to real life genetics as the current breeding code was intended to be "vanilla style" until a more complex genetics system is possible!

⮞ HOW CAN I EDIT THE COLOR TAGS A HORSE HAS?
You can tweak the information for custom coats in config > swem > community-packs > [pack_name] > jsons > coats

• You can add or remove color tags but be sure to use the correct format and only enter valid color values!
• You can edit obtaining conditions such as lapis_cyclable or obtainable_by_breeding from true / false

It is not recommended to edit community packs that you require on a server - try to keep server / client files the same!

Wrongly formatted JSON files can break your pack - use Creators Corner for info if you don't know what you're doing!

   COMMUNITY PACK TROUBLESHOOTING   
FOLLOW EACH STEP CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP AFTER 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

FOR VERSION 1.20.1-1.5 OR ABOVE, YOU NEED TO MANUALLY UPDATE THE OFFICIAL PACK. SEE HERE (DISCORD)

• 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 -> 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 in our Discord with a description of the issue(s).
  

   SOLUTIONS & SUGGESTIONS   
ALWAYS SHUT DOWN THE GAME + RELOAD AFTER MAKING CHANGES

It is not recommended to modify packs from a Creator unless 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!

⮞ 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 > 📁 coats > JSON FILES HERE
      📁 textures > 📁 coats > 📁 legacy > 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 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": "default: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 OR NOTHING WORKED

• Create a post in Tech Help 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  
  

⮞ 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.

⮞ 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.

   COMMUNITY PACK TROUBLESHOOTING   
FOLLOW EACH STEP CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP AFTER USING THIS!

⮞ COMING SOON

  DO NOT UPLOAD PAID/PRIVATE PACKS WITH TEXTURES FROM CREATORS WITHOUT CONSENT  

⮞ 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?
 [TBC]  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?
 [TBC]  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?
 [TBC]  

⮞ HOW DO ANIMATION PACKS APPEAR IF A PLAYER IS MISSING THE RESOURCE PACK?
 [TBC]  

   ANIMATION PACK TROUBLESHOOTING   
FOLLOW EACH STEP CAREFULLY + NOTE ISSUES AS YOU GO. ONLY REQUEST HELP AFTER USING THIS!

⮞ COMING SOON

  DO NOT UPLOAD PAID/PRIVATE PACKS WITH FILES FROM CREATORS WITHOUT CONSENT  

                                                                             SUPPORT & FEATURES                                                                            

⮞ 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 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.

                                                                        USE ON SAVES & SERVERS                                                                       

⮞ 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.
Please be mindful of creators and do not distribute or use content in a way that is not explicitly permitted!

⮞ MULTIPLAYER SERVERS (SERVER SIDE ONLY)?
Community packs on server only may not be possible and would likely violate the terms of use for custom content.

⮞ 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?
TBC. Probably fine.

                                                                   MODIFYING A COMMUNITY PACK                                                                   

⮞ 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).
   → DO NOT REMOVE CREDITS (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>

                                                                                           OTHER                                                                                           

⮞ SEE COAT NAME?
It is not currently possible to find out the name or artist for a coat in-game without using a command:
/data get entity @e[type=swem:swem_horse,sort=nearest,limit=1] Behaviors[6].Coat

{
  "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"]
}

{
  "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"]
}

Coat names in SWEM files might not accurately align to in-game values. Example: swem:sweetboi = 13_m_sweetboi

Shown: Coat file names for all default SWEM coats in 1.20.1-1.5.0

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

Avoid editing an agreement or expecting users to remain informed of any minor (or major) alterations.

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!

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.

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.

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!

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'

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.

EXAMPLE TERMS OF USE (NOT A LEGAL CONTRACT OR LICENSE)

• 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 can/not be used in content (images, videos) - credits are optional but appreciated.
  → This creation can/not be used privately in singleplayer or a small private group.
  → This creation can/not be used publicly in multiplayer.
  → This creation can/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 -> unlock)
      NOTE: Commercial services must abide by Minecraft's EULA
  
  
• DISTRIBUTION
  → This creation can/not be reuploaded with/without consent and/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 can/not be altered with/without consent and with/without credits for public/private use.
      ✅🚫 Texture
      ✅🚫 Information (json: name, description, color tags etc)
      ✅🚫 Other conditions 

This is not a complete list of version changes / fixes. It is a changelog of relevant wiki-related version information.

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)

Model Overrides are used at your own "risk" and support for issues should be sought via the Pack Creator not SWEM.

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)?

• TBC  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)
  →  TBC  Server packs may override client side unless you can opt out of using it

RELEVANT INFORMATION (CREATORS)

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)

• 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
  →  TBC  If add on models can support "new" custom animations via 1.20.1-1.5+ features

 STEP ONE:  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
   

 STEP TWO:  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" 
        Note:  Supports color + format &l&9Pack Name V1.0 &0By &dCreator = Pack Name  V1.0 By Creator
   → pack_format Which format (MC version) is supported ✅ "pack_format": 15 = MC 1.20 - 1.20.1
        Note:  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

 STEP THREE:  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)

 STEP FOUR:  ADD YOUR CONTENT

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

 STEP ONE:  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

 STEP TWO:  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
   

 STEP THREE:  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) > assets / pack.mcmeta / pack
   → ❌Pack Name (Zip) > Pack Folder > 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.

 STEP ONE [A]:  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
   

 STEP ONE [B]:  MODIFY AN EXISTING ANIMATION

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

 STEP ONE [B]:  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
   

 STEP THREE:  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) > assets / pack.mcmeta / pack
   → ❌Pack Name (Zip) > Pack Folder > 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.