Links
Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 3 months ago
All versions
1.0.5-1.20.1
Release
MmdSkin 1.0.5-1.20.14 months ago 50.4K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
MMD Skin 1.0.5 Changelog
✨ New
- Mob Model Replacement You can now configure which model each animal uses directly in the mod's config screen. ⚠️ Caution: Watch your memory usage!
- Default Expression System Added a set of hardcoded default expressions to make models more lively.
- Handheld Item Size Adjustment Set the size of held items per model, available in each model's individual configuration.
- Stage Mode Volume Control Stage mode now includes a volume adjustment option.
- Preliminary Vivecraft Compatibility Very early support — you can view models and move arms, but not much else. Good for a quick test.
⚡ Improvements
- Cel-Shading Effect The toon shading looks more natural and polished, giving characters a feel closer to anime-style games.
- Major Performance Boost Average FPS increased by over 25%. Even with dozens of models on screen, it stays close to 100+ FPS.
- GUI System Fully semi-transparent interface with a new selection animation for the radial menu.
🐛 Fixes
- Leg IK Locking Fixed an issue where a model's legs would freeze after certain animations.
🔧 Porting Plans
- Versions like 1.21.11 are being ported and should be uploaded to Modrinth in the next couple of days.
- I might also port to 26.1 when I get around to it, but I'm waiting for the stable Vulkan API in 26.2, so it's pending.
- I'll try to cover as many intermediate 1.21 minor versions as possible. Less popular versions likely won't receive long-term support — maybe just bug fixes — since I'm working solo with limited time. Thanks for understanding!
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:6eYjvXFw:ubeNzJz9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6eYjvXFw:ubeNzJz9"
}

