Tags
Creators
Details
2.10.2
Compatibility
Changes
DecentHolograms 2.10.2
Summary: DecentHolograms now runs on Folia and supports 26.3. Placeholders inside display attributes no longer freeze, and skin lookups have stopped filling your console.
New & Improved
- Added support for Minecraft 26.3
- Added support for Folia
- Dev builds are available from GitHub Actions
- Removed the old, unused reflection-based NMS code
- Updated
item-nbt-api, which no longer warns about an unsupported version on 26.2 - Updated some other dependencies
Fixes
- Legacy color and formatting codes are applied on 1.16 again (Thanks Kepchyk1101)
- Placeholders inside display attributes keep updating, instead of being stuck on the value they had when the display was first shown
- Skins of players that don't exist are no longer looked up over and over, or reported as errors
- Skins are no longer requested for names that can't be valid usernames
- Requests that Mojang rejects outright are no longer retried, while rate limits and timeouts still are
- Materials that the bundled XSeries doesn't know yet no longer cause errors on newer Minecraft versions
- Damage and Healing displays no longer show in all worlds
/dh d nearbyno longer fails when there are displays in other worlds/dh h teleportnow tells you when the hologram's world isn't loaded, instead of erroring/dh h linesno longer errors when run from the console on a hologram with multiple pages/dh h renameno longer shows the usage message after saying the new name is already taken/dh convert <plugin> [file]now uses the file you give it, instead of ignoring it- Tab completion for
#ICON:,#HEAD:,#SMALLHEAD:and#ENTITY:content in/dh page insertworks again - The bundled Configurate library is now relocated, like the rest of the bundled libraries
- The
/dh profiler helpcommand now uses thedh.command.profiler.helppermission instead ofdh.profiler.command.help. This only affects you if you granted the old node directly —dh.adminanddh.command.profilerworked either way
For developers
- DecentHolograms is now published as a single, self-contained artifact (
com.github.decentsoftware-eu:decentholograms) — no extra CodeMC repository needed, and a sources jar is published alongside it
Found a bug or a mistake? Report it on our Discord.
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:w02MKsTg:fbE7wARc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w02MKsTg:fbE7wARc"
}

