Tags
Creators
Details
2.6.0
Compatibility
Changes
FreeMinecraftModels 2.6.0: [New] Geyser/Floodgate support! Geyser/Floodgate clients can now see custom models. Requires ResourcePackManager for the conversions. [New] Craftenmine's Weapons Item Pack — new free scripted item-model pack available now via Nightbreak (and /fmm setup) [New] Craftenmine Tools Item Pack — new premium scripted item-model pack available now via Nightbreak (and /fmm setup) [New] Player disguise system — /fmm disguise <model> [player] and /fmm undisguise [player] disguise yourself (or another player) as any loaded model; mirrors player movement, head rotation, and arm-swing animations [New] /fmm disguiselist admin command to see all active disguises [New] DisguiseAPI public class for third-party plugins (disguise / undisguise / isDisguised / getDisguiseModelID / getDisguisedPlayers) [New] FmmReloadedEvent API — fires after FMM finishes initializing (startup and /fmm reload) so plugins shading FMM can re-attach their custom models [Fix] Custom models on MC 26.1+ no longer fail to bake with "Cannot compute translucency out of bounds" errors (UV coordinates that went past texture bounds are now clamped) [Fix] Custom models on MC 26.1+ no longer spam "Missing block model" warnings for empty/anchor-only bones [Fix] Disguise invisibility now persists through milk buckets, /effect clear, and third-party effect strippers [Fix] /fmm disguise with no model arg now self-disguises correctly instead of erroring [Fix] freeminecraftmodels.* wildcard now properly grants the new disguise permissions [Tweak] Various MagmaCore library improvements (MC 26 Spigot compatibility, Bedrock position sync, classloader isolation for shaded copies, etc.) [Tweak] plugin.yml api-version updated from 1.18 to 1.21.4 [Tweak] Added .gitignore for Maven build artifacts and IDE files
Optional dependencies
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:dXA9IZkK:hZ6W5eiK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dXA9IZkK:hZ6W5eiK"
}

