Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 22 hours ago
All versions
5.0.0+neoforge
Release
Assorted Lib 5.0.0 (NeoForge)2 days ago 50
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
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
ForgeRegistryEntriesalong with its worldgen. It replacesForgeDatapackRegistryProviderand the recipeRunners, and still writes the files for both loaders. ConditionalRecipeProviderandLibBlockLootProviderare built from 26.3's datagen contexts, andIConditionHelper#conditionalContextgives each entry its load conditions.- Fuel is an item component now.
IPlatformHelper#isFuelchecks an item on either side,#getFuelTimegives its burn time in a furnace, another block or anywhere on the server, andBurnTimesnames the burn times a mod's fuels use. CompostChancesandIPlatformHelper#modifyDefaultComponentsset components on items, which is where 26.3 keeps compost chances.LootTableModificationContext#lootTablegives the holder a nested loot table needs now.SubmitHelperkeeps thesubmitModelcalls that drew the block breaking overlay.BlockPosUtilkeeps the box shaped block searchesBlockPosno longer has.- On NeoForge the blocks given to
registerFlammablego in NeoForge's flammable data map, written by datagen, so a datapack can change their fire odds. HandWrittenData#advancementreads 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.
ClientModelCheckandManualCheckare client gametest helpers. They find blocks and items that draw the missing texture, and manual pages or station slots that would draw nothing.CommonTestsregisters 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.ClientChecksruns the client checks from a Fabric client gametest, andTestSupport#mortalPlayergives a test player that can be hurt.ClientModelCheckalso readies every entity's renderer, andCommonTests#upgradesThatLoseTheirDatachecks that storage upgrade recipes keep what the upgraded item held.- The
assortedlib:recipe_existsdisplay condition hides a manual page until one of its recipes is loaded, andChapterBuilder#optionalRecipesadds a recipe page with it, for recipes another mod's ingredient turns on. The manual checks its conditions again once recipes reach the client.
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:KkmxwW72:WwlKxKyN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KkmxwW72:WwlKxKyN"
}

