[Suggestion] A setting for the range of Inaccessible chunks around a player that get networked to them that is separate from the server's view-distance
Kenajcrap opened this issue ยท 5 comments
This would probably require some pretty heavy trickery with chunk tickets, so I don't expect it to actually be a thing, but being able to set so the player can see a larger section of the world without having to fly around, while not affecting the default chunkloading behavour would be a pretty cool feature, if you have the spare server performance to splurge.
From my understanding, the way this is set up is that world generation happens until the first strip of Inaccessible chunks. So having an option to increase this range, or even just network to the player chunks further than that that have already been generated before would be amazing for small or private vanilla servers that run a surplus of performance.
Thanks for developing this project, I like it a lot.
Check https://github.com/QuiltServerTools/TickTools for literally this if I understood correctly.
well, if you have a server with lots of performance, you can tweak view distance on the server with carpet already, and then increase it on your client - on the fly. I don't thing any trickery in sending some chunks to the clients is needed at this point. Maybe that can be done already with scarpet API - it can create chunk tickets as well as update chunk data to the client, not sure though how the client would react on that (for chunks outside of the view area)
well, if you have a server with lots of performance, you can tweak view distance on the server with carpet already, and then increase it on your client - on the fly. I don't thing any trickery in sending some chunks to the clients is needed at this point. Maybe that can be done already with scarpet API - it can create chunk tickets as well as update chunk data to the client, not sure though how the client would react on that (for chunks outside of the view area)
Thank you for the response gnembon! I don't think I explained myself clearly:
What I'm talking about is a way to increase the amount of terrain that gets sent to the players without having to change the server's view distance, since according to the wiki, changing the server view distance would increase the range of entity ticking and redstone ticking chunks around each player, changing the behavior of farms and stuff like that. Which would be unwanted for a lot of players wanting an experience as close to vanilla as possible
So this setting would consist, ideally, not of forced tickets (which would set the chunk's load level to 31) but of somehow forcing a higher load level of 34 in chunks further away around the player, so in those chunks entities and redstone would not be ticked, and they would simply serve as eye candy without actually affecting the gamestate.
For example: given this is the state of the chunks around a player:
Increasing this setting would do this:
While increasing the server's view distance does this:
Moreover I also think this would be a popular enough feature to be included as a setting in the base Fabric Carpet, although I can't corroborate this data or anything because I don't think something like this has come up before, but I still think people would like and use this a lot.
I will try and implement this with the scarpet API eventually, at least as a proof of concept.
Thank you again for your work.
Hm... I think your use-case could be solved by installing the (client-side) Bobby mod, which keeps a radius greater than the one the server loads and sends (and saves it so if it still hasn't been sent this session, you also render it), essentially doing what you want without touching (server-side) chunkloading nor overloading the server or network.
Also I think someone was making a no-tick-viewdistance server-side mod for Fabric, not sure how well does it work at the moment.