## 5.0.0
Updated to Minecraft 26.3, for NeoForge and Fabric.
- Recipes, loot tables and advancements are registry entries in 26.3, so a mod's NeoForge datagen
writes them through `ForgeRegistryEntries` along with its worldgen. It replaces
`ForgeDatapackRegistryProvider` and the recipe `Runner`s, and still writes the files for both loaders.
- `ConditionalRecipeProvider` and `LibBlockLootProvider` are built from 26.3's datagen contexts, and
`IConditionHelper#conditionalContext` gives each entry its load conditions.
- Fuel is an item component now. `IPlatformHelper#isFuel` checks an item on either side,
`#getFuelTime` gives its burn time in a furnace, another block or anywhere on the server, and
`BurnTimes` names the burn times a mod's fuels use.
- `CompostChances` and `IPlatformHelper#modifyDefaultComponents` set components on items, which is
where 26.3 keeps compost chances.
- `LootTableModificationContext#lootTable` gives the holder a nested loot table needs now.
- `SubmitHelper` keeps the `submitModel` calls that drew the block breaking overlay.
- `BlockPosUtil` keeps the box shaped block searches `BlockPos` no longer has.
- On NeoForge the blocks given to `registerFlammable` go in NeoForge's flammable data map, written
by datagen, so a datapack can change their fire odds.
- `HandWrittenData#advancement` reads an advancement a mod writes as json by hand back through
vanilla's codec, so a format change fails datagen instead of the server.
- A manual recipe page skips the recipes that are not loaded, such as ones an optional mod adds, and
only says a recipe is missing when none of its recipes are there.
- `ClientModelCheck` and `ManualCheck` are client gametest helpers. They find blocks and items that
draw the missing texture, and manual pages or station slots that would draw nothing.
- `CommonTests` registers four gametests every mod can share. They check that each recipe is made from
its own ingredients, each block drops something, each block entity reads back what it saved, and each
item is in a creative tab, apart from any the mod names as kept out on purpose. `ClientChecks` runs the client checks from a Fabric client gametest, and
`TestSupport#mortalPlayer` gives a test player that can be hurt. `ClientModelCheck` also readies every
entity's renderer, and `CommonTests#upgradesThatLoseTheirData` checks that storage upgrade recipes keep
what the upgraded item held.
- The `assortedlib:recipe_exists` display condition hides a manual page until one of its recipes is
loaded, and `ChapterBuilder#optionalRecipes` adds a recipe page with it, for recipes another mod's
ingredient turns on. The manual checks its conditions again once recipes reach the client.
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }