Links
Tags
Creators
Details
1.2.5
Compatibility
Changes
本次更新将 Fabric / Forge / NeoForge 四个版本的功能完全对齐,并修复了若干问题:
This update brings all four builds (Fabric / Forge / NeoForge) to feature parity, along with several fixes:
新功能 / New features:
- 新增「游戏日设置」:可设置游戏日与季节从第 0 天还是第 1 天开始计数,修改后 HUD 立即刷新。
New "Game Day Settings": choose whether game days and seasons count from day 0 or day 1; the HUD refreshes instantly after changes. - 计数器升级为物品 + NBT 双模式:可按 NBT 标签(支持点分隔路径)累加数值,也可直接显示玩家属性(生命值、饥饿度、等级等);物品图标现在可以隐藏。
The counter now supports item + NBT modes: sum values by NBT tag (dot-separated paths supported), or display player stats (health, food level, XP level, etc.); the item icon can now be hidden. - 货币统计增强:铜/银/金币自动折算总铜币(1:9:81),支持钱袋内钱币递归统计、KubeJS 硬币与 SDM Shop 电子货币。
Enhanced money counting: automatic copper/silver/gold conversion (1:9:81), recursive counting inside Money Pouches, plus KubeJS coin and SDM Shop balance support. - 深度适配 Serene Seasons:安装后直接读取其季节数据并显示季节剩余天数。
Deep Serene Seasons integration: reads its season data directly and shows remaining days in the season. - 新增调试日志开关(默认关闭),日志不再刷屏。
New debug logging toggle (off by default) — no more log spam. - Forge / NeoForge 配置界面重新设计为四个分页(通用 / 游戏日设置 / 可见性 / 计数器),并加入页码指示与保存提示。
The Forge / NeoForge config screen is redesigned into four tabs (General / Game Day / Visibility / Counter), with a page indicator and save notifications.
修复 / Fixes:
- 修复按 F1 隐藏界面后 HUD 仍然显示的问题(NeoForge)。
Fixed the HUD staying visible after hiding the GUI with F1 (NeoForge). - 修复季节图标可能不刷新的问题。
Fixed season icons occasionally failing to refresh. - 修复 KubeJS 硬币未统计钱袋内数量的问题。
Fixed KubeJS coins inside pouches not being counted.
注:每日运势(Every Single Day)联动目前仅在 Fabric 版本可用,Forge / NeoForge 版本的联动将在后续更新中补齐。
Note: Every Single Day fortune integration is currently available on Fabric only; Forge / NeoForge integration will arrive in a future update.
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:hvnOGUOZ:2hAszMSZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hvnOGUOZ:2hAszMSZ"
}

