Tags
Creators
Details
All versions
3.1.0
Release
CatSkinC 3.1.02 months ago 105
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
[3.1.0] - 2026-06-12 (26.1.2)
Added
- Added editable
catskinCloudIpsetting to specify custom server addresses. The server URL is automatically normalized and prepended with a protocol (http://orhttps://) if missing. - Added toggle settings to selectively enable or disable various toast notifications (
showConnectionToast,showUploadToast,showInfoToast, andshowErrorToast). - Added the original button click sound to the Slim Model toggle switch.
Changed
- Redesigned the client Settings screen: replaced the dropdown menu with search-filterable and collapsible accordion categories.
- Replaced the library slot thumbnail rendering with a 2D player face (matching the Tab Server List appearance) utilizing
PlayerFaceExtractorto integrate with Minecraft's deferred PiP rendering pipeline. - Shortened Toast messages in English and Thai language files to prevent text overflowing the toast boxes.
Fixed
- Decoupled connection checks from skin downloads: increased client concurrent connection limit to 50 and executed pings on a separate thread pool to ensure player skins load instantly without queueing.
- Fixed the "Clear Skin" action: attached the Mojang verification session token to clear selection requests to prevent HTTP 401 Unauthorized errors on session-enforced servers.
- Fixed skin texture registration issues by utilizing a 2-argument
ResourceTextureconstructor to prevent path modification.
Optional dependencies
Any compatible version
Any compatible version
Supplementary resources
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:HQ1Bl3VC:CqeUGlzJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HQ1Bl3VC:CqeUGlzJ"
}

