Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 8 hours ago
All versions
3.3.0
Release
Custom Capes 3.3.0yesterday 6
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Forge
Supported environments
Client-side
Changes
- New GUI
- The cape library shows its capes a page at a time, and the cape switches are sorted under three tabs: Effects, Motion and Extras
- Collection collabs: invite other players by name to add their own capes to one of your collections. They say yes or no on their creator page, add and take out their own capes, and can leave whenever they like. You can take out anyone and any cape. Up to 10 players per collection
- Crosshair: a new Crosshair... button in the wardrobe. Pick a cross, dot, circle, square or arrow and set its size, gap, thickness, opacity and colour, with a centre dot and a black or white outline, or paint your own pixel by pixel. Only you see it
- Boat skins: a new Boat Skins... button in the wardrobe. Paint a skin for your boat, starting from any wood's own look, or import a picture or a resource pack. Everyone with the mod sees it on the boat you drive. Rafts keep their own look. There is a Boat of the Week too
- Hitboxes: a new Hitboxes... button in the wardrobe. Set the colour and opacity of hitboxes for players, mobs, items and everything else, hide any of them, make the lines thicker, and turn the eye line and look line on or off with colours of their own. Show them in game with F3+B as usual
- Imported models look exactly as they were made: Blockbench models (mesh parts too) and resource-pack models keep their real shape and texture instead of being turned into voxels, on weapon and tool skins, hats, wings, scarves, tails, pets and nameplates. Editing one in the editor turns it into voxels
- The weapon and tool skin painter's mirror has four settings: off, left-right, up-down and corner to corner
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:uNQA5l3J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ocbOUiHH:uNQA5l3J"
}

