Skip to main content

Coats

Community Packs: Coats

This feature is available in 1.20.1-1.5+ and will NOT be backported to any outdated versions.

Community packs support adding NEW custom coats in-game without overriding the default options.


Important - Update Changes

FeaturesChanges
Summon

Minecraft /summon results in white horses only (cannot randomize).

 

 NEW  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

Coat Data

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)

 

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

MC Commands are exempt from role key restrictions - which may be useful to some servers.

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

/data get entity @e[type=swem:swem_horse,sort=nearest,limit=1] Behaviors[6].Coat 

 

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

Model

Coats and commands must specify model - this is to support future options.

LEGACY Default model and the only one currently supported.


Frequently Asked Questions & Fundamentals

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

[1] Community Pack Vs Content Pack

⮞ 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

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

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

  • The folders will merge into one
  • The files will not override others unless they have an identical name
    This is unlikely if Creators use the recommended format of coatname_artist
    Packs with outdated files could replace updated (fixed) files with the same name

 

This will work in the same way as a content pack - the files will merge into one pack. This is not a problem unless coats have an identical name, but could be annoying when it 

 


Using A Community Pack

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

 

FAQs

⮞ PRE-MADE VS INDIVIDUAL FILES
Creators should ideally check their packs and clearly state if it is ready to use. If not, look at the file contents and check it has the correct structure and contents. 
✅ pack_name > json ( > coats) / textures ( > coats > legacy)
❌ Individual files in a single folder
❌ Files or folder names that have spaces, symbols or capital letters

⮞ COMMUNITY PACK VS CONTENT PACK?
These are the same thing, but Content Pack is a term that might be used if it is an 'add-on' to or update an existing pack.

Example: A coat artist uploads all files under a pre-made pack called ArtistName_Kofi. If you download ONE coat, you can install it and play immediately. If you download another coat from the same artist, the files will merge under ArtistName_Kofi so you have TWO coats in one pack. 

If an artist gives every pack a unique name, you will get lots of individual packs instead or one consolidated pack!

If multiple artists use the same pack name (ie kofi_coats) files will merge under one pack unless you rename it first.

⮞ DUPLICATE FILES - REPLACE OR NOT?
There is no correct answer to this, because replacing files can be good or very bad! 

  • If a content pack is intended to update coat info or fix a coat error - replacing the original file(s) is expected!
    This could still cause issues for any horse currently using that coat, though same name + info is generally safe.
  • If a content pack has an updated (fixed) coat - merging it with an outdated pack may override the fixed version

⮞ CAN I RENAME COATS?
Coat names do not display in game, so there is not many reasons to do this, but it is possible. Any changes must be made to both png (coat texture) and json (coat info) as well as texture path. If the coat was in use, it will turn white unless an alternative texture using the original name is available.

Always read the Terms Of Use (TOU) from Creator's as altering coats might fall outside appropriate use for content.