All versions
1.20.1-1.0.8.1.119
Release
1.20.1-1.0.8.1.119last year 111K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Changelog
General
- Update to version 1.0.8.1
Features
- Added ITEM_CRAFTED event
- Added ENTITY_AUTOMATION ApiLookup
Fixes
- Fix a bug where Controller blocks would randomly stop inserting items
- Fix a bug where Controller blocks could lead to a crash
- Fixes a bug where stopping a jukebox after pressing the play button twice was not possible
- Fixes a bug that could lead to desynchronization between server and client when using the paintbrush
Merged from upstream
Features
- Added a bit of support for finer shaped recipe results definition
- Changed upgrade code to allow carts running them
- Added support for recipe types other than just crafting to transfer from JEI functionality
- Added support for ticking render logic in upgrade tabs (at the moment used for rotating slot backgrounds in backpack's smithing upgrade)
- Added new Paintbrush item that allows applying decorations to storage blocks in world
- put into Decoration Table instead of storage to set the decorations that the paintbrush applies
- right click blocks in world to apply the decoration
- works on individual storage blocks as well as on storage controller to apply the decoration to all storages in controller multiblock
- pulls blocks / dyes needed to apply the decoration from player's inventory as well as from any container items including backpacks
Fixes
- Fixed feeding upgrade to only put original main hand item into player's hand after all of its logic is done because some foods shrink the stack only in finishUsingItem which was taking from whatever item player had in hand
- Fixed sophisticated guis to not double render player inventory slots
- Fixed storage gui to close if something has messed with number of slots in the storage like in case of double chest when creeper explodes half of it
- Fixed fluid filters in pump upgrades so that they can be set and cleared properly
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:9jxwkYQL:KrzdxAak"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9jxwkYQL:KrzdxAak"
}



