3.0.0+mc26.3
Compatibility
Changes
Settings from 2.x are not carried over: config/day-counter.json is
rewritten with the defaults on first launch.
Added
- One jar for Minecraft 26.1, 26.1.1, 26.1.2, 26.2 and 26.3.
- Always-visible mode, in one of six screen positions, hidden while the debug screen is open. Pixel offsets can be set in the config file.
/daycounteropens the settings screen. It runs on the client, so it works on any server.- Colors for the Dappled Forest and Sulfur Caves biomes.
- Biomes from other mods are added to the settings the first time a world that has them is joined, with the color of their foliage as default.
Changed
- The settings screen uses Minecraft's own option widgets. The label and the number
each follow the biome, or use a custom
#RRGGBBcolor, white by default. Biome colors have their own screen, grouped by dimension, with each default shown; clearing a field restores it. - Colors are stored as
#RRGGBBstrings. - The label is a single text field,
Dayby default; left empty, only the number is shown. The settings screen is translated into English and French. - The counter is drawn as its own overlay instead of through the action bar, which
item names, jukeboxes and
/titlewould overwrite. - The typing sound plays as an interface sound and skips spaces.
- The world clock is read once a second and the biome twice a second, instead of on every tick and every frame.
- New icon: a sunrise over the counter.
- Licensed under the GNU Affero General Public License v3.0 only, instead of the 02Alexis Protective License.
Removed
- Fabric API and Yet Another Config Lib are no longer required; only the Fabric loader is.
- The settings key binding, replaced by
/daycounter. - Milestone effects at 100, 1,000 and 10,000 days.
- The translations of the word "Day": the label is now plain text.
- Background transparency for the always-visible counter.
One jar for Minecraft 26.1, 26.1.1, 26.1.2, 26.2 and 26.3, on the Fabric loader 0.19.3 or later.
Optional dependencies
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:gZOTEPbp:omDUptIO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gZOTEPbp:omDUptIO"
}

