Balm (模组MOD的英文名)

- Fixed Balm capabilities not being exposed as mod-loader native capabilities on Fabric and NeoForge

- Fixed Balm capabilities not being exposed as mod-loader native capabilities on Fabric and NeoForge

- Fixed Balm capabilities not being exposed as mod-loader native capabilities on Fabric and NeoForge

- Fixed Balm capabilities not being exposed as mod-loader native capabilities on Fabric and NeoForge

- Fixed Balm capabilities not being exposed as mod-loader native capabilities on Fabric and NeoForge

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world

- Fixed unsynced properties resetting to default when joining a world
---
- Backported new config system from 1.21.5
- Waystones, Ex Compressum and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Fixed unsynced properties resetting to default when joining a world
---
- Backported new config system from 1.21.5
- Waystones, Ex Compressum and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Added `BalmConfig.onConfigAvailable` to access config safely during initialization
- Added `Balm.isDevelopmentEnvironment()`
- Fixed ResourceLocation options not showing in Cloth Config screen
- Fixed crash when accessing config from multiple threads
- Fixed `BalmItems` being unable to add items to existing creative tabs
- Changed `/balm export config` command to take schema id instead of class name

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed ServerStartingEvent not firing on NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Fixed synced config properties not being respected on Forge and NeoForge

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5
- Fixed empty comments being written into config file on Fabric

- Fixed crash when using the sink in Cooking for Blockheads

- Fixed version reject when joining world on Forge
- Fixed crash when joining world on Forge

- Fixed version reject when joining world on Forge
- Fixed crash when joining world on Forge

- Fixed crash on joining dedicated servers on NeoForge and Forge

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5

- Fixed crash on joining dedicated servers on NeoForge and Forge

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5

- Fixed crash on joining dedicated servers on NeoForge and Forge

- Fixed config sync not working
- Fixed fallback providers for native capabilities not being registered on NeoForge and Forge

- Fixed crash on joining dedicated servers on NeoForge and Forge

- Fixed config sync not working
- Fixed fallback providers for native capabilities not being registered on NeoForge and Forge

- Fixed config sync not working
- Fixed fallback providers for native capabilities not being registered on NeoForge and Forge

- Fixed config sync not working
- Fixed fallback providers for native capabilities not being registered on NeoForge and Forge

- Fixed config sync not working
- Fixed fallback providers for native capabilities not being registered on NeoForge and Forge

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5

- Backported new config system from 1.21.5
- Waystones, Ex Compressum, Forgiving Void and Fertilization should be updated alongside this version to avoid crashes
- Backported new capabilities system from 1.21.5
- Backported other minor changes from 1.21.5

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly
- Fixed crash when calling sendToServer while not ingame on Fabric
- Added SidedProxy.build() and SidedProxy.buildLazily()
- Added Balm.getEnvironment()

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly
- Fixed crash when calling sendToServer while not ingame on Fabric
- Added SidedProxy.build() and SidedProxy.buildLazily()
- Added Balm.getEnvironment()

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly
- Fixed crash when calling sendToServer while not ingame on Fabric
- Added SidedProxy.build() and SidedProxy.buildLazily()
- Added Balm.getEnvironment()

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed version verification falsely treating allowServerOnly/allowClientOnly as denyServerOnly/denyClientOnly

- Fixed crash with custom stats on Forge
- Fixed crash when calling sendToServer while not ingame on Fabric

- Added SidedProxy.build() and SidedProxy.buildLazily()
- Added Balm.getEnvironment()
- Fixed capability providers on Forge not being registered

- Updated to Minecraft 1.21.5
- Added `BalmModule` and `BalmClientModule` as an alternative more structured way of initializing a mod with Balm
- Added `Balm.onRuntimeAvailable` and `BalmClient.onRuntimeAvailable` to allow more stable access to Balm outside of mod loader lifecycles
- Added `BlockGetter` and `BlockPos` to `DigSpeedEvent`, now sets the final value on all loaders
- Refactored Capabilities support to reduce mod-loader-specific overhead
- Refactored Configs to allow for declarative config schemas and cleaner implementation
- Balm mods no longer need to register their own config sync packet
- Added `BalmClient.addResourceReloadListener()`
- Added `ConfigLoadedEvent`
- Fixed `ScreenInit` events not firing reliably for all screens
- Fixed `GuiDrawEvent` not firing
- Changed config i18n to use `modid.configuration.category.key` format
- Changed client-side registration methods to require identifiers
- Removed several obsolete hooks from `BalmHooks`
- Removed obsolete key mapping methods - use Kuma instead
- Removed obsolete `BalmTextures`
- Removed `ExtractionAwareContainer` in favor of `WorldlyContainer`
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition` to register custom resource conditions
- Added `balm:config` resource condition to check a config option against a stringified value

- Fixed potential crash when using `BalmModule` (e.g. Waystones)
- Fixed crash on dedicated servers
- Fixed crash with Sinytra Connector (for real now)

- Fixed potential crash when using `BalmModule` (e.g. Waystones)
- Fixed crash on dedicated servers
- Fixed crash with Sinytra Connector (for real now)

- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed GuiDrawEvent not firing on Forge and NeoForge
- Fixed crash with Sinytra Connector (again)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on Forge and NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition`

