Community Packs

                                                                             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.