Links
Tags
Creators
Details
1.1.1-hotfix.1+26.2
Compatibility
Required content
Changes
Fix: With the printer's Servux hand-confirmation option enabled and Litematica's own entity-data sync disabled, newer Litematica builds could suppress the metadata/entity requests needed to confirm the server-held item. Printing would then wait indefinitely. The printer now opens Litematica's handler-level request gate while that option is enabled, without changing Litematica's saved setting or duplicating its v1/v2 protocol handling. Printing actions and other modes are unchanged.
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:Im0hpzfN:ASNgFr6p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Im0hpzfN:ASNgFr6p"
}

