Tags
Creators
Details
2.7.0
Compatibility
Changes
Note: this update adds full support for bedrock clients that connect via geyser or floodgate for proxied servers! ResourcePackManager is mandatory to make this work. This should now cover every possible case of bedrock clients connecting to serverss being able to see models.
FreeMinecraftModels 2.7.0:
- [New] sendCustomModelsToBedrockClientsV2 now defaults Bedrock custom-model display to true
- [New] /fmm debug bedrock [on|off] toggles runtime Bedrock display diagnostics
- [New] preventPropPlacementInProtectedRegions blocks prop placement in WorldGuard and GriefPrevention regions unless the player has freeminecraftmodels.bypassregionprotection
- [Fix] Projectile hits now connect with modeled entity hitboxes reliably, including fast arrows, tridents, and rotated models
- [Fix] Projectile hits on dynamic models now damage the underlying entity as projectile hits instead of melee/raw damage
- [Fix] Player disguises now hide and restore armor and held items for other viewers, including players who join or change worlds mid-disguise
- [Fix] MagmaCore Bedrock detection now recognizes Floodgate/Geyser players through plugin, UUID, and username fallbacks so Bedrock viewers stay on the custom-model packet path
- [Fix] MagmaCore NMS packet handling now avoids Bedrock bundle and entity-position desync issues on newer servers
- [Tweak] Prop Lua tables are cached per prop with lazy current_location updates
- [Tweak] Location protection now uses MagmaCore's shared location registry so WorldGuard, GriefPrevention, EliteMobs dungeons, and other registered providers can block protected prop placement
- [Tweak] Setup menu now uses MagmaCore's shared SetupMenuBuilder, Nightbreak setup icons, and setup-done handling
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:cKyU8hoi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dXA9IZkK:cKyU8hoi"
}

