Minecraft 26.3 Pre-Release 1
Overview
Minecraft 26.3 is not yet released. The most notable change so far is the switch from GLFW to SDL, as well as migrating more things to use Data Components.
event.button() == 0 or button == 1 to test for left/right mouse buttons, you must update to use the appropriate InputConstants field instead. The numeric values have changed due to the migration to SDL.Version Catalog
⚠️ Known Issues
Some features are not available on Forge
For a full list of features unsupported on Forge, check the new Loader Parity overview.
If you depend on any of those features, my recommendation is to drop support for Forge. Balm won't be putting major efforts into feature parity with Forge.
Breaking Changes
Removed BalmHooks#setBurnTime
Minecraft provides a Data Component CookingFuel now that you should use.
Removed BalmHooks#blockGrowFeature
This method was only used to fire an event on Forge. There is no direct replacement. If you have need for this, you can define a bi-directional event mapper or use a platform proxy.
Removed BalmCompostableRegistrar
Minecraft provides a Data Component Compostable now that you should use.
Removed BalmResourceReloadListenerRegistrar.VanillaKeys#advancements() and #recipes()
Recipes and Advancements appear to no longer use a resource reload listener.
Replaced BalmItemTags with ConventionalItemTags
Use ConventionalItemTags for conventional c: item tags. Most constants keep the same name, with the following exceptions:
BalmItemTags.DIAMONDSis nowConventionalItemTags.DIAMOND_GEMS.BalmItemTags.EMERALDSis nowConventionalItemTags.EMERALD_GEMS.BalmItemTags.DYE_TAGSis nowConventionalItemTags.COLOR_DYESand uses aColorCollection<TagKey<Item>>instead of an array.BalmItemTags.COOKING_OILhas no replacement, since it was not an official conventional tag.
Balm no longer ships the outdated c: tag data that previously populated these tags. Both Fabric and NeoForge already take care of that.