1.0.0
Compatibility
Changes
Day Counter
Day Counter** is a clean and lightweight Fabric mod that adds a simple day counter to your Minecraft HUD.
Instead of opening the F3 debug screen just to check the current day, this mod displays the day directly on your screen in a clean format like:
Day: 01
This is useful for survival players, hardcore worlds, Minecraft 100 Days challenges, multiplayer SMPs, content creators, and anyone who wants an easy way to track world progress.
Features
-
Shows the current Minecraft day on your HUD
-
Clean display format: Day: 01
-
Works in singleplayer and multiplayer when installed on the client
-
Perfect for Hardcore, Survival, SMP, and 100 Days challenges
-
Press K to cycle the HUD position
-
Supports multiple screen positions:
- Top Left
- Top Center
- Top Right
- Center Left
- Center
- Center Right
- Bottom Left
- Bottom Center
- Bottom Right
-
Optional HUD toggle key through Minecraft Controls
-
Config file support for changing text, color, margin, shadow, background, and position
-
Lightweight and simple, with no unnecessary extra features
Config
After launching the game once, the config file will be created here:
.minecraft/config/sg-day-counter.json
You can edit options like:
- Enable or disable the HUD
- Change the position
- Change the prefix text
- Change minimum digits
- Change text color
- Enable or disable shadow
- Enable or disable background
- Adjust margins
Controls
Default key:
K — Cycle HUD position
The toggle key is available in Minecraft keybind settings but is unbound by default. You can set it from:
Options → Controls → Key Binds → SG Day Counter
Recommended For
- Minecraft Survival
- Hardcore Minecraft
- 100 Days Challenges
- SMP gameplay
- YouTube recordings
- Live streams
- Players who want a clean day counter without using F3
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:3SWIStG5:QlzGTgcm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3SWIStG5:QlzGTgcm"
}
