1.4.0+26.2
Compatibility
Changes
1.4.0
This release bundles everything since 1.3.7 in one go ā the World Journal storage fix and
/journal commands were finished but never actually published as their own release, so this is
the first version where all of it reaches players.
Added
- Custom HUD position: 9 presets (top/middle/bottom Ć left/center/right) instead of just top/bottom, from the settings screen.
- Automatic boss bar avoidance: with the top-center preset, if a vanilla boss bar shows up ā
an Ender Dragon or Wither fight, a raid, or a server's own custom
/bossbarā the counter smoothly shrinks a little and slides below it, then returns to its normal spot once the boss bar clears. No manual repositioning needed. - A "World Journal" title logo above the day heading in the book screen, on every page where a new day begins.
- New automatic World Journal milestones:
- Every death (not just the first), with the very first one still called out specially
- Every raid you defend or lose
- Every villager trade, with what you received
- Every advancement you complete
- Milestone sound settings: turn the notable-day sound off, or pick which sound plays, from the Mod Menu settings screen.
/journalcommands:/journal add <text>ā logs a manual entry on the current in-game day, without opening the book screen/journal removeday <day>ā shows how many entries exist for that day; running/journal removeday <day> confirmdeletes all of them/journal clearā shows a warning about what's about to happen; running/journal clear confirmpermanently wipes the current world's entire journal
- New public API (
dev.notesow.vanilladaytimecounter.api.v1) for other Fabric mods:getDeathCount()/getDeathCount(long day)getRaidCount()/getRaidCount(long day), plusgetRaids()/getRaids(long day)for which ones were won vs. lostgetTradeCount()/getTradeCount(long day)andgetTrades()/getTrades(long day)for what was receivedgetAdvancementCount()/getAdvancementCount(long day)andgetCompletedAdvancements()/getCompletedAdvancements(long day)for which ones- Each counter comes both as a world/server total and scoped to a single in-game day
- New
JOURNAL_DAY_REMOVED/JOURNAL_CLEAREDevents, so a mod tracking journal data is notified when/journal removeday//journal clearwipes it, instead of being left with stale cached state - New DTOs
TradeRecord,AdvancementRecord, andRaidRecord, alongside the existingJournalEntry
See "For developers" on this page for the full reference (method signatures, DTO fields, namespacing rules, threading notes).
Fixed
- World Journal entries mixing between different worlds (major bug). On this Minecraft
version, the way the game reports a singleplayer world's own save folder could resolve to the
same generic path for every world instead of that world's actual folder. As a result, every
singleplayer world ended up sharing one single journal file instead of getting its own ā so a
brand-new world could show deaths, trades, advancements or notes that actually happened in a
completely different world, and deleting a world and creating a new one with the same name
could resurrect the deleted world's entries.
- Each world's journal is now tied to its own save folder through a small hidden marker file stored inside that folder, completely independent of the folder's name ā this can't reoccur, even if you reuse an old world's name.
- If you had already been affected, opening the singleplayer world list now shows a one-time recovery screen (it keeps appearing until you act on it) offering two choices: delete the old shared file and let every world start with a clean journal, or pick which of your worlds should receive the old file's recovered entries.
- Minecraft 26.1 compatibility: the 26.1 jar previously declared it needed Fabric Loader
0.19.3+, a version that isn't available on 26.1, so the mod failed to load there with an "incompatible mods" error. Fixed ā download the jar matching your Minecraft version.
Changed
- Rebuilt the mod's own build system on Gradle + Fabric Loom, compiling against real Minecraft/ Fabric API jars instead of hand-written approximations of them. No effect on the mod itself ā called out here only because it's the reason this release took a version bump on its own even though most of the content above was already finished earlier.
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:jpbIWAdU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DinbWefJ:jpbIWAdU"
}

