Cape Command
Cape Command lets players choose a cape from a list of capes the server makes available, and reset it to the default skin.
What it does
Once the mod is installed on a server, players can run the cape command in both solo worlds and multiplayer servers. Each player picks from the capes that are listed as available, and a reset option returns the skin to its default. Cape Command includes support for custom capes and a permissions API, so server owners decide which capes a player may use. A custom cape feature is listed as planned.
Clients that have Cape Command installed can see their own cape, but only a server running the mod lets them see the capes of other players. Players on a Bedrock-based setup connect through Geyser, and a server with Geyser installed lets them see everyone's capes and use capes as well. The mod requires Fabric API on Fabric.
Cape Command is published for Fabric and NeoForge across 20 release versions, 1.20.4 – 26.3. Snapshot builds are published. NeoForge ports are available for Minecraft 26.1 onwards. The server has to run the mod while a player's client may skip it, and the code is released under the GNU Lesser General Public License v3.0 only, so the source is open.
Key features
Cape selection command
A command lets players pick a cape from the available list in single-player worlds and on servers.
Cape reset
A reset command returns a player's skin to the default look.
Permissions API
Server owners can control which players may use which capes through the permissions API.
Custom capes
Custom capes can be added, and a further custom cape feature is listed as planned.
Geyser support
A server with Geyser installed lets Bedrock players see capes and use them.
Compatibility
Latest build for each game version and loader.
26.x5 of 5 versions with builds
1.21.x12 of 12 versions with builds
1.20.x3 of 3 versions with builds
This mod also publishes snapshot builds. Snapshots are not shown in the matrix.
Use cases
Who it’s for: Server owners who want to offer cosmetic capes, and players who want to choose one on a server that runs the mod.
How it compares
Pride Cape Flags is client-side friendly and open source, published for Fabric and NeoForge across 1.20.1 – 26.3, and its client environment means the server does not need it. Better Capes is client-side only, with all rights reserved and Fabric files for 1.20 – 26.3. Cape Command differs from both because the server must run it, and its license is the GNU Lesser General Public License v3.0 only.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| Cape Command | Fabric and NeoForge | 1.20.4 – 26.3 | Server required, client optional | 2026-10-01 |
| Pride Cape Flags | Fabric and NeoForge | 1.20.1 – 26.3 | Client required, server optional | 2026-10-13 |
| Better Capes | Fabric | 1.20 – 26.3 | Client-side only | 2026-09-21 |
Questions
Does Cape Command require Fabric API?
Does the server need Cape Command?
Which versions are supported?
In the catalog
Cape Command is one of 5,392 Social mods on ModsFinder, and one of 4,084 Social mods for Fabric. 8,071 mods support Minecraft 26.3.
More from eclipseisoffline
Similar mods
What the author says
This mod adds a /cape command to Minecraft, which allows you to use any cape you want. Use /cape reset to reset your cape to its default on your skin. All the capes listed here are available, with custom capes being a planned feature.
Official listing
- Modrinth page
- modrinth.com/mod/cape-command
- Owner
- eclipseisoffline
- Published
- 2024-02-09
- Updated on Modrinth
- 2026-10-01
- Facts verified
- 2026-10-15