Tags
Creators
Details
1.1.0
Compatibility
Changes
OfflineSkins Reloaded 1.1.0
🎨 Display custom skins and capes without relying on Mojang servers.
OfflineSkins Reloaded allows you to use local player skins and capes on offline-mode servers, private networks, and custom setups.
📁 Simply place your textures into:
cachedimages/skins/ - Player skins
cachedimages/capes/ - Player capes
The file name must match the player's nickname.
✨ What's new in 1.1.0: • Added support for Minecraft 1.21.9–1.21.11 • Added 17 language localizations • Improved Mod Menu integration • Updated translations and localization support
✨ Features: • Custom skins from local files • Custom capes support • Works on offline-mode servers • Lightweight and client-side only • No external skin services required
🌍 Supported languages: English, Russian, Spanish, German, French, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Simplified Chinese, Ukrainian, Azerbaijani, Turkish, Czech, Dutch, and Swedish. Added support for Minecraft 1.21.6–1.21.11.
Warning!
Note: due to Minecraft compatibility limitations, this release is split into two builds:
- 1.21.6–1.21.8
- 1.21.9–1.21.11
Currently this build supports Minecraft 1.21.9–1.21.11.
Please download the version that matches your Minecraft version by checking the mod file name.
If you are using Minecraft 1.21.6–1.21.8, please download the corresponding build by checking the mod file name.
link to the 1.21.6-1.21.8 build: https://modrinth.com/mod/offlineskins-reloaded/version/xPLyeL0k
Original author: zlainsama
Fabric port & maintenance: VoreZ
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| offlineskins-reloaded-1.21.9-1.21.11-fabric-1.1.0.jar | Unknown | 143.65 KiB |
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:jwBsp59y:gR36C0HR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jwBsp59y:gR36C0HR"
}

