Skip to main content

Coats [WIP]

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

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

Important - Update Changes

Changes To Coat Data & Summoning
FeaturesFeature Changes
Summon

Minecraft /summon results inspawns 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 usesRemoved Variant: # NBT and insteadchanged usesto Behaviors[6].Coat



Data modifyvalues commandsfor coat 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 keykeys restrictions(ie swem:mod) - which may be useful to some servers.

 

Get the value (id + name) ofIdentify a Horse'scoat coat(ID)

 

/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 specifystate a supported model - this iswill tobe supportexpanded futurein options.future.

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

Frequently Asked Questions & Fundamentals

This section has drop-downs for FAQs and expanded information about Community Packs.Pack Coats.
If your question is not answered here, check out General Information.

[1]Features

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

Using A Community Pack

&

To install a Content PacksPack or PREMADE Community Pack, see General Information.

Read More

⮞ WHAT IS A COMMUNITY PACK?
Community Packs are folders that include all the files necessary to add NEW assets suchand asare custom coatsready to SWEM.play once installed.

⮞ WHAT IS A CONTENT PACK?
Content Packs is another name foralso a Community Pack.Pack, Contentbut Packsusually generally havewith less content,content. or even a single file. On pasting, itIt will merge into any Community PackPacks with the same name.name,

like
    an Creators can use a single (or multiple) consistent'expansion' 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?
      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

        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 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!
          [2] Modified Packs & Files

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

          ⮞ 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?
               Multiplayer                No. This may prevent you from seeing any custom coats, even if you have all the correct files.

               Singleplayer  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?
               Multiplayer  No. This may prevent you from seeing any custom coats, even if you have all the correct files.

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

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

                ⮞ CAN I EDIT COAT INFORMATION (JSON)?
                 Multiplayer  Yes, however:

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

                   Singleplayer  Yes, it is generally safe to modify coat info.

                  You should not remove or modify Artist credits +/- reference and inspiration comments.add-on.

                  [3] Multiplayer Use

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

                  UsingCreating A Community Pack Coat

                  This

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

                   


                   STEP ONE:  GENERATE THE NEW FOLDERS (FIRST TIME USING SWEM 1.5 Beta)

                    Install the mod update. Load the game to the menu screen. Exit the game.

                    [?] Features

                     

                    Troubleshooting / Common Issues

                    Back to top