0.1.3
Compatibility
Changes
# HoloBuilder 0.1.2
Large schematic display fix.
I forgot to remove a block display limit that was left over from the test version, which could make large schematics look incomplete after loading.
Fixed
- Removed the leftover test display limit from hologram rendering.
- Visible blocks are now selected by render distance instead of by their order in the schematic file.
- Improved rendering performance for very large schematics by using a spatial block index and rendering the nearest visible blocks first.
- Fixed a client crash that could happen when rendering outlines for very large schematics.
- Export now fails with a clear message if the selection contains chunks that are not loaded client-side, instead of silently exporting those areas as air.
Changed
- New exports now use the player's position as the placement reference, so reloading them keeps the schematic offset relative to the player reference point.
Notes
- Export is still client-side only.
- On multiplayer, HoloBuilder can only export chunks that are loaded by the client.
- If the export reports unloaded chunks, move closer, increase render distance, or export a smaller area.
HoloBuilder 0.1.3
Hologram rendering optimization update.
Fixed
- Reduced lag spikes while a hologram is visible by caching world/schematic comparisons for a few ticks instead of recomputing them every rendered frame.
- The HoloBuilder render distance cap is now actually applied; high Minecraft render-distance settings no longer force holograms to scan and render too far away.
- Cached Minecraft block-state conversions and parsed expected block states to reduce per-frame allocations during hologram rendering.
Notes
- Hologram block status can now update with a very small delay after world changes, which is the tradeoff that keeps rendering smoother.
- The mod remains client-side only.
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:k9maSaFI:opEuZ7k5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k9maSaFI:opEuZ7k5"
}

