[MC-149714] Client no longer keeps chunks loaded beyond server render distance

My server's render distance is set to 8.
My client's render distance is set to 32.

In 1.13.2, the client kept chunks loaded even if they were beyond the server's render distance, up until they were beyond the client's render distance.
In 1.14.0, the chunks disappear at a distance of just 8, despite the higher client setting. In singleplayer I can still view up to 32 chunks, so it's specifically multiplayer this affects.

Attached below are screenshots of:

The 8-chunk distance I can see of my base when first logging in (which I would expect, unless you want to start caching chunks between logins).
The 32-chunk distance I could see from my friend's base after walking there, with the roof of my house visible in the distance fog.
The 8-chunk distance I can now see from the same vantage point. Can't even see the intermediary base anymore. 😞 The screenshot is taken from chunk 2,6,8 and the torch on the horizon is right on the edge of -6,4,10; so it's definitely 8 chunks and not some other value.

I'm hoping this isn't an intentional change, as I really enjoyed being able to see a long way, without my low-powered server having to generate a 32-chunk radius or send a 32-chunk radius to my friends over my slow home internet.

Related issues

is duplicated by

MC-151697 Chunks Not Loading Properly On Realms

MC-157624 Minecraft 1.14 chunks loading slow on servers

MC-232781 Realms server render distance capping local render distance

relates to

MC-159361 Chunks near the edge of view distance aren't sent to client after movement

Attachments

Actual 8-chunk render distance after walking to friend's base.png

Expected 32-chunk render distance after walking to friend's base.png

Expected 32-chunk render distance after walking to friend's base (with F3).png

Expected 8-chunk render distance after login.png

Comments

migrated 2019-04-25T22:14:31Z

[media][media][media][media]

violine1101 2019-04-25T22:15:35Z

As far as I know, this is an Optifine feature. Are you sure you tested this in 1.13.2 without any mods?

Road_hog123 2019-04-26T00:06:04Z

All pure Vanilla 1.13.2, no optifine:

[media]

migrated 2019-05-13T18:56:41Z

Confirmed affects 1.14.1

migrated 2019-05-28T01:19:51Z

Continues to affect the game in version 1.14.2

migrated 2019-07-11T12:34:21Z

This is still an issue in 1.14.3

migrated 2019-07-31T03:03:06Z

still an issue in 1.14.4 (on realms)

migrated 2019-09-24T15:48:34Z

Still isusue.

migrated 2020-01-07T06:49:35Z

confirmed this affects 1.15.1 as well

migrated 2020-04-08T02:34:58Z

Confirmed for 1.15.2. I urge Mojang to take a look at this report when their schedule allows. Not only is this bug a deviation from pre-1.13 behavior, it degrades the quality of the game for players that play on low render distance servers.

j_p_smith 2020-06-09T02:28:18Z

Related to MC-54545.

migrated 2020-06-24T19:03:51Z

Confirmed still an issue for 1.16.1.

migrated 2020-10-31T16:41:45Z

Still an issue in 1.16.3. It would be awesome to be able to set the range of chunks that are cached client-side, which are updated when the player is within server render distance of those chunks. This would greatly improve immersion in multiplayer where you are often limited by the server's capabilities. Especially so when a player's local machine could handle (far) more chunks (e.g. 32 render distance).

migrated 2021-09-20T22:16:04Z

Why is this marked as "Works as intended"? What exactly was wrong with caching multiplayer chunks on the client side if the client's hardware and render distance was good enough to allow it? What's the point of having vast new terrain generation in 1.17 if the server(s) you're playing on can't handle a render distance beyond 10 because render distance and simulation distance aren't detached in any way.

This actively makes game worse, and as an earlier commenter noted "it degrades the quality of the game for players that play on low render distance servers."