Chunks not being sent to client under some scenarios.

[slidedrum]

I believe this may be the same issue as others have reported, but I have no idea as they didn't provide much information. But I have found some consistent repro steps! The issue seems to be related to dynamic render distance. Possibly tick distance as well, but I have not tested that yet.

• Join the server
• Wait for view distance to get to max,
• Then leave the server.
• And rejoin while the server is still at max render distance.
• You will be sent chunks near you when you log in, but you will not be sent any new chunks if you move away from where you logged in.

I have isolated this to only be using ticktools 1.1.0 and fabric api 0.40.1. Tested on MC 1.17.1. Issue persists on vanilla client. Another thing to note is that /ticktools status reports the render distance being 1 or 2 chunks higher than what the server log is reporting. But I didn't look into that yet. Might be related, might be cosmetic. Mentioning it just in case.

My config

# Required options
splitTickDistance = false
# Required if relevant config option above is enabled
tickDistance = 8

[dynamic]
dynamicTickDistance = false
minTickDistance = 4
dynamicRenderDistance = true
minRenderDistance = 4
maxRenderDistance = 12

# This value controls the MSPT used to target
targetMSPT = 50.0

The server log does not have anything useful. but the client log is being spammed with
[Render thread/WARN]: Ignoring chunk since it's not in the view range: X, Z

So here is my client's latest.log (vanilla 1.17.1) I can send my server's log too but I don't think it will tell you anything. I can also provide videos and screenshots if needed. Just tell me what information you still need. I tried to provide everything I can think of.

[Genau6502]

[Render thread/WARN]: Ignoring chunk since it's not in the view range: 9, -27

What is your client render distance?

[slidedrum]

I had it set quite high for testing. I set it to 24. Will test if issue persists if client render distance is less than server's max.

[slidedrum]

Issue does persist with client render distance lower than servers. Set my client render distance to 6, followed repro steps. And I get sent chunks up to server's max render distance from where I logged in. but not further. And the client log is still spamming Ignoring chunk since it's not in the view range:

[solonovamax]

Can also confirm, happens in the latest version: 1.1.1, on mc 1.18.1. (for the 1.18 version, I'm using a PR I made, #20)
Fabric api version 0.45.2.

It will cause chunks to be randomly unrendered for the client, and the new chunk cannot be requested in any way (eg. by placing a block to update it)