ManufacturingSaw/horizon-capes-skins-minecraft
GamesGives Horizon players free wearable capes, wings, hats, shoulder pets and emotes that other Tailor users see on any server.
Tailor: free cosmetics for Horizon
Tailor is a Windows desktop app plus a native Horizon mod that adds cosmetic items to Horizon, the Rust rewrite of Minecraft: Java Edition 26.3. You pick a cape, wing, hat or shoulder pet in the app, press Wear it, and other players who also run Tailor see it in-game on any 26.3 server. Emotes work similarly: hold B in the game to open a wheel of eight emotes, and nearby Tailor players see your animation.
The wardrobe has 24 capes, 8 wings, 12 hats and 6 shoulder pets, each with a preview. You can also build a squad cape from 12 emblems and two colours and share a code like WOLF-7Q2K, or turn a PNG, JPG or GIF into a custom cape with a draggable crop frame.
It is aimed at Horizon players who want cosmetics without paying for a client or a donation tier. Nothing is sent to the Minecraft server, so cosmetics are drawn locally and give no gameplay advantage; players without Tailor see your normal skin.
Get started
Requirements: Windows 10 or 11, and Horizon 26.3 installed on the same PC. Tailor locates Horizon itself.
- Download
Tailor-1.2.1-portable-x64.exe. It is a single file with no installer and needs no admin rights. - Run it. The build is not code-signed, so SmartScreen may warn you on first launch; choose More info, then Run anyway.
- In Tailor, press Add to Horizon. The app copies its native mod (
.hnmod) intohorizon-native-mods/in your game folder and addsconfig/tailor/credentials. - Open Horizon once. It asks you to trust the mod, then builds the game with it; Tailor finds you automatically once the mod writes its sign-in data.
- Pick a cape in the wardrobe and press Wear it.
The first build can download Rust and take 20 to 30 minutes according to the README; later builds are faster.
Building from source takes Rust 1.85 or newer plus the Tauri prerequisites for your system:
git clone https://github.com/ManufacturingSaw/horizon-capes-skins-minecraft.git
cd tailor
cargo test --workspace
cargo tauri build
The catalogue lives in catalog/cosmetics.toml.
Constraints and behaviour
- Platform: Windows 10 and 11 only for the portable build. Source builds are possible elsewhere with the Tauri toolchain, but no other packaged build is documented.
- Native mod trust: Horizon shows a one-time trust prompt because native mods are not sandboxed. Skipping it means the mod is not compiled in.
- Who sees cosmetics: only other players running Tailor, on any 26.3 server. The Minecraft server receives no cosmetic data, and server rules remain the server's call.
- Login: the mod proves identity through the game's existing session token and a nonce/hash exchange; your password is never sent to Tailor, and Tailor stores only your player ID and name. The app uses Mojang's public profile API to fetch your skin without a login.
- Custom capes: up to 512 KB, GIFs up to 32 frames. Anyone can hide a custom cape locally or report it; three reports from different players hide it for everyone pending volunteer review. Settings let you choose whose custom capes you see: everyone, friends and squad, or nobody.
- Offline server: if Tailor's server is down, capes still render from cache but emotes do not reach other players.
- No account, no shop: no paid tier, ads, telemetry or purchases.
- Licence: MIT.
HotRepo's take
The only HotRepo snapshot for this project is from 2026-11-01, on the JavaScript new-project list, recording 106 stars gained since the previous day's window and 5 forks. That is a single first-day reading with no daily all-language rank on record, so it says nothing yet about whether the project holds momentum. What the data does support is a clear launch spike for a very young repository created on 2026-10-31. The technical facts around it are more useful for judging fit: Tailor is a Windows-only native-mod companion for a specific Horizon version, and its social value depends on other players also installing it. Anyone evaluating it should weigh that explicit dependency rather than the one-day star count.
Written by AI from the project's README, updated . The project's own docs are the source of truth.