You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've talked about this on Discord before: the ability to configure a custom "render distance" per wizard.
However, doing so would require modifying the current system for adding players as watchers of a wizard, which may be challenging and potentially disrupt the current, reliable method of using vanilla Minecraft's code to manage this process.
Despite these potential obstacles, the benefits of this feature warrant further consideration, as some of my players are reporting seeing things beyond their local render distance 😅
Just call them extremely visible chairs™ and make it a feature. I agree that moving away from vanilla's system might be a good idea. Also opens up more options for culling and stuff. There's some work done already for moving wizards off-thread, so those will combine well. I believe Paper (or some fork, idk) optimizes the entity tracking system as well so we should be able to get a decently performant solution by adapting some of that.
I believe the current system will send the entity once the chunk is sent to the client. I don't know why the entities show for this person. Might be related to their entity distance? I've got no clue how the client determines if an entity is visible tbh
We've talked about this on Discord before: the ability to configure a custom "render distance" per wizard.
However, doing so would require modifying the current system for adding players as watchers of a wizard, which may be challenging and potentially disrupt the current, reliable method of using vanilla Minecraft's code to manage this process.
Despite these potential obstacles, the benefits of this feature warrant further consideration, as some of my players are reporting seeing things beyond their local render distance 😅
Minecraft__1.19.1_-_Multiplayer_3rd-party_Server_2022-12-10_14-48-28-resized.mp4
The text was updated successfully, but these errors were encountered: