All versions
12.4.2-194
Release
12.4.2-194last year 423K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
- Add feature for the item router to filter by mod in addition to tags (BluSunrize)
- Add "fluid" as an optional element in cloche recipes (BluSunrize)
- Crimson and warped fungi are now grown with lava
- If not specified, the recipe will use water
- Add the item hatch, which allows pulling a single stack from an inventory (BluSunrize)
- Change extracting conveyors to have configurable stack-size instead of configurable tickrate (BluSunrize)
- This requires existing conveyors to be adjusted again
- Change insertion logic for the storage shelf (BluSunrize)
- Will now try to fill slots with the same item, otherwise place in slots immediately after that item
- This should keep individual crates on the shelf more organized
- Works for shift-clicking and automatic insertion!
- Change illager loot tables (BluSunrize)
- Fusiliers and bulwarks now respect looting
- Commandos no longer drop emeralds
- Fix mixer accidentally crafting a lingering awkward potion (BluSunrize)
- Fix catwalks not working properly when using a hammer (BluSunrize)
- Fix shift-click behavior in the Engineer's Crafting Table (BluSunrize)
- Fix chutes not accepting item input from the side (BluSunrize)
- Fix engineer illagers not dropping their raid banner (BluSunrize)
- Fix shelves causing crashes when accessed from unexpected sides (BluSunrize)
- Fix windows used in multiblocks being too directionally dependent (BluSunrize)
- Fix backpack antenna not (visually) disconnecting from wires (BluSunrize)
- Translations Added/Updated: zh_cn (qingfeng13579)
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:tIm2nV03:uNRARSH2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tIm2nV03:uNRARSH2"
}
