Client Custom Capes

Custom Capes Mod

Transform your Minecraft experience with fully customizable player capes!

This client-side mod revolutionizes how capes work in Minecraft, giving you complete control over which players display capes and what designs they use. Unlike traditional cape systems, our solution offers granular customization without requiring server modifications or special permissions.

🧩 Core Functionality

1. Personalized Cape Management

• Set custom cape URLs (supports PNG images)
• Define default capes for all players
• Store local cape files in config/custom-cape/capes/ folder

1. Advanced Player Filtering

• Whitelist Mode: Only show capes to specific players
• Blacklist Mode: Hide capes from selected players
• Case-insensitive nickname recognition with automatic UUID caching

⚙️ Technical Implementation

• Client-Side Only: Zero server requirements
• Optimized Performance:
• Asynchronous texture loading (dedicated thread pool)
• Smart caching system (prevents reloading)
• Automatic cache clearing on config changes
• Dynamic Configuration:
• In-game GUI via Cloth Config API
• Live preview of settings changes
• Auto-saves to config/custom-cape/capes.json

🖥️ User Experience

• Intuitive Controls:
• Access settings via pause menu (top-right cape icon)
• No commands or complex setup required
• Visual Feedback:
• Instant cape updates without reloading
• Clear error logging for invalid URLs/files
• Accessibility:
• Fully translatable text components
• Tooltip explanations for all options

Future Updates

This mod will continue to be updated with new features and improvements.

Planned enhancements include:

• Per-player cape customization (assign unique capes to individual players)
• Granular control over specific players’ appearances
• Regular updates for new Minecraft versions
• Ongoing optimization and bug fixes

Development is active – stay tuned for new releases!

🎬 Preview

Final Note: This mod respects Mojang’s cape guidelines and only overrides visual elements client-side. Original cape visibility rules remain intact for unmodified clients. All functionality is opt-in and requires explicit user configuration.

P.s: Idea