1.3.0
Compatibility
Required content
Changes
Automation & Colors update for Minecraft 1.21.1 (Fabric + NeoForge): hopper automation, generator toggles and 16 new dye generators — 47 total on this version.
- Hopper automation: hoppers and item pipes can now pull produced items straight out of any generator, from any side (insertion stays blocked — generators only output). Comparators read the buffer fill level. Requested by ratiflette_219 in the comments — thanks!
- Generator toggles: every set (ores, wood, stone, colors) can be disabled in the config, plus per-generator overrides (Category default / Forced ON / Forced OFF) picked from dropdowns — no typing ids. Disabling a generator stops its production instantly and removes its recipe, recipe-book entry, creative-tab entry and JEI/EMI/REI listing when you join the world or run
/reload. Placed blocks stay in the world, show OFF on the HUD and can still be emptied. Requested by NerdySNES — thanks! - New: 16 Color generators, one per vanilla dye. Every recipe follows the same pattern: glass corners, the dye's source item on top and bottom, bone meal on the sides, and the dye itself as the center sample (crafting-unlock item). All produce every 5 s with a 1024 buffer.
- The internal buffer is now backed by real inventory slots (that's what hoppers see). Existing worlds migrate automatically — nothing to do, no items lost. Offline production works exactly as before.
- Fully localized: English + Spanish (es_ES).
- No changes to the existing 31 generators' recipes or production stats.
Version numbers stay aligned with the Bedrock edition: its v1.3.0 is the Colors update. The automation features are Java-first.
Optional dependencies
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:4BHtTMuL:Pt8uI5ZK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BHtTMuL:Pt8uI5ZK"
}




