Tags
Creators
Details
1.7.12
Compatibility
Required content
Changes
[1.7.12] - 2026-07-31
变更 / Changes
-
async-save PalettedContainer 多线程崩溃修复 / async-save PalettedContainer multithreading crash fix: 修复
async-save把整个saveAll重定向到异步线程导致PalettedContainer.pack触发 ThreadingDetector 崩溃的问题。改为统一"主线程序列化 + 异步磁盘 I/O"模式:序列化(PalettedContainer.pack→ NBT 编码)在主线程执行,磁盘 I/O(attemptSaveSubLevel/attemptSaveHoldingChunk)提交到异步线程执行。/ Fixedasync-saveredirecting entiresaveAllto async thread causingPalettedContainer.packThreadingDetector crash. Changed to unified "main-thread serialization + async disk I/O" model: serialization (PalettedContainer.pack→ NBT encoding) runs on main thread, disk I/O (attemptSaveSubLevel/attemptSaveHoldingChunk) submitted to async thread.- 移除 c2me 特殊处理,统一行为。/ Removed c2me special handling, unified behavior.
-
整数极限方块破坏坐标防护 / Integer-overflow block destruction coordinate guard (Issue #14): 新增
block-destroy-coordinate-guard修复项,拦截Level.setBlock和Level.destroyBlock,当坐标超出可配置范围(默认 X/Z ±30M, Y -512~1024)时跳过操作并记录警告(60 秒节流)。/ Addedblock-destroy-coordinate-guardfix: interceptsLevel.setBlockandLevel.destroyBlock, skips operations when coordinates exceed configurable limits (default X/Z ±30M, Y -512~1024) and logs throttled warnings (60s).- 坐标范围可通过
config/fucksable/config.json的fixParams.block-destroy-coordinate-guard节点调整。/ Coordinate limits are configurable viafixParams.block-destroy-coordinate-guardinconfig/fucksable/config.json.
- 坐标范围可通过
-
修复项参数恢复命令 / Fix options reset command: 新增
/fucksable <fix> reset命令,恢复指定修复项的参数到默认值。/ Added/fucksable <fix> resetcommand to reset a fix's options to defaults.
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:YS1hdEUp:LSUn333s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YS1hdEUp:LSUn333s"
}

