Links
Tags
Creators
Details
All versions
0.15.1
Beta
Beta 0.15.13 years ago 336
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Fabric
Supported environments
Client and server
Changes
- When holding
Shiftwhile falling will buffer a small amount of damage. - Added automatic check for updates
- Players now cannot sleep until after 21:00 game time (new thread)
- Fixed the following bugs:
- Spear and spiked club can cut down trees.
- Spear digging speed is ok, so much so that it can replace stone cones.
- Game difficulty and sponsorship hints reappear after death
- Difficulty display problem
- Zombies can't destroy stone and harder blocks unless they have the corresponding tool(s) in their hands
- Abnormal amount of meat drops when animals are killed (up to 10 meats drops from one chick)
- Optimized the following:
- Getting unhappy is too fast
- Stone cone digging is too slow
- Slight bleeding jumped from one to severe bleeding after re-injuries
- Creepers blowing up wood, ores or nuggets, and TNT blowing up ore and nuggets won't drop items now
- Reduced food saturation gain (e.g. cooked animal viscera)
- zombies are too sensitive with X-ray abilities (retained in challenge mode)
- Bandages' using time is prolonged
- When the life limit is too low, it is easy to bleed after getting injured.
- Mod welcome prompt is too long
- 添加了下落时按住
Shift能缓冲少量伤害的设定 - 添加了自动检查更新功能
- 游戏时间21点以后才能入睡
- 修复了以下bug:
- 矛和狼牙棒能砍树
- 矛挖土速度还行,以至于可以替代石锥
- 游戏难度和赞助提示会在死亡后再次出现
- 游戏难度显示有问题
- 僵尸除非拿上了对应的工具,不然就不能破坏石头及以上硬度的方块
- 幼年动物被杀死时掉落异常数量的小肉(最多的时候一只小鸡掉了10个小肉)
- 优化了以下内容:
- 忧郁速度过快
- 石锥挖掘过慢
- 轻微出血再次受伤后从一下子跳到严重出血
- 苦力怕炸木头、矿石或金属块、TNT炸矿石或金属块会掉落物品
- 降低食物饱和度所得(如熟动物内脏)
- 僵尸的感知能力过强,还能透视(挑战模式保留)
- 绷带使用前摇过长
- 生命上限过低受伤容易大出血的bug
- Mod欢迎提示过长
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:N0Q7g8Xn:LUcCpt8Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N0Q7g8Xn:LUcCpt8Q"
}

