1.2.0
Compatibility
Changes
Stonecutter Sifting 1.2.0
Stonecutter Sifting has been rebuilt as a fully configurable, data-driven sifting system. You can now customize what each block produces without editing the mod or writing code.
- JSON configuration: Create, edit, disable, and organize sifting recipes inside
config/scsifting/. - Custom drops: Set individual drop chances, define multiple independent output pools, and combine results from the same sift.
- Dynamic item pools: Use item tags, registry-name matching, and mod namespaces to include compatible items automatically.
- Processing settings: Adjust speed and batch size, enable instant processing, and control sounds and particles.
- Multiplayer support: Dedicated servers control the active configuration, which is synchronized to clients and their recipe viewers.
- Automation improvements: Queued inputs stay on the Stonecutter until processed, while finished results can be collected by Hoppers and compatible automation.
- JEI and EMI: Updated recipes, cycling result slots, clearer probability tooltips, and displays that follow the active server configuration.
- Default recipes: Rebalanced default drops.
Examples, validation, world-specific overrides, and a utility for restoring bundled defaults were added for an easier setup.
Compatibility: Minecraft 1.20.1, Forge 47.2.0+. JEI and EMI are optional. The mod must be installed on both the server and clients.
Note: Existing configurations are preserved. Use restore_defaults.bat inside config/scsifting/ to restore the updated default recipes.
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:SeAO1duq:Q2jBFkH2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SeAO1duq:Q2jBFkH2"
}

