PerformanceX

v1.1.84 — FancyHolograms Backend + Display Performance

FancyHolograms integration as a rendering backend If you have FancyHolograms installed, /px display now delegates all hologram rendering to it instead of spawning its own ArmorStand or TextDisplay entities. FancyHolograms handles everything — chunk load/unload, visibility distance, TextDisplay fallback — so you get its rendering quality for free with zero extra config.

To disable and revert to the built-in renderer, set perf_display_backend: false in plugins/PerformanceX/integrations/fancyholograms.yml.

Performance: dirty-checking on display updates Previously, every update tick would dispatch a runAtRegion task and call updateLabel/refreshForViewers for every hologram even if TPS, MSPT, RAM, and player count hadn't changed. On a stable server that was a lot of unnecessary scheduling overhead per second.

Now the update is skipped entirely if the rendered text is identical to the last update. On a stable server this means near-zero entity update calls between actual metric changes — a significant reduction in per-tick overhead, especially with multiple holograms placed.

Architecture note All FancyHolograms API calls are isolated inside FancyHologramsIntegration — the display module never touches FH classes directly. This means: no hard dependency, the plugin loads fine without FancyHolograms, and if FH spawn fails for any reason it automatically falls back to the NMS renderer.