Player data desync on server change about husksync HOT 5 CLOSED

Your hardware seems reasonable enough

Looking at the trace in more detail - it seems like it's crashing on an I/O write of that player's data to their NBT data file (like, the actual .dat file in the playerdata directory on your server.

HuskSync doesn't prevent Minecraft from persisting user data to disk, as is by default, for redundancy purposes. Have you done something to remove permissions from writes to the playerdata directory in your world folder / are you doing stuff with that data to, say, delete or move it?

from husksync.

This issue happens since the update of attribute synchronization. I have been running earlier version for a long time with no sync issue than the "health" one.

from husksync.

It looks like it failed to finish processing the disconnect packet on your server due to thread timeout. Try disabling sync modes?

Honestly this is kind of unusual; I'm not doing anything massively expensive aside from reading player attribute data, is your server that low spec?

from husksync.

I find it unusual too since the TPS remain consistently at 20. This is the second time that my player report a desync problem since the update to 3.5. I plan to test a different infrastructure to determine if the issue persists. My current cpu is ryzen 5800x and it's a shared plan so I'm not sure if it's the spike, because if player don't disconnect from the network, the problem is still there each disconnection event.

from husksync.

Closing this as the issue reported seems specific to the user's case - if further help is needed, get in touch on Discord.

from husksync.