All versions
1.3.8-rc.1
Beta
SkinCraft 1.3.8-rc.1last week 407
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
SkinCraft 1.3.8-rc.1
Minecraft: 26.1, 26.1.1, 26.1.2, 26.2, 26.3 · Loader: Fabric · Java: 25+
Highlights
- Minecraft 26.3 support: Use one SkinCraft JAR across all five Minecraft versions listed above.
- Hex color input: Fix number-key and numpad handling and update text-input focus behavior on 26.3.
- Preview rotation: Fix right-click drag rotation in the local and community skin galleries on 26.3.
- Compatibility fixes: Correct the cape entity-preview and overlay-message fallback paths used by older Minecraft versions.
Compatibility
- This is a release candidate, published for testing before the final 1.3.8 release.
- Requires Fabric API matching your Minecraft version and a compatible Fabric Loader. Validation uses Fabric Loader 0.20.1.
- Automated startup and editor smoke checks cover all five listed Minecraft versions. Manual testing on 26.3 was reported successful.
- Multiplayer, detailed in-world appearance across versions, and alternative graphics backends still need broader testing.
- Minecraft 26.4 snapshots and Minecraft 1.21.x are not supported by this release.
Install
- Add
skincraft-1.3.8-rc.1.jarand Fabric API matching your Minecraft version to the clientmodsfolder. Use the same SkinCraft JAR for every version listed above. Remove the previous SkinCraft JAR first. - New to Fabric? fabricmc.net/use — choose the same Minecraft version as your installation.
Notes for developers and modpacks
- SkinCraft is client-side; a server installation is not required. Java 25 or newer is required.
- Please include your Minecraft version, Fabric Loader/API versions, and relevant logs when reporting an issue.
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:DZjAFKLW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k3mJyqXq:DZjAFKLW"
}

