so, lots of servers have view distance limits, and I figured out one way to get around it is to simply keep the chunks you've already been sent cached and visible but not updating till you get new ones from the server.
If a server adopted this, it could reduce the view to about 5 chunks, allowing hundreds more on a single server. The cached chunks won't update, but you'll be able to see them in the distance, and the chance of someone randomly building a house between you going fishing and returning to your area is pretty small. It may put some strain on your client, but shouldn't be worse than hosting a server for some friends, or setting the render distance to extreme on optifine.
I know it's very possible to do, I'm just bad at networking code. Surely in 5 years I can't be the first to think this up?
so, lots of servers have view distance limits, and I figured out one way to get around it is to simply keep the chunks you've already been sent cached and visible but not updating till you get new ones from the server.
If a server adopted this, it could reduce the view to about 5 chunks, allowing hundreds more on a single server. The cached chunks won't update, but you'll be able to see them in the distance, and the chance of someone randomly building a house between you going fishing and returning to your area is pretty small. It may put some strain on your client, but shouldn't be worse than hosting a server for some friends, or setting the render distance to extreme on optifine.
I know it's very possible to do, I'm just bad at networking code. Surely in 5 years I can't be the first to think this up?