Uebliche

Appearance

CapesClient cape override mod

Merge Mojang capes with a moderated Uebliche catalog and render the selected public cape in-game.

GitHub
Changelog
Feature checklist
Capes preview

Shared cape domain

Canonical cape types live in the Capes repo `core` module.

Multi-loader build

Thin Fabric and NeoForge loaders share one client runtime.

Mixed-source browser flow

The launcher can merge Mojang account capes with the public Uebliche cape catalog.

Public cape overrides

Modded clients replace the visible cape only when a public Uebliche selection exists.

Overview ​

Capes is a client-side mod plus shared launcher and API surface for curated cape selection. Mojang capes remain vanilla-native and launcher-local, while public Uebliche capes are uploaded, moderated, selected per account, and resolved by the Public API.

Runtime behavior ​

  • If a player has an active public uebliche cape selection, the client loads that texture and overrides only the cape layer.
  • If no public uebliche cape is active, the client leaves Mojang or vanilla cape rendering untouched.
  • The launcher skin editor may preview capes and set the active account selection, but it does not persist cape ids inside saved skin projects.

Build ​

bash
# Fabric
export JAVA_HOME=/Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home
./gradlew :loader-fabric:build -PonlyLoader=fabric

# NeoForge
export JAVA_HOME=/Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home
./gradlew :loader-neoforge:build -PonlyLoader=neoforge

Feature checklist ​

Track feature progress in the checklist.

Feature highlights ​

  • Shared cape domain
  • Multi-loader build
  • Mixed-source browser flow
  • Public cape overrides
  • Add feature checklist page to track project progress.
  • Add Capes documentation overview. (#docs)