Tags
Creators
Details
Licensed ARR
Published last month
Updated 7 hours ago
All versions
2.3.0
Release
Custom Capes 2.3.023 hours ago 10
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client-side
Changes
- Java and cracked players with the same name no longer get in each other's way: they are separate accounts, and a cracked player's capes show as "Name (offline)" with their own creator page, tagline and followers
- Capes can have see-through parts: transparent pixels are now see-through on the player instead of black
- Fixed "an admin removed this cape" showing for new capes that only looked a little like a removed one
- The Elytra switch in the cape menu now says it's a preview; wear an elytra in game to see your cape on it
- Emotes: press B for the emote wheel, pick from 8 built-in emotes or make your own frame by frame in the emote editor, and other players with the mod see you play them
- Outfits: save your cape and cosmetics together as an outfit in Cosmetics, Outfits..., and press O to switch to the next one
- Pets can be up to 600% big, and can circle you, swoop around you or walk beside you
- Cosmetics react to what you do: wings can spread wide while you fly, pets can sit down when you stand still, and tails can tuck in while you sneak
- New materials for cosmetic colours: Glass, Hologram and Pulse
- Trails can come out as a ring or a spiral around you, and their particles can face you
- New Footprints cosmetics: fading pixel footprints behind you as you walk, with their own tab and Footprints of the Week
- New built-in cosmetics: Holo Visor, Crystal Wings, Dragon, Ghost, Puppy, Star Ring, Magic Spiral, Paw Prints, Boot Prints and Heart Steps
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:neZ5ozJW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ocbOUiHH:neZ5ozJW"
}

