Screenshot 1 of 1. Cape Options menu lists Cape Provider under Contributors, with a flame-patterned cape on a player model.
What Cape Provider works with.
| Platform | Java Edition |
|---|---|
| Loaders | Fabric |
| Minecraft versions | 1.21, 1.21.11, 26.1.2, 26.2, 26.3 |
| Environment | Client |
Cape Provider is a client-side Fabric mod that gives you capes from a list of providers, or from sources you add yourself. It is an improved, reworked version of the Capes mod, written only in Java with no Kotlin needed. It has no server side and is not for servers.
Loaders and versions
- Fabric: Minecraft 1.21 to 26.3. The newest build requires Fabric API, optionally Mod Menu; some builds for 1.21.5 to 1.21.7 need no dependencies; builds for 1.21.4 to 1.21.5 need no dependencies; builds for 1.21 to 1.21.4 need no dependencies.
What the cape provider mod changes
- Pick from several built-in cape providers and put them in your own order.
- Add custom providers from local files, remote URLs or other mods.
- Fine-tune how capes are applied, with fixes over the original Capes mod.
- Animated capes through a stacked PNG sprite or a GIF, which can be frozen or disabled in settings.
Adding your own cape
The simplest route is a file named cape.png in the config/cape-provider folder. An optional owners.txt limits it to listed player names or UUIDs, and name.txt renames the provider. More providers go in subfolders of config/cape-provider/simple-custom.
For a remote source, add an entry with an id, a name and a uriTemplate to the remoteCustomProviders section of config/cape-provider/config.json. The template accepts $id, $name and $idNoHyphen to vary the cape per player. Restart and activate the provider afterwards. Mod authors can ship supporter capes through a custom cape entry in fabric.mod.json, in the way Mod Menu reads mod metadata.
Installing it
- 1.Set up Fabric for your Minecraft release, following the Fabric install guide.
- 2.Put the mod file and Fabric API in the mods folder. Mod Menu is optional.
- 3.Launch with the Fabric profile.
Questions about Cape Provider.
3 questions
Does Cape Provider work on multiplayer servers?
It is client-side only and server use is unsupported, so nothing needs installing on a server. Cape Provider runs in your own game, where it loads capes from the providers you activate, from local files, remote URLs or capes that other mods ship in their metadata.
How is Cape Provider different from the original Capes mod?
It is an improved rework of the Capes mod. It adds easier provider integration, provider ordering, custom providers and more options for how capes are applied. It is written only in Java, so it needs no Kotlin, and it includes various fixes.
Can I use my own cape image with Cape Provider?
Yes. Put a texture named cape.png in the config/cape-provider folder. An optional owners.txt limits the cape to listed player names or UUIDs, and name.txt changes the provider's display name. Keep textures under 10 MB, since larger files might be ignored.
