Thread title:
Loaded Chunks Beyond Server Render Distance Not Kept Client Side

Minecraft Username:
Volvith

Description:
So, something that i noticed upon coming back from a ~3 month leave is that chunks that have been loaded server-side, are no longer kept client side after leaving the server-side render limit.
This behaviour that appears to now be bugged/missing, previously enabled you to for instance, an 8x8 chunk area, while the server would be set to 2x2.
The chunks wouldn't be active, and would essentially be static visual relics, but not having access to them anymore makes the main server feel extremely confined, and flying around, especially in mining, is extremely disorienting without them.

Is this a change implemented by ECC, and if yes, how much do i have to pay you to undo that change?

 

Yeah, that's actually a pretty large deal-breaker for a lot of server-content for me.
I sincerely hope nobody is stupid enough to consciously implement a bug like this.

 

Oh well, can't say i expected much else from 1.14, but thanks for trying anyways. :)
Let's hope that 1.15 is a bit more forgiving.

 

I will, thanks.

 

Sorry for the late reply, took a bit of a leave there.
I'm currently still experiencing the issue where chunks are immediately unloaded the second they cross the 4-chunk radius.
If you are not experiencing the same issue, i might try to re-install the Minecraft launcher entirely to see if that has any effect. (I highly doubt it but perhaps the issue lies in a configuration file?)

EDIT: Issue persists after a full re-install of the launcher, by means of uninstalling the program and manually deleting any left-over folders (.minecraft in roaming).
At this point, if you're not experiencing it anymore, i'm unsure as to what the cause might be...
Version used for testing is 1.15.1.

 

I think you might be right here: https://bugs.mojang.com/browse/MC-149714
Status is not yet officially confirmed by Mojang, nor shot down for being an intended change.
I highly doubt this is an intended change due to the fact that Nathan Adams, technical director at Mojang, has viewed/edited this page at least once halfway through last year.
Personally i think that right now, the priority to fix something like this is probably non-existant, if they'll ever plan on fixing it at all with the current amount of people complaining about it.

Still, @andrewkm you said you were not experiencing this issue, if that's still correct i wonder how.
Maybe something related to configuration/jvm arguments after all?[/user]