Community Packs

Can community packs support tack, breed models, animations?
Currently, no. It is planned to add tack and animation support at a later date - and expand on the models as part of development. Texture packs that add new models to override the default model should still work.

Can community packs add foal variants?
Currently, no. The current system only supports one foal per color tag (white, gray, black, brown etc) - supporting additional foals would require a more realistic genetics system. Of course if you want to overhaul foals anyway, you can continue to texture pack override the default coats. 

Can community packs be used on servers?
Yes, provided all clients must the necessary resources (community pack). Please be mindful of creators and abide by their terms of using, including appropriate distribution of content files.

Can community packs be used server-side only (not needed by client)?
Probably not easily, or in such a way that does not violate terms of use for custom content creators.

Can server clients create a texture pack override for CUSTOM coats?
Clients can replace the PNG to override a specific coat - the replacement file must have the same name. The override will only be visible to them.

Can coats still be changed via NBT command?
Yes, the MC command is /data modify entity @e[type=swem:swem_horse,limit=1,sort=nearest] Behaviors[6].Coat set value <id:coat>. Alternatively, use the simple command: /swem set coat <id:coat> 

Can I use a different content pack for each save?
Community Packs apply to all saves for that instance or profile. You could manually switch out to packs to see different options, but that would probably be more effort than it is worth.

Can the natural spawning datapack (community creation) be used with these new coats?
Yes, this datapack was specifically tested and code/commands fixed to continue to support this.

Can custom coats appear from cantazarite conversion?
Yes, if conversion is allowed in configs.

Can you or what happens if...
Add a new coat 
   → You can safely add new community packs AND new coats at any time provided you quit and reload!
   → If you forget to add the json, the coat will not be registered (not an option to select coat, no cycling etc)
   → If you forget to add the png, the coat will be registered but will appear black.
Alter coat information Requires a game quit and reload!
   → You can safely modify credits, inspiration, obtaining, color tags at any time provided you quit and reload!
   → If you change file name or model path this will remove the coat from any using it, and create a new coat.
Remove a coat
   → You can safely remove community packs or coats at any time provided you quit and reload! 
   → If you remove the json + png or just the json, the coat will not register and will appear white coat on next load.
   → If you only remove the PNG, the horse(s) using it will appear black.
Join a server with packs the server does not have
   → TBC

Can I fix my horse after accidentally removing a pack or coat?
Yes - if a coat is removed, the still horse retains their information (but not texture) for that coat unless modified! You can easily add back the correct community pack and/or files with the same name and model information to see the correct texture again.

Can you alter the color tag data of default (SWEM) coats?
No, these are hard coded. You can continue to override the textures if you want to alter their appearance, but unless you do so with similar coats or colors the tags will not be logical when breeding. 

Can I see the details of a coat (artist, name, tags etc) I get in game?
To be confirmed if this is officially supported (non-OP command or GUI display) but coat data can be shown using the 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.