All versions
1.3.0
Release
SkinCraft 1.3.06 months ago 65
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
SkinCraft 1.3.0
Minecraft: 26.1 · Loader: Fabric · Java: 25+
Highlights
- New Community Skins view in the skin selector browse, preview, and either Save to your local skins folder or Apply directly to your player.
- Share to Community on the local screen now opens a dialog to add a Name and Category, with optional Tags and Description, so uploads are easy to find.
- Category dropdown and name search on the community screen; results load in pages sized to your window.
- Community list repaginates automatically when you resize the window.
- Local screen buttons relabeled for clarity: Open Skins → Import, Upload → Share.
- Header toggle for Local ↔ Community sits in the same spot on both screens.
- Fix: opening the category filter with a community skin previewed no longer crashes the game.
- Fix: on multiplayer servers, your custom skin no longer leaks onto other players — only you see it on yourself.
Compatibility
- Requires Fabric API for Minecraft 26.1 (e.g.
0.144.3+26.1or compatible).
Install
- Use Minecraft 26.1 with Fabric. Add Fabric API (matching this MC version) and
skincraft-1.3.0.jarto yourmodsfolder. - New to Fabric? fabricmc.net/use — choose the same Minecraft version as this release.
Online disclosure
- Community Skins is an online feature and connects to the SkinCraft community service.
- When you share a skin, the name, category, and any tags or description you enter are uploaded together with your Minecraft name and UUID so other players can see who uploaded it.
- Local mode keeps working even if the community service is unavailable.
Notes for developers and modpacks
- —
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:k3mJyqXq:s816DpGm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k3mJyqXq:s816DpGm"
}

