Tags
Creators
Details
All versions
3.1.0
Release
DBetterModel 3.1.0 | BM v1.10.1last year 44
Compatibility
Minecraft: Java Edition
1.21–1.21.8
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
for BetterModel v1.10.1, MC 1.21.4, Denizen 1.3.1 (7144)
Added:
- Bone Visibility Mechanism (
visible): Implemented a new mechanism forBMBoneTagto control bone visibility. It supports both global toggling and per-player visibility changes via packet manipulation. [EXPERIMENTALLY, THERE ARE PROBLEMS] - Bone Item Mechanism (
item): Introduced a mechanism forBMBoneTagthat allows setting a customItemTagas the bone's model, with optional support for a localLocationTagoffset. [This mechanism previously existed, but has been added again] - Configurable Skin Application Delay: Introduced a new option in
config.yml(options.skin-apply-delay-ticks) to allow server administrators to define the delay before a player skin part is applied to a model bone via thebmpartcommand. This provides greater flexibility and control over the timing of asynchronous operations, enabling fine-tuning for server performance and skin-fetching reliability. - Dynamic Skin Part Command (
bmpart): Implemented the newbmpartcommand to interface with BetterModel's skin and bone APIs. This command allows scripts to map a model bone to a player's skin part (e.g., head, arm), enabling dynamic model customization. The feature utilizes a customBoneItemMapperin conjunction withSkinManager#removeCacheto ensure skin textures are fetched and applied correctly, even when updated in real-time by other plugins. - SkinsRestorer Hook, new debug, new config and more
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:shlJaQgd:vxsUvO7U"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:shlJaQgd:vxsUvO7U"
}

