Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 years ago
Updated last week
All versions
2.10.0
Beta
DecentHolograms 2.10.0 [EXPERIMENTAL]6 months ago 16.5K
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platforms
Paper
Spigot
Changes
Changes in Version 2.10.0 [EXPERIMENTAL]
Notes:
- This release is marked as experimental. It is safe to use on your server, but unexpected bugs or version-specific quirks may still occur.
- If you encounter any issues (displays not working properly, errors, visual glitches, etc.), please report them on our Discord server so we can fix them quickly.
- Feedback is highly appreciated and helps improve Displays faster.
- More information about this update can be found in Discord announcements.
New Features / Improvements:
- Added Displays: a brand new hologram type alongside classic Armor Stand holograms, configurable with
/dh display ...- Powered by Minecraft display entities (1.19.4+)
- Supports text, item, and block displays
- Includes customizable attributes such as:
- background color
- glow color
- scale
- rotation
- billboard mode
- translation
- brightness
- opacity
- alignment
- skull textures
- and more
- Supports animations for selected attributes
- Uses a custom data-driven attribute system configurable with
/dh display attribute ... - Includes configurable defaults via
attribute-defaults.yml - Includes full tab completion support
- Includes major rendering and performance optimizations:
- custom text parsing (~26× faster than Bukkit)
- designed to have near-zero impact on normal setups
- Uses canonical Minecraft material IDs (
minecraft:stone, etc.)
Have you found any bugs or mistakes? Please, report them on our Discord server.
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:nGwsH27P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w02MKsTg:nGwsH27P"
}

