1.4.3
Compatibility
Required content
Changes
New: Clear Grid on Recipe Autofill JEI recipe transfer now clears the Surgery Table's crafting grid, stitches slot, and mutation agent slots (hardening/sharpening/integrating) before filling in a new recipe. Previously, autofill only placed the new recipe's ingredients and left old, non-matching items sitting in the grid — you had to clear them out by hand first. Clearing and filling now happen automatically in one step.
Technical changes:
Implemented a proper client→server→client packet flow for clearing the grid, stitches, and agent slots server-side before the JEI fill runs. Mod is now classified as client + server (previously client-only), since grid-clearing logic runs server-side. This jar must be installed on the server as well as all clients — client-only installs will not work correctly with this version. Added debug logging throughout the clear/fill pipeline for easier diagnosis of future issues.
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:9m2VtUT8:ImTb41re"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9m2VtUT8:ImTb41re"
}

