Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 2 hours ago
All versions
3.2.0
Release
Custom Capes 3.2.02 hours ago 12
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
- Cape sounds: capes now rustle and flap when they move fast. Sprinting gives a soft flap, sprint-jumping, flying and falling flap harder, and at high speed the cape flutters with a whoosh as it catches the air. All the sounds are new and made for the mod. Turn them off with the new Sounds switch in the cape menu, or set how loud they are with the game's Players volume
- Torn capes: a cape now tears when its wearer is low on health or their armour is nearly broken. The hem frays and holes appear, a little more as it gets worse, and it mends again as they heal or repair their armour. Everyone sees it on everyone's cape. Turn it off with the new Torn switch in the cape menu
- Nameplate cosmetics: a new Nameplates tab in the wardrobe for models that float above your name, like a crown, a star or a symbol. Make your own in the 3D editor and set its size, its height, whether it spins, faces whoever is looking or stays still, and whether it bobs. Four come with the mod: Floating Crown, Star, Heart and Gem. There is a Nameplate of the Week too
- Cape packs: collections on a creator page are now packs that anyone can like. Open a creator's collection to see its likes and press the heart to like it
- Save pack likes every cape in a pack at once, so the whole pack is in your liked capes, ready to wear
- Top packs: a new tab on the leaderboard with the most liked packs, a preview of their capes and who made them. Click a pack to open it
- The creator name under the cape preview moved up a little to make room for the new switches
- Translated into all 24 languages
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ocbOUiHH:X8FItYEE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ocbOUiHH:X8FItYEE"
}

