Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 7 months ago
Updated 2 days ago
All versions
1.8
Release
Carpet EDTP Addition 1.82 days ago 21
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
更新内容
新内容:
- 添加规则:
snowlessDepths:Y=0 以下无法自然生成或增厚雪层,不影响雪傀儡造雪和细雪炼药锅。noChickenJockeysOnMagmaBlocks:阻止鸡骑士在岩浆块上生成。
新增规则均默认关闭。
- 添加 Fabric GameTest 与 CI 检查,覆盖寒冷群系降雪、Y=0 边界、Y<0 积雪限制、雪傀儡和细雪炼药锅行为。
- 将 Fabric Loom 从
1.15.4升级至1.16.3。
Bug 修复:
- 将
resonantWater的水桶注入改为WrapOperation,仅处理放置分支(ordinal = 0),通过original.call(...)保留其他模组的调用链,维持 ViaFabricPlus 兼容性,规则原有功能不受影响。 - 为 TNT 爆炸掉落处理补充非空参数注解,不改变规则行为。
- 修复运行时修改
tickCommandForAll后,在线玩家的命令树没有刷新、需要重新登录才能使用/tick的问题。
Update Details
What's New:
- Added rules:
snowlessDepths: Prevents snow layers from naturally forming or growing below Y=0 without affecting snow golems or powder snow cauldrons.noChickenJockeysOnMagmaBlocks: Prevents chicken jockeys from spawning on magma blocks.
Both new rules are disabled by default.
- Added Fabric GameTest coverage and CI checks for snowfall in cold biomes, the Y=0 boundary, snow restrictions below Y=0, snow golems, and powder snow cauldrons.
- Updated Fabric Loom from
1.15.4to1.16.3.
Bug Fixes:
- Changed the
resonantWaterbucket injection toWrapOperation, targeting only the placement branch (ordinal = 0). Delegating throughoriginal.call(...)preserves other mods' call chains and maintains ViaFabricPlus compatibility without changing the rule's existing behavior. - Added a non-null parameter annotation to TNT explosion drop handling without changing the rule's behavior.
- Fixed
tickCommandForAllnot refreshing the command tree of connected players when changed at runtime, which previously required players to reconnect before using/tick.
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:slX6HdVH:9W3nCzaX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:slX6HdVH:9W3nCzaX"
}

