Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated yesterday
All versions
3.5.0
Release
Custom Capes 3.5.02 days ago 28
Compatibility
Minecraft: Java Edition
1.21.x
Platform
NeoForge
Supported environments
Client-side
Changes
- Visuals: a new "Visuals..." button in the Wardrobe, next to Boat Skins, with five tabs: Outline, Totem, Kill, Fire and Sky
- Block outline: choose the colour, opacity and thickness of the box around the block you're looking at, and fill it with a see-through colour
- Totem pop: paint or upload your own picture for the Totem of Undying pop, with a Classic, Spin or Burst animation
- Kill effects: lightning, hearts, flames, souls, an explosion, a totem burst or music notes where you make a kill, with or without sound. Everyone with the mod sees it. The lightning is only for show: it can't hurt anyone or set anything on fire
- Custom fire: soul fire, any colour you like, or your own picture (a strip of frames makes it move). It changes both the fire on screen when you burn and the fire on burning players and mobs
- Custom sky: five built-in skies (Sunset, Starry night, Aurora, Deep space, Pastel) or your own picture, as a panorama or a cube cross. Only you see your sky
- Fixed clicking a cape on page 2 of My Capes picking the cape in the same spot on page 1
- The player in the cape menu's preview no longer twitches when you swing or use an item
- The cape creator and painter run much more smoothly
- Fixed memory use slowly growing in long sessions: cape pictures you haven't seen for a while are freed
- Less background network use while you're not in a world
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:uDcIbQaf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ocbOUiHH:uDcIbQaf"
}

