1.3.6
Compatibility
Changes
v1.3.6 — Super Golem Persistence Fix
Fix: Super golems no longer revert to normal copper golems after a chunk unload or server restart — their status is now persisted to plugins/TurboGolem/supergolems.yml and restored automatically (via EntityAddToWorldEvent and a startup scan).
Fix: Super golems are re-anchored to their copper chest if pushed away (water, pistons, players), so they keep sorting items and emitting particles.
Fix: /turbogolem killgolems now also clears persisted records for golems whose chunks are currently unloaded.
Fix: Breaking the copper chest now removes the anchored super golem instead of leaving it floating forever.
Fix: A super golem record is only dropped after a 30s grace period when its chunk is loaded but the entity is briefly missing, preventing accidental removal during chunk-load races.
修复: 超级铜傀儡不再因区块卸载或服务器重启而退化成普通铜傀儡——状态持久化到 plugins/TurboGolem/supergolems.yml,并通过 EntityAddToWorldEvent 与启动扫描自动恢复。
修复: 超级铜傀儡被水流/活塞/玩家推动后自动传送回铜块,保持分拣与粒子效果。
修复: /turbogolem killgolems 也会清理区块未加载的持久化记录。
修复: 挖掉铜块会移除其上的超级铜傀儡,不再留下悬浮实体。
修复: 记录仅在“区块已加载但实体短暂缺失”超过 30 秒后才删除,避免区块加载瞬间误删。
注意: v1.3.5 及更早召唤的、已变普通的超级铜傀儡无法自动恢复,请重新用 /supergolem 召唤。
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:KurIlDYT:kZiDxvnT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KurIlDYT:kZiDxvnT"
}

