Tags
Creators
Details
All versions
7.3.20+forge-1.20.1
Release
7.3.20+forge-1.20.1last year 122.9K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Server-side
Changes
- Removed outdated keymapping mixins as they never worked well and resulted in Balm being loaded too early with Essential
- Shouldn't have any effect on Balm mods since all that depended on this already migrated to Kuma
- Added
BalmRegistries.register(...)to allow registering objects into any registry - Added
BalmParticlesto allow registering particles - Added
BalmRenderers.registerParticleProvider(...)to allow registering particle renderer providers - Added
Balm.platformProxy().withForge(...).withFabric(...).build()as a simple alternative to SPI for platform-specific implementations - Added
Balm.modProxy().with(modId, className).withMultiplexer(...).withFallback(...)for abstracting away mod compat under common interfaces - Added
BalmPermissionswith support for Neo/Forge PermissionAPI and fabric-permissions-api - Added
balm.command.balm.dev,balm.command.balm.export.config,balm.command.balm.export.iconspermission nodes - Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed
OnLoadHandlernot working on block entities in Fabric - Fixed in-memory config potentially being reset to default on Forge instead of using data from config load event
- Fixed PoiTypes not registering properly on Fabric
- Fixed Kuma version pinning to avoid shipping snapshots
- Changed
balm exportcommands to require op - Changed mod id on Fabric to "balm" ("balm-fabric" is still provided for backwards compatibility)
- Deprecated most getters in BalmRegistries since Vanilla equivalents can be used nowadays
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:m4NlBwVG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MBAkmtvl:m4NlBwVG"
}

