I can't see the holograms
Tanerx opened this issue ยท 4 comments
Confirmation
- I have read the FAQ.
- I have tested the latest development build of Holographic Displays and the bug is still present.
- I have updated Spigot to the latest release for my particular Minecraft version.
- I made sure the bug hasn't already been reported on the issue tracker.
Description
Creating hologram is working fine with Build #232 (Sat Oct 01 20:32:16 UTC 2022) Starting with Build #233 and all after builds i can't see any hologram in game even stable release of 3.0.0. This for 1.18.2 server. Created holograms with 3.0.0 can't see until i downgrade the plugin Build #232
For 1.19.3 server I used latest dev build 3.0.1 same issue.
How to reproduce
Create any in game hologram
/hd create example &7&lColor test&r: &uRainbow
Server version
Paper version git-Paper-375 (MC: 1.19.3) (Implementing API version 1.19.3-R0.1-SNAPSHOT) (Git: 7a64b85)
Holographic Displays version
HolographicDisplays version 3.0.1-SNAPSHOT-b244
Installed plugins that allow players to join with multiple Minecraft versions
Plugins (3): HolographicDisplays, ProtocolLib, Vault
Additional information
When testing 1.19.3 server i used unmodded 1.19.3 client.
Full 1.19.3 server log if you need https://pastebin.com/p0WvZ0nN
Found the problem. If view-distance is set 0 and using only simulation-distance 5, after Build 232 we can't see the holograms anymore. If i set view-distance=5 and simulation-distance=5 in settings, server view is still 5 chunks working fine. I thing this should be added to FAQ
Wait, why would you set view distance to 0? View distance should be greater or equal to simulation distance. Is there a legit use for that? I might not be aware.
Wait, why would you set view distance to 0? View distance should be greater or equal to simulation distance. Is there a legit use for that? I might not be aware.
Custom game with a adventure mode server. Ticking chunks doesn't need in this situation. Almost no server would ever need to do this anyway. It's a rare event.
@Tanerx ok I think I can close this then. Thank for finding the cause.