Tags
Creators
Details
1.2.0
Compatibility
Changes
Fox Model Loader → Sparkle's Morpher
Fox Model Loader has officially evolved into Sparkle's Morpher.
Starting with this release, active development on this Modrinth project continues under the Sparkle's Morpher name.
Sparkle's Morpher is the successor to Fox Model Loader and continues the same core custom-model functionality while significantly expanding the project's capabilities.
For Fox Model Loader users
Please remove the old Fox Model Loader JAR before installing Sparkle's Morpher.
Fox Model Loader used:
yes_steve_model
Sparkle's Morpher now uses:
sparkle_morpher
Do not intentionally install both at the same time.
Sparkle's Morpher includes backward-compatibility code for migrating the legacy config/yes_steve_model configuration directory to config/sparkle_morpher when appropriate.
Existing YSM models remain supported.
What's new with Sparkle's Morpher?
Sparkle's Morpher expands beyond the original Fox Model Loader scope with features including:
- YSM model support
- Direct Blockbench
.bbmodelloading - Figura avatar archive importing
- Expanded animation controllers
- Molang expressions
- Model sound effects
- Animation carousel
- Multiplayer synchronization
- Server-side model management
- Model groups and favorites
- Additional model targets and compatibility work
Previous Fox Model Loader releases will remain available on this project page as legacy versions.
All future development will continue under the Sparkle's Morpher name.
Source code:
https://github.com/sdf123098/Sparkle-Morpher
Legacy Fox Model Loader source:
https://github.com/sdf123098/Fox-Model-Loader
Thank you for supporting Fox Model Loader.
Welcome to Sparkle's Morpher.
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:jQtfvgHC:ELdmIwA5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jQtfvgHC:ELdmIwA5"
}

