- Fixed remote mod versions no longer being verified when connecting to a Fabric server
- Fixed optional mods always being considered uninstalled on clients when connecting to a NeoForge server
- Fixed server-client-optional mods sending packets even if the remote does not have the mod installed
- Updated minimum Fabric Loader version requirement, as older versions of Fabric Loader are not loading jarjar'd Kuma correctly
- For developers:
- Added
.sortedValues()helper toDiscriminatedBlocks, useful for data generators to have consistent order - Added
SessionLocalfor tracking state scoped to the client connection - Changed
sendTo*to only send if channel is supported or mod is announced
- Added
- Fixed ItemStack#is mixin to be less invasive, to prevent potentially breaking other mods targetting the same method
- Fixed wrong class name for Fabric common proxy
- Fixed wrong provider class for Configured on Fabric
- Fixed ItemStack#is mixin to be less invasive, to prevent potentially breaking other mods targetting the same method
- 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
BalmClientTooltipComponentRegistrarfor registering client tooltip component factories - Fixed various potential concurrency issues in Balm wrappers related to Permissions, Loot Modifiers, Commands and Capabilities
- Fixed
ContainerScreenDrawEvent.Backgroundfiring unreliably on Fabric
- Fixed Amecs support failing to initialize
- Fixed various potential concurrency issues in Balm wrappers and registrars
- Fixed
/balm export iconsnot working sometimes
