1.1.0
Compatibility
Changes
1.0.0 Now Unsupportable! The Next-Gen Hologram Update (v1.1.0) 🚀
This major release fundamentally changes how EasyHologram operates under the hood. Due to massive architectural improvements and API overhauls, version 1.0.0 is officially obsolete. All users are strongly advised to update to 1.1.0 immediately.
✨ What's New?
- 🖱️ Interactive Holograms Holograms are no longer just visual! You can now attach functional left/right ClickListener events to run code when a player punches or interacts with a hologram box.
- 🔄 PlaceholderAPI Integration
Complete native integration with PlaceholderAPI (
%player_name%,%server_online%). Placeholders update synchronously on the main thread via our newupdateIntervalsystem. - 📝 Multi-Line Arrays Introduced the MultiLineHologram wrapper class. You can now easily spawn, array, and customize vertically stacked text lines perfectly spaced along the Y-axis.
- 👁️ Per-Player Visibility
True conditional visibility tracking! Use
hologram.addViewer()to conditionally render specific holograms only for targeted players. Network packets are cleanly intercepted and dropped to unauthorized clients. - 🎬 Buttery-Smooth Interpolation Unlocked the vanilla 1.21 matrix interpolation limits. Modifying scales, XYZ translations, and rotational offsets now visually transitions smoothly rather than instantly teleporting.
💻 Administrator Tools
- Live Editor Command: Added the
/hologram edit <id> settext <text>command explicitly requested by server admins. You can now mutate text layouts in-game instantly without needing to destroy and recreate the geometry.
🛠️ Technical Fixes
- Safe Dependencies: Redesigned the
PlaceholderAPIdependency tracking. The library now securely verifies if the mod is present at runtime, preventing hard server crashes on environments without it. - Matrix Optimization: Minor NBT tracking optimizations and bounding box size injections for interaction scaling.
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:tiaSrKkc:b1FPASna"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tiaSrKkc:b1FPASna"
}

