All versions
1.3.7+26.2
Release
DayTime Counter 1.3.7+26.22 weeks ago 19
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
1.3.7+26.2
The biggest update to Vanilla DayTime Counter so far. 1.3.6 was compatibility-only (Minecraft 26.2 support, no new features) ā everything below is new since then.
Added
- World Journal, opened from the pause menu:
- Custom era names per dimension (Overworld/Nether/End)
- Automatic milestones: first Nether visit, first End visit, Ender Dragon defeated, one full year survived ā estimated retroactively if you'd already reached one before installing the mod
- Your own manual notes, tied to the current in-game day, with the journal always opening on today's page
- Materials collected, tracked per day ā items you only dropped and picked back up, or that followed you through a game mode switch, aren't double-counted
- Each world/server keeps its own separate journal
- Day/night HUD icon: dawn, day, sunset, dusk, or night, following the actual in-game time
- Multicolor progress bar option, tinting the day bar to match the time of day
- Compass direction indicator in the HUD label when holding a compass
- Public API for other Fabric mods: read the current day/time/era, subscribe to day-change/journal/material-collected events, and log custom journal entries. See "For developers" on this page.
Fixed
- The milestone sound and the sleep-time toast could silently fail to trigger after switching to a different world or server without restarting the game, if the new day happened to match a day number already used in the previous session.
Changed
- Bumped bundled Fabric API and Mod Menu reference versions.
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:VxRePyV1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DinbWefJ:VxRePyV1"
}

