Tags
Creators
Details
All versions
21.11.5+fabric-1.21.11
Release
21.11.5+fabric-1.21.117 months ago 85K
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Server-side
Required content
Changes
- Added
BalmVillagerTradeRegistrarfor registering additional trades to villagers - Added
BalmEntityTypeRegistration.withSpawnPlacementfor defining spawn placement on a new entity - Added
BiomeModificationBuilder.addSpawnandBiomeModificationBuilder.setSpawnCostfor adding mob spawns to biomes - Added
LivingEntityCallback.MobEffectCallback.*for reacting to changes of Potion Effects (server only) - Added
EntityCallback.DimensionChangefor reacting to changes of entity dimensions (client and server) - Added
EventMapper.configureMappingAndReturnto make defining custom event handlers easier inside interfaces - Added
BalmClientTooltipComponentRegistrarfor registering client tooltip component factories - Added
BalmRangeSelectItemModelPropertyRegistrarfor registering custom item model properties - Re-enabled unified recipe viewer support for JEI
- Updated to Loom 1.14 and ForgeGradle 7
- Updated to Kuma 21.11.12
- Added
overrideNameto specify a custom name for a key mapping - Added
skipRegistrationto create virtual key mappings that do not show up in controls - Fixed Kuma-registered keys not being remappable when
Controllingis installed - Fixed
handleWorldInputalways consuming the key on Fabric, even if handler returnedfalse
- Added
- Fixed
LivingEntityCallback.Fallnot respecting new damage amount on NeoForge and Forge - Fixed
LivingEntityCallback.Fallproviding wrong original fall damage on NeoForge and Forge - Fixed
LivingEntityCallback.Healnot respecting new heal amount on NeoForge and Forge - Fixed
RenderCallback.ComputeFovapplying FOV Effects scaling incorrectly on NeoForge and Forge - Fixed various potential concurrency issues in Balm wrappers related to Permissions, Loot Modifiers, Commands and Capabilities
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:MBAkmtvl:ZJWr2IS3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MBAkmtvl:ZJWr2IS3"
}

