2.3.2
Compatibility
Changes
点击看中文
- 近期更新频繁,给各位道歉,灵感实在太多了。
- 基于2.3.0开发的GostMod_v2中发现的问题——对局中饱食度会消耗,这显然不符合我之前的设计,在修复的时候我就认为饥饿值是不是也能作为追逐战中决胜的因素之一?随即做出了这个版本。
2.3.2更新内容:
①道具“冲刺矛”向低版本兼容!!
- 在<1.21.4的游戏版本中,冲刺矛的道具将换成“三叉戟”,功能一致,具体的效果是右键向前冲刺5米。
②新增对局饥饿值消耗功能(可配置、可开关)
- 对局现在默认会消耗饥饿值,但是局内可恢复,此功能跟局外的饥饿值独立,结算后会恢复开局前的饱食度。该新功能可配置开关和恢复速度
- 进入对局所有人的饱食度会回满,在游戏过程中奔跑会正常消耗饱食度
- 人类:按下[Shift]蹲下,每秒恢复1饱食度
- 鬼:按下[Shift]蹲下,每0.8秒恢复1饱食度
- 转换阵容时饱食度回满
- 猎魔人阶段饱食度回满且不消耗
- Apologies for the frequent updates lately—my inspiration has been overwhelming.
- An issue was discovered in GostMod_v2, developed based on 2.3.0: hunger would deplete during matches, which clearly contradicted my original design. While fixing it, I started wondering whether hunger could also become a decisive factor in chase battles. That led me to create this version.
Changelog 2.3.2:
① The "Sprint Spear" item now supports backward compatibility with older versions!
- In game versions <1.21.4, the "Sprint Spear" will be replaced with a "Trident," which functions identically—right-clicking allows you to sprint forward 5 meters.
② New feature: Hunger consumption during matches (configurable and toggleable)
- Matches now consume hunger by default, but hunger can be restored during gameplay. This system operates independently from your off-match hunger level and restores your initial saturation at the end of the match. The new feature is fully configurable, including toggling and adjusting recovery speed.
- All players' hunger levels are fully restored upon entering a match. Running during the match consumes hunger normally.
- Humans: Press [Shift] to crouch, regaining 1 point of hunger per second.
- Ghosts: Press [Shift] to crouch, regaining 1 point of hunger every 0.8 seconds.
- Hunger is fully restored when switching teams.
- During the Hunter phase, hunger is fully restored and does not deplete.
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:SKYebqyY:EB3MlYe5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SKYebqyY:EB3MlYe5"
}

