Tags
Creators
Details
1.0.4
Compatibility
Changes
Changelog (v1.1.5a)
Maintenance release for every supported Fabric version and the Paper plugin. It fixes crashes and visual bugs caused by the bundled default model, stale first-person hand textures, and — on 26.2 — custom models resetting after a reconnect.
Fixed
- Crash when switching to the default model. The bundled
defaultmodel is now reserved: it is stored separately, never uploaded as a regular model, never registered as a lazy model, and never replaced by a server catalog entry. This removes theNullPointerExceptionin the model screen, player renderer and hand renderers. - Crash after removing model files from the server and rejoining. A lazy model that fails to parse now keeps using the current fallback instead of freezing an empty or broken assembly.
- Stale first-person hand textures after a model switch. The local player's model capability is now ticked before first-person hands are rendered, and
PlayerGeoEntityrefreshes when the render shape or model ID changes. Hands now use the texture of the newly selected model. - Wrong default model and hands in singleplayer. Selecting a non-default model no longer briefly renders the default model or its hand textures first.
- Custom models lost after reconnecting (26.2). On disconnect, all assemblies except the bundled default are dropped and released, so the next catalog rebuild parses models fresh instead of reusing stale lazy wrappers.
- Paper: the
defaultmodel ID is now reserved. PaperBPM rejects uploads with the IDdefault(Model ID is reserved.) and ignores adefaultentry already present in the models folder, so unpatched clients and old uploads cannot break the server catalog.
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:25554vKP:jl0q3qpU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:25554vKP:jl0q3qpU"
}