- Fixed crash when opening mod menu
- Fixed crash with Sinytra Connector (again)
- Renamed `balm-fabric:milk` to `balm:milk` (should automatically migrate via alias)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition` to register custom resource conditions
- Added `balm:config` resource condition to check a config option against a stringified value

- Fixed crash when opening mod menu
- Fixed crash with Sinytra Connector (again)
- Renamed `balm-fabric:milk` to `balm:milk` (should automatically migrate via alias)
- Added `BalmNetworking.defineNetworkVersion` for more control over network compatibility
- Fabric's remote version check now uses the network version (which defaults to the mod version)
- Network version is also used to version the channel on NeoForge
- Added remote version verification even on client/server-only compatible mods if they are installed on both sides
- Added `BalmResources.registerResourceCondition` to register custom resource conditions
- Added `balm:config` resource condition to check a config option against a stringified value

- Updated to Minecraft 1.21.5
- Added `BalmModule` and `BalmClientModule` as an alternative more structured way of initializing a mod with Balm
- Added `Balm.onRuntimeAvailable` and `BalmClient.onRuntimeAvailable` to allow more stable access to Balm outside of mod loader lifecycles
- Added `BlockGetter` and `BlockPos` to `DigSpeedEvent`, now sets the final value on all loaders
- Refactored Capabilities support to reduce mod-loader-specific overhead
- Refactored Configs to allow for declarative config schemas and cleaner implementation
- Balm mods no longer need to register their own config sync packet
- Added `BalmClient.addResourceReloadListener()`
- Added `ConfigLoadedEvent`
- Fixed `ScreenInit` events not firing reliably for all screens on NeoForge
- Fixed `GuiDrawEvent` not firing on NeoForge
- Changed config i18n to use `modid.configuration.category.key` format
- Changed client-side registration methods to require identifiers
- Removed several obsolete hooks from `BalmHooks`
- Removed obsolete key mapping methods - use Kuma instead
- Removed obsolete `BalmTextures`
- Removed `ExtractionAwareContainer` in favor of `WorldlyContainer`

- Updated to Minecraft 1.21.5
- Added `BalmModule` and `BalmClientModule` as an alternative more structured way of initializing a mod with Balm
- Added `Balm.onRuntimeAvailable` and `BalmClient.onRuntimeAvailable` to allow more stable access to Balm outside of mod loader lifecycles
- Added `BlockGetter` and `BlockPos` to `DigSpeedEvent`, now sets the final value on all loaders
- Refactored Capabilities support to reduce mod-loader-specific overhead
- Refactored Configs to allow for declarative config schemas and cleaner implementation
- Balm mods no longer need to register their own config sync packet
- Added `BalmClient.addResourceReloadListener()`
- Added `ConfigLoadedEvent`
- Fixed `ScreenInit` events not firing reliably for all screens on NeoForge
- Fixed `GuiDrawEvent` not firing on NeoForge
- Changed config i18n to use `modid.configuration.category.key` format
- Changed client-side registration methods to require identifiers
- Removed several obsolete hooks from `BalmHooks`
- Removed obsolete key mapping methods - use Kuma instead
- Removed obsolete `BalmTextures`
- Removed `ExtractionAwareContainer` in favor of `WorldlyContainer`

- Updated to Minecraft 1.21.5

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash on startup on Forge

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Revert parts of initial fix to fix another threading issue causing a crash on startup
- Never doing workarounds for Sinytra Connector again

---

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash on startup on Forge

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash on startup on Forge

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- Fixed threading issue causing Balm to not initialize things correctly when multiple Balm mods are present, causing lots of weird followup issues

---

- Fixed crash on startup on Forge

---

- Fixed crash when mods falsely access Balm too early e.g. due to Sinytra Connector

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- 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 `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Added `BalmRegistries.register(...)` to allow registering objects into any registry
- Added `BalmParticles` to 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 `BalmPermissions` with support for Neo/Forge PermissionAPI and fabric-permissions-api
- Added `balm.command.balm.dev`, `balm.command.balm.export.config`, `balm.command.balm.export.icons` permission nodes
- Added crash when active config is unexpectedly set to null to avoid confusing errors later on
- Fixed `OnLoadHandler` not 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 export` commands 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

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed ScreenInitEvent not firing on options screen
- Fixed ScreenInitEvent.Pre falsely running on AFTER_INIT on Fabric
- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed comments in lists of configs being treated as corrupted config in Fabric
- Fixed potential crashes with configs being null
- Will now log an error to help debug how they ended up becoming null

- Fixed crash on startup on Fabric
- Added network registration methods with StreamCodecs, deprecate old ones
- Renamed `openGui` to `openMenu`, deprecated old method

- Fixed crash on startup on Fabric
- Added network registration methods with StreamCodecs, deprecate old ones
- Renamed `openGui` to `openMenu`, deprecated old method

- Fixed crash on startup on Fabric
- Added network registration methods with StreamCodecs, deprecate old ones
- Renamed `openGui` to `openMenu`, deprecated old method

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Fixed `/balm` command not registering on Fabric
- Marked current deprecation for removal in Minecraft 1.22

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Fixed `/balm` command not registering on Fabric
- Marked current deprecation for removal in Minecraft 1.22

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Fixed `/balm` command not registering on Fabric
- Marked current deprecation for removal in Minecraft 1.22

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Backported newer block/item registration methods with identifier in callback, deprecated old ones
- Backported `registerPoiType`
- Fixed `/balm` command not registering on Fabric

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Backported newer block/item registration methods with identifier in callback, deprecated old ones
- Backported `registerPoiType`
- Fixed `/balm` command not registering on Fabric

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Backported newer block/item registration methods with identifier in callback, deprecated old ones
- Backported `registerPoiType`
- Fixed `/balm` command not registering on Fabric

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Backported newer block/item registration methods with identifier in callback, deprecated old ones
- Backported `BalmProxy.isIngame()` and `BalmProxy.isClient()`
- Backported `/balm` commands

- Added compatibility layer for Jade/WTHIT/TheOneProbe
- Fixed `LevelLoading.Load` event not firing for client levels on Fabric
- Added `registerRecipeSerializer` and `registerRecipeType`, deprecate old `registerRecipeType` method that combined both
- Backported newer block/item registration methods with identifier in callback, deprecated old ones
- Backported `BalmProxy.isIngame()` and `BalmProxy.isClient()`
- Backported `/balm` commands

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Added compatibility layer for Curios and Trinkets
- Fixed addon classes for Fabric mods loading too early

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- Fixed crash related to pushing/pulling items using hoppers or similar
- Fixed LivingDeathEvent not firing on Fabric

- **Requires NeoForge 21.4.84-beta or above**.
- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- **Requires NeoForge 21.4.84-beta or above**.
- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- **Requires NeoForge 21.4.84-beta or above**.
- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Fixed loot modifiers not applying on dedicated servers
- Fixed potential issues with some container blocks

- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- **Requires NeoForge 21.4.84-beta or above**. Updated for breaking change in NeoForge.
- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- **Requires NeoForge 21.4.84-beta or above**. Updated for breaking change in NeoForge.
- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- **Requires NeoForge 21.4.84-beta or above**. Updated for breaking change in NeoForge.
- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- Added disconnect on join when client mod version does not match server mod version on Fabric
- Added support for Configured on Fabric
- Fixed extraneous fields appearing on Fabric config screens

- Fixed Forge crash when receiving a config reload event without config data

- Added automatic migration of Balm entity data between NeoForge/Fabric/Forge
- Fixed crash when mod returns null container on Fabric

- Added automatic migration of Balm entity data between NeoForge/Fabric/Forge
- Fixed crash when mod returns null container on Fabric

- Added automatic migration of Balm entity data between NeoForge/Fabric/Forge
- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash when mod returns null container on Fabric

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed crash on dedicated servers

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed ClientStartedEvent firing twice, likely causing issues in Default Options

- Fixed model load errors on NeoForge causing Cooking for Blockheads to crash

- Fixed model load errors on NeoForge causing Cooking for Blockheads to crash

- Fixed crash when using mods like Crafting Tweaks and Inventory Essentials together in a small pack

- Fixed crash when using mods like Crafting Tweaks and Inventory Essentials together in a small pack

- Updated to Minecraft 1.21.4

- Updated to Minecraft 1.21.4

- Fixed crash on dedicated servers
- Added support for NeoForge's config screen

- Fixed crash on dedicated servers
- Added support for NeoForge's config screen

- Added support for NeoForge's config screen

- Added support for NeoForge's config screen

- Updated to Minecraft 1.21.2

- Updated to Minecraft 1.21.2

- Fixed crash on newer Forge versions

- Fixed crash on newer Forge versions

- Fixed crash on newer Forge versions

- Fixed biome modifiers not working on NeoForge, causing wild waystones to not spawn

- Fixed biome modifiers not working on NeoForge, causing wild waystones to not spawn

- Fixed biome modifiers not working on NeoForge, causing wild waystones to not spawn

- Fixed crash on dedicated servers
- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed crash on dedicated servers
- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed crash on dedicated servers
- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed crash on dedicated servers
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed crash on dedicated servers
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed embedded Kuma causing crash on Fabric
- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed potential crash with other mods in regards to the dummy milk fluid

- Fixed potential crash with other mods in regards to the dummy milk fluid

- Updated to Minecraft 1.21.1

- Updated to Minecraft 1.21.1

- Updated to Minecraft 1.21.1

- Added support for Reborn Energy on Fabric
- Fixed milk fluid causing errors with certain other mods

- Added support for Reborn Energy on Fabric
- Fixed milk fluid causing errors with certain other mods

- Fixed configs not loading properly on NeoForge
- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed configs not loading properly on NeoForge
- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed configs not loading properly on NeoForge
- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Updated to Breaking Changes of NeoForge 21.0.82
- USE BALM 21.0.12 FOR NEOFORGE VERSIONS BEFORE 21.0.82
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed UseItemInputEvent not respecting cancellation correctly

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Updated to Breaking Changes of NeoForge 21.0.40
- USE BALM 21.0.9 FOR NEOFORGE VERSIONS BEFORE 21.0.40
- USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31

- Fixed milk fluid crash on Fabric

- Updated to Breaking Changes of NeoForge 21.0.31 - USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed milk fluid crash on Fabric

- Updated to Breaking Changes of NeoForge 21.0.31 - USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed milk fluid crash on Fabric

- Updated to Breaking Changes of NeoForge 21.0.31 - USE BALM 21.0.7 FOR NEOFORGE VERSIONS BEFORE 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed config load issues with \r\n newlines
- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Fixed config load issues with \r\n newlines
- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Updated to Breaking Changes of NeoForge 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed config load issues with \r\n newlines
- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Fixed config load issues with \r\n newlines

- Updated to Breaking Changes of NeoForge 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed config load issues with \r\n newlines

- Updated to Breaking Changes of NeoForge 21.0.31
- Fixed config load issues with \r\n newlines

- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Fixed certain modded player data (like activated waystones) not pchersisting properly on Forge

- Update Kuma API to fix log spam issues and Forge dedicated server crash

- Update Kuma API to fix log spam issues and Forge dedicated server crash
- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Update Kuma API to fix log spam issues and Forge dedicated server crash

- Update Kuma API to fix log spam issues and Forge dedicated server crash
- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Update Kuma API to fix log spam issues and Forge dedicated server crash

- Update Kuma API to fix log spam issues and Forge dedicated server crash
- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed certain modded player data (like activated waystones) not persisting properly on Forge

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Fixed startup crash on NeoForge with certain mods
- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Updated to Minecraft 1.21

- Hotfix: Fixed crash on startup on Forge

- Fixed fluid storages not working correctly on Fabric
- Added embedded Kuma API, which will be responFsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Hotfix: Fixed crash on startup on Forge

- Fixed fluid storages not working correctly on Fabric
- Added embedded Kuma API, which will be responFsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Fixed fluid storages not working correctly on Fabric
- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Fixed fluid storages not working correctly on Fabric
- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated Kuma API to fix another issue in Inventory Essentials

- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated to NeoForge 20.6.78-beta changes

- Hotfix: Fixed Balm no longer working on client-only or server-only due to Reborn Energy API inclusion
- Updated to Minecraft 1.20.6

- Updated Kuma API to fix another issue in Inventory Essentials

- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated to NeoForge 20.6.78-beta changes

- Hotfix: Fixed Balm no longer working on client-only or server-only due to Reborn Energy API inclusion
- Updated to Minecraft 1.20.6

- Updated Kuma API to fix another issue in Inventory Essentials

- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated to NeoForge 20.6.78-beta changes

- Hotfix: Fixed Balm no longer working on client-only or server-only due to Reborn Energy API inclusion
- Updated to Minecraft 1.20.6

- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated to NeoForge 20.6.78-beta changes

- Hotfix: Fixed Balm no longer working on client-only or server-only due to Reborn Energy API inclusion
- Updated to Minecraft 1.20.6

- Added embedded Kuma API, which will be responsible for advanced key mappings in Inventory Essentials and Crafting Tweaks

- Updated to NeoForge 20.6.78-beta changes

- Hotfix: Fixed Balm no longer working on client-only or server-only due to Reborn Energy API inclusion
- Updated to Minecraft 1.20.6