Matt Clarke (The Hive)
Assigned
Reported
Comments
This is feature of The Hive at the moment. Due to some issues with performance in players with high we only show a small % of players in the hub, to help improve your FPS. If you wish to turn this off you may use the command /toggleperformance (on The Hive server only), and you'll see all hub players again.
Hi Creepergirl. This is feature of The Hive at the moment. Due to some issues with performance in players with high we only show a small % of players in the hub, to help improve your FPS. If you wish to turn this off you may use the command /toggleperformance (on The Hive server only), and you'll see all hub players again.
Jira mods, you may close this as it's not a client issue 🙂
This is caused by a client bug that is marked as resolved in 1.14. In the mean time, you can use the command /fixpurchase (only on The Hive server) and we'll resync your purchases. If issues still continue please feel free to reach out to The Hive support - [email protected]
Hi Jordy, and others. Hive developer here. This is due to a client bug that was introduced in 1.13 causing the client to not inform us (The Hive) of your purchase. You should automatically get your items on the next login, or you may type the command /fixpurchase. This issue has already been fixed by Minecraft in 1.14.
This is still very much a problem and very easy to reproduce. To reproduce, join a LAN server with a friend, ask them to get into a boat, walk far enough away so the entities are despawned in the client, then move back into visible range - you'll see the passenger in a fixed position with the boat moving and only the passengers head updating.
The issue lies in chunk sending, it appears the server sends the entity spawn packets correctly, but the server does not send the PacketPlayOutMount correctly (it never gets sent, it's only sent when you are within the entity-range when the passenger is set/vehicle is mounted).
Would love to see this fixed. 🙂
Hive developer here.
The glitch is a memory-related issue, specifically with how player skins are handled. Seemingly, the client doesn't release player skins from memory when it is no longer needed. This leads me to assume that this results in the clients texture atlas/memory being exhausted, resulting in RenderDragon being unable to load/assign new textures.