Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 3 months ago
All versions
0.2.0
Release
Compressed Furnace 0.2.08 months ago 6,907
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Version [0.2.0] (Release Date: 2025-11-17)
Features
- Input Lock System:
- Inputs are now “linked” to their outputs.
- Each input slot shows which items are allowed there, based on what it will turn into.
- You can no longer put items into an input if that slot can’t process them.
- Hoppers/pipes and other automation follow the same rules.
- Powered versions of the machines use this same system.
Bug Fixes
- Fixed a serious issue where powered machines could sometimes erase their items and stored energy.
- Fixed the powered machines trying to use a fuel slot they don’t actually have, which could break their data.
Improvements
- Saving and loading for powered machines is more reliable:
- Fixed cases where their internal cooking progress could become invalid after loading a world.
- Powered machines that previously showed “stuck” or extremely long cook times should now correct themselves when the world loads.
- The auto‑split feature has been updated:
- Items are only split between input slots that produce the same output.
- This helps stop items from being spread into slots that can’t process them.
Notes
- On existing worlds, powered machines already in a broken state may have their current progress reset once after updating, but they should work correctly afterward.
Future
- The auto‑split system will continue to be improved in future updates, especially for setups with many different recipes at once and mixed inputs.
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:So5bK0mE:JR7nZkNB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:So5bK0mE:JR7nZkNB"
}

