Tags
Creators
Details
1.1.0.4
Compatibility
Changes
原文
- 继续修复多线程和ae2的线程安全问题
- 继续修复多线程和create的线程安全问题
- 修复1.21的tacz和多线程的兼容问题
- 修复1.21的curios和多线程的兼容问题
- 修复1.21的pipesnphysics和多线程的兼容问题
- 修复1.21的refinedstorage和多线程的兼容问题
- 修复RedstoneTorchBlock异步问题
Translation
-Continue to fix thread safety issues with multithreading and AE2 -Continue to fix thread safety issues with multithreading and create -Fix compatibility issues with Tacz and multithreading in version 1.21 -Fix compatibility issues with Curios and multithreading in version 1.21 -Fix compatibility issues with pipesnphysics and multithreading in version 1.21 -Fix compatibility issues with Refined Storage and multithreading in version 1.21 -Fix Redstone TorchBlock asynchronous issue
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:GMjacMKh:4VV0SQ0y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GMjacMKh:4VV0SQ0y"
}

