Wrong chunk rendering

[TheoMarque]

Describe the bug
Using a latest packetevents for 1.21.10 and paper latest build for 1.21.10, sometimes chunks are not render properly and in client I see in logs:

[15:28:21] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -46, 341
[15:28:21] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -50, 341
[15:28:21] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -63, 327
[15:28:22] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -63, 328
[15:28:22] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -64, 327
[15:28:22] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -64, 328
[15:28:22] [Render thread/WARN]: Ignoring chunk since it's not in the view range: -51, 341

How To Reproduce
Steps to reproduce the bug:

1. Paper 1.21.10 (latest), packet events fot 1.21.10 (latest), PVDC 2.3.3.
2. Just run a server and leave it for few hours. Back and start walking/flying around.
3. Spam of "view range occur" and in game you not see any chunks. Yes, these chunks have different coordinates than in client console saw.

Not tested for 1.21.11 because only way to not see a problem is using paper 1.21.10 - build 69. Latest builds - has it. Asked a Paper Engine team, they not change anything in engine for chunk generation/packet serving
Asker packet events author that not see a problem related to a chunk view (packetevents without PVDC) not cause any problems.

So, root cause is in PVDC.

[Wyzebb]

Hmm this is very strange, I haven't seen it before. What version of pvdc are you using?

[TheoMarque]

Latest of course, 2.3.3.

I think, my friend that have a server too, used other plugins with packet events and cause the same effect. Probably a problem is caused in api of paper and / or with packet events. Maybe need to be hooked in other way?

And, if I bypass a player, (or be op) missing chunks still occurring, so, just enabled PVDC on default config.

[Araflologo]

Can confirm i have the same bug. Paper 1.21.10 latest versions of PVDC and packet events