Creators Capes

Add custom capes to your modpack without writing code or shipping a resource pack. Creator Capes lets pack authors define cape items in JSON, drop PNG textures into a config folder, and hand them out as rewards, shop items, or creative-tab entries. You can also assign permanent UUID cape overrides (local or remote textures) with no item required — useful for staff, patrons, or shared pack branding.

Features

• JSON-driven items: register any number of cape items in config/creatorcapes/capes.json
• Simple asset workflow: worn cape textures go in config/creatorcapes/textures/
• Optional inventory icons: per-cape icons, or a shared ? placeholder when none is set
• Creative tab: all cape items appear in the Creator Capes item group
• UUID cape overrides: permanent capes by player UUID via remote.toml (no item needed)
• Remote override config: point config.toml at a hosted TOML so every client loads the same UUID list
• Local or HTTPS textures: override textures from textures/ or image URLs (cached on download)
• Vanilla cape rendering: equipped / override capes replace the player’s worn cape sheet (including elytra when the sheet has wing UVs)
• Wavey Capes support: compatible when Wavey Capes is installed (optional; not required)
• Flexible equip slots: Trinkets / Curios when present, chestplate slot otherwise

Getting started

After the first launch, the mod creates:

config/creatorcapes/
  capes.json
  config.toml
  remote.toml
  textures/

Cape items

1. Open capes.json and add your cape entries.
2. Place worn cape PNGs in textures/ (standard 64×32 Minecraft cape layout).
3. Optionally add inventory icon PNGs and reference them with "icon".
4. Restart the game or server.
5. Find capes in the Creator Capes creative tab, or run /give @s creatorcapes:<id>.

Right-click a cape item to equip it.

UUID overrides (no item)

1. Edit remote.toml (or host a copy and set [remote].url in config.toml).
2. Add [[cape]] entries with a player uuid and texture (filename under textures/ or an https:// URL).
3. Restart clients (and the server if you keep configs in sync that way).

Configuration

Cape items — config/creatorcapes/capes.json

{
  "capes": [
    {
      "id": "my_cape",
      "name": "My Cape",
      "texture": "my_cape.png",
      "icon": "my_cape_icon.png",
      "rarity": "uncommon"
    }
  ]
}

Fields

UUID overrides — config/creatorcapes/config.toml

[remote]
# Fetch UUID cape overrides from this URL (empty = off)
url = ""

# Also merge overrides from this file under config/creatorcapes/
local_file = "remote.toml"

Merge order: remote URL entries first, then the local file (local wins on duplicate UUIDs).

UUID list — config/creatorcapes/remote.toml

# Permanent cape overrides (no item required).
# texture = HTTP(S) URL, or a filename under config/creatorcapes/textures/

[[cape]]
uuid = "00000000-0000-0000-0000-000000000000"
texture = "https://raw.githubusercontent.com/example/repo/main/cape.png"

[[cape]]
uuid = "11111111-1111-1111-1111-111111111111"
texture = "override_local.png"

An example remote.toml is created on first launch. Prefer GitHub raw or a CDN for hosted images — Imgur is blocked in some countries. If any override uses Imgur, clients see a one-time chat warning when joining a world.

Texture notes

• Worn capes should be 64×32. Larger images are cropped at runtime.
• Inventory icons are separate files (typically 16×16 or 32×32).
• If "icon" is set but the file is missing, the cape item still loads and uses the fallback icon.
• Downloaded override images are cached under config/creatorcapes/cache/.

Priority

When several cape sources apply to the same player:

1. Equipped Creator Capes item (Trinkets / chest)
2. UUID override from remote.toml / remote URL
3. Vanilla / Mojang default cape

So UUID overrides only replace the player’s default cape — they never block an equipped Creator Capes item.

Equipping

Without Trinkets or Curios, cape items equip to the vanilla chest slot like a chestplate.

For modpack creators

• Ship config/creatorcapes/ to both clients and servers (items + overrides).
• For shared UUID lists without shipping files, host a remote.toml and set [remote].url on every client.
• A restart is required after editing capes.json, config.toml, remote.toml, or changing textures.
• Client inventory icons from config are applied automatically; no extra resource pack.
• While an item cape is equipped, it fully replaces the player’s cape texture (and elytra when the sheet includes wing UVs).

Compatibility