Tags
Creators
Details
All versions
3.0
Release
The Real Full Release - Version 3.0last year 130
Compatibility
Minecraft: Java Edition
1.21.5
Platform
Data Pack
Changes
⚠️ Disclaimer
This version has two known major issues and one known minor issue:
- Nether portals only save the initial entrance point.
- Updating from an old version does not immediately remove the old bossbar — players must run
/function dash.date:updateonce after updating. - Minor issue: Extra bossbars may appear if a player changes their username.
Fixes for all of these are in progress.
Changelog
[3.0] - 🎉 Major Overhaul 🎉
✨ New Features & Improvements
- 🆕 Per-Player Bossbars: Switched from a single global bar to individual
dash.date_$(bossbar_id)bars—unlocking all the powerful new display logic below. - 🕹️ Bossbar Toggle: Sneak-looking down while holding a clock will hide your personal bossbar.
- 🌋 Unique Nether Display: In the Nether, see your current XYZ coords, distance from your entrance portal, and the Day Count—all in one neat bossbar.
- 🪐 Dynamic End Display: In the End, view your coords + Day Count by default. If you’re wearing an Elytra, it auto-switches to show remaining flight time (in seconds)!
- 🌧️ Accurate Weather: Condition checks are now per-player—so you’ll get real-time snow, rain, or overcast indicators even on busy multiplayer servers.
- 🧹 Rock-Solid Uninstall: The
uninstallfunction now wipes every bossbar, tag, storage entry, and scoreboard objective—leaving zero trace of the datapack. - 🔌 Addon Compatibility: Fully namespaced
dash.date/tags/functionhooks (e.g.day_change,valentines) and an installation flag (dash.date_installed) enable seamless integration with official or third-party addons.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| rp.dash_dt_display_V1.0.zip | Required resource pack | 227.82 KiB |
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:Z5Qum2EN:mrcjNaRL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z5Qum2EN:mrcjNaRL"
}

