Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 5 hours ago
All versions
3.0.0
Release
Custom Capes 3.0.02 days ago 62
Compatibility
Minecraft: Java Edition
1.21.x
Platform
NeoForge
Supported environments
Client-side
Changes
- Capes are real cloth now: a wavey cape hangs on your back, flaps on its own and slides over your body, armour and worn cosmetics instead of going through them (turn it off with the Cloth switch in the Library)
- Capes fall over the saddle or seat when you sit or ride, and gather when you sneak
- Wind: capes catch the breeze under open sky (gustier in rain, wild in a thunderstorm), blasts from explosions, wind charges, rockets and riptides, and the air of players rushing past
- Materials: pick Cloth, Silk, Leather or Chainmail when you upload. Silk catches every breeze, while leather and chainmail hang heavy
- An optional trail fades out behind your cape on very fast moves (the Trail switch in the Library)
- Cape painter: layers (add, hide, merge), mirror left/right, top/bottom or all four corners, Round, Square, Spray and Dither brush tips (layers work on the inside lining too)
- Animations in the painter: onion skin shows the frames before and after, each frame can be held longer, and frames copy and paste between frames and layers
- The painter keeps a saved version every 20 seconds (History steps back through them), and Draft keeps a cape to finish later
- Picture import in Cape Creator can cut the colours down to a pixel-art palette, with optional dithering
- Creator stats on your creator page: views and likes per week, your top capes, and who wears them most
- Collections: group your capes into tabs on your creator page
- Badges on creator pages and cape info: First upload, 100 likes, Contest winner, Cape of the Week and 1-year creator
- 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:3KsZ9em9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ocbOUiHH:3KsZ9em9"
}

