BDS-18458server-authoritative-movement=client-auth causes Issues mining blocks, picking up items, and actuating doors/traps
—
Update: This issue has been mitigated by changing `server-authoritative-movement` to `server-auth` instead of `client-auth`
Even newly generated worlds are broken in 1.20.10.23 using `client-auth`
—
Cannot mine blocks or pick up blocks after latest update to 1.20.10.23
Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them in the client.
After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
We tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.
I also encountered this error message at one point:
NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Also found this WARN level error:
[2023-06-16 04:35:39:555 WARN] LevelDB worlds/Bedrock level/db status NOT OK(Corruption: 11 missing files; e.g.: worlds/Bedrock level/db/447921.ldb). Trying repair.
It may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly.
Environment
Minecraft Bedrock Preview server version 1.20.10.23 running on Ubuntu VM
Attachments1
Comments4
History14
Changed description:
Cannot mine blocks or pick up blocks after latest update.
0Cannot mine blocks or pick up blocks after latest update.
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Changed description:
Cannot mine blocks or pick up blocks after latest update.
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them. After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up
0Cannot mine blocks or pick up blocks after latest update.
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them. After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up
I also encountered this error at one point while investigating the issue:
NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Changed description:
Cannot mine blocks or pick up blocks after latest update.
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them. After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
0We tested this with multiple clients
I also encountered this error at one point while investigating the issue:
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Changed description:
Cannot mine blocks or pick up blocks after latest update
Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them
Cannot mine blocks or pick up blocks after latest update
Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them
NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Changed description:
Cannot mine blocks or pick up blocks after latest update to 1.20.10.23
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them in the client.
0After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
0We tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.
0I also encountered this error message at one point:
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
Also found this WARN level error:
[2023-06-16 04:35:39:555 WARN]
It may be worth noting we upgraded from 1.20.10.21 to 1.20.10.23 directly.
Changed description:
Cannot mine blocks or pick up blocks after latest update to 1.20.10.23
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them in the client.
0After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
0We tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.
0I also encountered this error message at one point:
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
0Also found this WARN level error:
0[2023-06-16 04:35:39:555 WARN] LevelDB worlds/Bedrock level/db status NOT OK(Corruption: 11 missing files; e.g.: worlds/Bedrock level/db/447921.ldb). Trying repair.
0It may be worth noting
Cannot mine blocks or pick up blocks after latest update to 1.20.10.23
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them in the client.
0After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
0We tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.
0I also encountered this error message at one point:
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
0Also found this WARN level error:
0[2023-06-16 04:35:39:555 WARN] LevelDB worlds/Bedrock level/db status NOT OK(Corruption: 11 missing files; e.g.: worlds/Bedrock level/db/447921.ldb). Trying repair.
0It may be worth noting
Changed description:
—
Update: This issue has been mitigated by changing `server-authoritative-movement` to `server-auth` instead of `client-auth`
Even newly generated worlds are broken in 1.20.10.23 using `client-auth`
—
Cannot mine blocks or pick up blocks after latest update to 1.20.10.23
0Attached a video to demonstrate the issue. Blocks are not actually "mined" after mining them in the client.
0After restarting the server, there is a brief period where 4-5 blocks can be mined before the issue starts again, but those blocks cannot be picked up.
0We tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.
0I also encountered this error message at one point:
0NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121
0Also found this WARN level error:
0[2023-06-16 04:35:39:555 WARN] LevelDB worlds/Bedrock level/db status NOT OK(Corruption: 11 missing files; e.g.: worlds/Bedrock level/db/447921.ldb). Trying repair.
0It may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly.
Changed summary:
Changed summary:
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Resolution: Unresolved → Incomplete
Hi
Does this issue occur immediately or there are any specific actions taken before issue start to occur? Have you updated your server by copying new version files to existing server directory and replace alredy existing files?
This ticket will automatically reopen when you reply,
I'm getting this. Happens immediately.
1) I was able to jump off the end island and walk on the void floor taking no damage.
2) Relogged - was in same position as initial login.
3) Switched to server-auth and died
4) Switched back to client-auth to test - ran away from zombie at spawn and he damages me even though I am not there, again, as if I'm not actually moved.
Hi
Does this issue still occur after updating to 1.20.15?
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki