Creators' Corner [WIP]

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

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

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

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