![](\"https:\/\/raw.githubusercontent.com\/litetex-oss\/mcm-cape-provider\/refs\/heads\/dev\/src\/main\/resources\/assets\/icon.png\"){kind=icon}
<\/p>\n<\/p>\n
Provides you with capes!<\/p>\n
You can choose from various providers or add your own.<\/p>\n
Improved\/Reworked version of the “Capes” mod:
\n* Improved and easier cape provider integration
\n* Allows ordering providers
\n* Support for custom providers
\n* More options to fine tune how capes are applied
\n* Written only in Java (no Kotlin needed)
\n* Various fixes and improvements<\/p>\n
### Creating a custom cape provider<\/p>\n
![](\"https:\/\/raw.githubusercontent.com\/litetex-oss\/mcm-cape-provider\/refs\/heads\/dev\/assets\/config-2.avif\")
<\/p>\n
The mod provides many different ways how a provider can be added.<\/p>\n
The following possibilities are sorted by simplicity:<\/p>\n
#### Simple Local Provider<\/p>\n
> Recommended for:
\n> * Users that just want a customizable cape
\n> * Modpacks (using `config\/cape-provider\/simple-custom`)<\/p>\n
The simplest way to display a cape is by going into the `config\/cape-provider` directory and creating a cape texture file named `cape.png`.<\/p>\n
Additionally there are the following optional files:
\n* `owners.txt` – Determines which player names or UUIDs will get the cape displayed. If this file is not present then all players will display with the cape.
\n* `name.txt` – To override the display name of the provider<\/p>\n
You can also add more providers by creating corresponding directories in `config\/cape-provider\/simple-custom`.
Example: `config\/cape-provider\/simple-custom\/my-super-cool-provider\/cape.png`<\/p>\n
#### Remote Provider in configuration<\/p>\n
> Recommended for:
\n> * Users that want to add a custom remote provider<\/p>\n
This demo showcases how to apply the capes inside “custom-cape-demo“.<\/p>\n
1. Open the config file located in “config\/cape-provider\/config.json“ “`jsonc 3. Restart the game and activate the provider<\/p>\n For more details have a look at RemoteCustomProvider and RemoteCustomProviderConfig<\/p>\n NOTE: Texture resolvers can be selected using the `textureResolverId` attribute (see below for details).<\/p>\n #### via Mods<\/p>\n > Recommended for: If you are a mod developer and want to e.g. display a cape for supporters or contributors of your mod, you can provide it using the mod’s resources and\/or metadata in “fabric.mod.json“. ##### Local\/Simple (Recommended)<\/p>\n This approach requires no network communication and is the recommended way. Here is an example: “fabric.mod.json“ The mod uses this strategy itself. See the `fabric.mod.json` or `cape` directory for details.<\/p>\n ##### Remote<\/p>\n Here’s an example implementation that shows how a remote cape provider can be added:<\/p>\n “fabric.mod.json“ “fabric.mod.json“ #### Programmatic<\/p>\n You can also create a programmatic cape provider.<\/p>\n ### Further notes<\/p>\n #### Maximum size<\/p>\n Images\/Textures should not exceed 10MB. Otherwise they might be ignored.<\/p>\n #### Texture resolvers \/ Animated textures<\/p>\n The following resolvers are currently built-in:<\/p>\n | Resolver-ID | Animated | Format | Example | Notes | Please note that animated textures can be frozen or completely disabled in the settings.<\/p>\n","protected":false},"excerpt":{"rendered":" Provides you with capes!<\/p>\n You can choose from various providers or add your own<\/p>\n","protected":false},"featured_media":36885,"template":"","meta":{"_minecraft_slug":"cape-provider","_minecraft_project_id":"orXAsira","_minecraft_author":"litetex","_minecraft_license":"LGPL-2.1-or-later","_minecraft_downloads":955743,"_minecraft_follows":70,"_minecraft_client_side":"required","_minecraft_server_side":"unsupported","_minecraft_storage_type":"zip","_minecraft_archive_name":"cape-provider.zip","_minecraft_size_bytes":6099601,"_minecraft_version_count":62,"_minecraft_updated_at":"2026-05-16T13:00:43.832745Z","_minecraft_date_created":"2025-03-11T11:41:42.855770Z","_minecraft_date_modified":"2026-05-07T19:26:54.574454Z","_minecraft_project_url":"https:\/\/modrinth.com\/mod\/cape-provider","_minecraft_icon_attachment_id":36885,"_minecraft_imported_at":"2026-06-01T18:30:31+00:00","_minecraft_import_hash":"4461c85235ad21d1020b98bbd5196045","_minecraft_versions":"","_minecraft_links":"","_minecraft_gallery":"","_minecraft_api_metadata":""},"mod_category":[156,88,97,867,92],"mod_loader":[99],"minecraft_version":[62,37,40,41,38,78,79,784,80,81,82,83,167,163,842],"class_list":["post-36884","mod","type-mod","status-publish","has-post-thumbnail","hentry","mod_category-decoration","mod_category-equipment","mod_category-fabric","mod_category-social","mod_category-utility","mod_loader-fabric","minecraft_version-1-21","minecraft_version-1-21-1","minecraft_version-1-21-10","minecraft_version-1-21-11","minecraft_version-1-21-4","minecraft_version-1-21-5","minecraft_version-1-21-6","minecraft_version-1-21-6-rc1","minecraft_version-1-21-7","minecraft_version-1-21-8","minecraft_version-1-21-9","minecraft_version-26-1","minecraft_version-26-1-1","minecraft_version-26-1-2","minecraft_version-26-2-snapshot-7"],"yoast_head":"\n
\n2. In the “remoteCustomProviders“ section add the following entry:
\n “`jsonc
\n {
\n “id”: “cp1”,
\n “name”: “CustomProvider1”,
\n \/\/ You can replace uuid with $id, $name or $idNoHyphen to customize the cape per Player
\n “uriTemplate”: “https:\/\/raw.githubusercontent.com\/litetex-oss\/mcm-cape-provider\/refs\/heads\/dev\/custom-cape-demo\/uuid.png”
\n }
\n “`<\/p>\n\nExample for SkinMC<\/summary>\n
\n {
\n “id”: “skinmc”,
\n “name”: “SkinMC”,
\n “uriTemplate”: “https:\/\/skinmc.net\/api\/v1\/skinmcCape\/$id”
\n }
\n “`<\/p>\n<\/details>\n
\n> * Mods<\/p>\n
\nThe overall behavior is similar to how “modmenu“ handles this.<\/p>\n
\nIt works by reading metadata and resources from the `cape` directory.<\/p>\n
\n1. Add the following mod metadata:
\n “fabric.mod.json“
\n “`json5
\n {
\n …
\n “custom”: {
\n “cape”: “Contributors”
\n }
\n }
\n “`
\n2. Create a `cape` directory inside `resources`
\n3. Add the cape texture in `cape\/cape.png`
\n4. Add the players that should be given the cape in `cape\/owners.txt` with their UUIDs or names<\/p>\n\nNote: There is also a more detailed variant<\/summary>\n
\n“`json5
\n{
\n “custom”: {
\n “cape”: {
\n “name-extra”: “Contributors”,
\n “owners”: {
\n \/\/ You can also used UUIDs
\n “names”: [
\n “Notch”
\n ]
\n }
\n }
\n }
\n}
\n“`<\/p>\n<\/details>\n
\n“`json5
\n{
\n …
\n “custom”: {
\n “cape”: “https:\/\/raw.githubusercontent.com\/litetex-oss\/mcm-cape-provider\/refs\/heads\/dev\/custom-cape-demo\/uuid.png”
\n }
\n}
\n“`<\/p>\n\nHere’s a more detailed variant<\/summary>\n
\n“`json5
\n{
\n “custom”: {
\n “cape”: {
\n \/\/ Gives everyone a christmas cape
\n \/\/ You can also use variables here, like $uuid. See above for more details
\n \/\/ You may have to escape the $ with or you can alternatively use \u00a7 instead of $
\n \/\/ Alternative: “uriTemplate”
\n “url”: “https:\/\/example.org\/textures\/\u00a7uuid.png”,
\n “changeCapeUrl”: “https:\/\/…”,
\n “rateLimitedReqPerSec”: 20 \/\/ Default is 20
\n }
\n }
\n}
\n“`<\/p>\n<\/details>\n
\n| — | — | — | — | — |
\n| `default` \/ null | \u274c | PNG | uuid.png | |
\n| `sprite` | \u2714 | Stacked PNG | animated.png | |
\n| `gif` | \u2714 | GIF | animated.gif | _Usage not recommended_
GIFs require more resources when compared to more modern formats like PNG. |<\/p>\n