1.4.3+26.1
Compatibility
Changes
1.4.3
This release is about playing nicely with other mods' HUD elements, plus another batch of public API for developers building on top of this mod.
Added
- HUD Position โ "Extra top clearance": a new setting (Off / +20px / +40px / +60px) that adds extra space above this mod's HUD block for the "top" position presets โ a manual fallback for the rare mod that draws its own top-of-screen bar (a custom boss bar, a level/progress bar on a OneBlock-style map, ...) through a channel this mod's automatic avoidance can't see. It stacks on top of that automatic avoidance rather than replacing it.
recordCustomCounter(Identifier)/recordCustomCounter(Identifier, int)andgetCustomCounterCount(Identifier)/getCustomCounterCount(Identifier, long day): other mods can now track their own named counters (anything the built-in death/raid/trade/advancement counters don't cover) through this mod's journal, the same as those built-in ones โ a world/server total or scoped to a single in-game day.DayTimeEvents.DAY_MILESTONE_REACHED: fires the first time each in-game day this mod treats as a milestone is reached (day 50, day 365, and every multiple of 100 after that, with no upper bound) โ the same day set that drives this mod's own HUD celebration and milestone sound, now something a third-party mod can hook into directly instead of re-deriving it.getHudBlockBounds()/HudBlockBounds: returns where this mod's own day/time HUD block is currently drawn on screen (position, size, whether it's showing anything at all), so another mod can position its own independently-rendered HUD content anchored to it โ or deliberately clear of it โ instead of hardcoding a screen position that might collide.- Hardcore run recap: on a hardcore world's final death, a dedicated "You survived N days" screen now appears in front of the usual death screen, with a short recap pulled from this mod's own World Journal (dimension era names, first Nether/End, the Dragon, raids/trades/ advancements) and a shortcut straight into the full journal. A "Continue" button hands off to the normal death screen exactly as before โ nothing about vanilla's own exit-to-title flow is touched. Has its own on/off toggle in settings (Info & Alerts).
- Day display format: a new HUD setting groups the day counter into weeks, months, or years ("Week 36 ยท Day 1", "Month 9 ยท Week 4 ยท Day 1", ...) instead of the plain running count, purely as a different way to read the same number โ with a second toggle choosing whether the smallest shown unit resets each period or keeps counting up alongside the bigger label. Everything this mod tracks internally (journal entries, milestones, the API's current day) still uses the plain absolute day count; only this HUD text changes. The unit order follows what reads naturally in each language โ English lists largest-to-smallest ("Year 1 ยท Month 9 ยท Week 4 ยท Day 1"), Italian lists smallest-to-largest ("Giorno 1 ยท Settimana 4 ยท Mese 9 ยท Anno 1") โ rather than forcing one fixed order translated word-for-word.
See "For developers" on this page for the full reference (method signatures, DTO fields, namespacing rules, threading notes).
Fixed / Clarified
- Confirmed and documented: this mod's existing boss-bar avoidance (the shrink-and-duck behavior
for the "top center" HUD position) already reacts to any boss bar shown through vanilla's own
boss bar system โ dragon, wither, a raid, or a server/datapack's own
/bossbarcommand โ which covers most OneBlock-style maps, since their "Level: X" bar is typically implemented exactly that way. No code change was needed for that case; the "Extra top clearance" setting above covers the remaining case of a mod that draws its own bar outside that shared channel.
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:DinbWefJ:M02n2qwe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DinbWefJ:M02n2qwe"
}

