1.20.1 Chunk Problem

[dniidnii]

Description

Hello. This problem has been written before, but it is currently happening on my server and it is fixed when I delete the plugin. The problem is that some chunks are not loading properly on some players, but they are loading properly on some players. What adjustment should I make for this?

Orebfuscator Version: 5.5.4
ProtocolLib is also available on my server

Reproduction Steps

.

Expected Behaviour

.

Orebfuscator Dump

.

Extra Details

No response

[Ingrim4]

Please provide an Orebfuscator dump file (use /orebfuscator dump) or if Orebfuscator didn't start provide a ProtocolLib dump (use /protocol dump). You should use https://gist.github.com/ to upload it, then include the link below. Without a dump file we sadly can't help you properly.

[dniidnii]

https://gist.github.com/dniidnii/b199c8f41dd259b6e087090f6269240e > orebfuscator-dump.txt
https://gist.github.com/dniidnii/14c47db79c27d6d77eeb7e2b11b27241 > protocol-dump.log

[Ingrim4]

Your dump file looks fine at first glance. My initial recommendation is to try disabling the disk cache in the config to see if that resolves the issue.

If that doesn't help, please follow these steps so I can get more detailed information:

1. Wait until a player experiences the issue.
2. Run the /orebfuscator command multiple times (around 5 times over 30 seconds) and observe whether obfuscationQueueLength ever drops to zero.
3. If it drops to zero, try reloading the server (or just reload ProtocolLib followed by Orebfuscator) and check if that fixes it.
4. Let me know what you find.

[dniidnii]

I tried setting the disk cache to false and unfortunately the same problem occurred. I deleted and reinstalled ProtocolLib and Orebfuscator, but unfortunately it did not work either. When I did /orebfuscator, obfuscationQueueLength always showed 0.

[Ingrim4]

Sounds to me like the packet is stuck somewhere in ProtocolLib, can you please try the steps above where you run /reload when the issue occurs. If a reload fixes it than the packet is likely stuck in ProtocolLib as the obfuscationQueueLength is always zero.

[dniidnii]

Yes, for me it always shows 0.

[Ingrim4]

That's not what I'm asking, I want to know if a /reload solves the problem momentarily for all the chunks that aren't send properly right before the reload?

[dniidnii]

The problem is fixed by teleporting the player to another area, then teleporting away from there and back there. How exactly should I do what you said?

[Ingrim4]

If you or someone else is experiencing this issue with missing chunk(s) simply run the /reload command in console (or as a player with sufficient permissions) and check/ask them if the missing chunk(s) isn't missing anymore (after the reload is done).

[dniidnii]

I found a broken chunk and reloaded it but it still didn't fix the chunk. What I mean by broken chunk is that the chunk doesn't load and it fixes itself when I teleport it to another place and teleport it again.

[Ingrim4]

That is indeed strange, normally I would expect the packets to be stuck in ProtocolLib as that was an issue in the past. Does this happen shortly after teleporting from one world into another because we do have an open issue that is related to switching the worlds?