{ "expand": "operations,versionedRepresentations,editmeta,changelog,renderedFields", "id": "536790", "self": "https://bugs.mojang.com/rest/api/2/issue/536790", "key": "BDS-18458", "fields": { "issuetype": "1", "project": "11700", "fixVersions": [], "resolution": "4", "customfield_10500": { "self": "https://bugs.mojang.com/rest/api/2/customFieldOption/10300", "value": "Unconfirmed", "id": "10300", "disabled": false }, "customfield_12800": null, "customfield_12602": [], "customfield_12601": null, "customfield_12604": null, "customfield_12603": null, "customfield_12606": null, "customfield_12605": null, "customfield_12608": null, "resolutiondate": "2024-05-14T19:14:11.000+0300", "customfield_12607": null, "customfield_12609": null, "workratio": -1, "lastViewed": null, "watches": { "self": "https://bugs.mojang.com/rest/api/2/issue/BDS-18458/watchers", "watchCount": 1, "isWatching": false }, "created": "2023-06-16T07:10:00.000+0300", "customfield_12000": null, "customfield_12201": null, "customfield_12600": null, "labels": [], "customfield_11700": "{}", "versions": [ "21502" ], "issuelinks": [], "assignee": null, "updated": "2024-05-14T19:14:11.000+0300", "status": "5", "description": "---\r\n\r\nUpdate: This issue has been mitigated by changing `server-authoritative-movement` to `server-auth` instead of `client-auth`\r\n\r\nEven newly generated worlds are broken in 1.20.10.23 using `client-auth`\r\n\r\n---\r\n\r\nCannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly.", "customfield_11100": 0.0, "customfield_11300": null, "customfield_11500": null, "customfield_12503": null, "customfield_12700": "[Briefly describe the bug here]\r\n\r\n*Steps to Reproduce:*\r\n# [Step 1]\r\n# [Step 2]\r\n# [Step 3]\r\n\r\n*Observed Results:*\r\n[Describe what happens]\r\n\r\n*Expected Results:*\r\n[Describe what should happen]\r\n\r\n*Screenshots/Videos attached:* [please attach an image or short video]\r\n\r\n*Notes:*", "customfield_12502": null, "customfield_12504": null, "attachment": [ "540183" ], "summary": "server-authoritative-movement=client-auth causes Issues mining blocks, picking up items, and actuating doors/traps", "creator": "JIRAUSER752091", "reporter": "JIRAUSER752091", "customfield_10002": null, "customfield_12501": null, "customfield_12500": null, "customfield_11601": null, "customfield_11600": "0|i2dzc7:", "environment": "Minecraft Bedrock Preview server version 1.20.10.23 running on Ubuntu VM", "customfield_11801": null, "customfield_11800": null, "customfield_11602": null, "customfield_11802": null, "comment": { "comments": [ { "self": "https://bugs.mojang.com/rest/api/2/issue/536790/comment/1266941", "id": "1266941", "author": "JIRAUSER648376", "body": "Hi\r\n\r\nDoes 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? \r\n\r\nThis ticket will automatically reopen when you reply,", "updateAuthor": "JIRAUSER648376", "created": "2023-07-04T12:52:57.816+0300", "updated": "2023-07-04T12:52:57.816+0300" }, { "self": "https://bugs.mojang.com/rest/api/2/issue/536790/comment/1273904", "id": "1273904", "author": "flavourous", "body": "I'm getting this.\u00a0 Happens immediately.\u00a0 \r\n\r\n1) I was able to jump off the end island and walk on the void floor taking no damage.\u00a0\r\n2) Relogged - was in same position as initial login.\r\n3) Switched to server-auth and died\r\n4) 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.", "updateAuthor": "flavourous", "created": "2023-08-08T20:55:42.975+0300", "updated": "2023-08-08T20:55:42.975+0300" }, { "self": "https://bugs.mojang.com/rest/api/2/issue/536790/comment/1279892", "id": "1279892", "author": "JIRAUSER648376", "body": "Hi\r\n\r\nDoes this issue still occur after updating to 1.20.15? \r\n\r\nThis ticket will automatically reopen when you reply. ", "updateAuthor": "JIRAUSER648376", "created": "2023-09-15T13:00:39.675+0300", "updated": "2023-09-15T13:00:39.675+0300" }, { "self": "https://bugs.mojang.com/rest/api/2/issue/536790/comment/1322837", "id": "1322837", "author": "JIRAUSER484247", "body": "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.\r\n\r\nQuick Links:\r\n\ud83d\udcd3 Issue Guidelines \u2013 \ud83d\udcac Mojang Support \u2013 \ud83d\udce7 Suggestions \u2013 \ud83d\udcd6 Minecraft Wiki\r\n\r\n", "updateAuthor": "JIRAUSER484247", "created": "2024-05-14T19:14:11.665+0300", "updated": "2024-05-14T19:14:11.665+0300" } ], "maxResults": 4, "total": 4, "startAt": 0 }, "votes": { "self": "https://bugs.mojang.com/rest/api/2/issue/BDS-18458/votes", "votes": 1, "hasVoted": false } }, "changelog": { "startAt": 0, "maxResults": 14, "total": 14, "histories": [ { "id": "2823567", "author": "JIRAUSER752091", "created": "2023-06-16T07:11:28.159+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121" } ] }, { "id": "2823568", "author": "JIRAUSER752091", "created": "2023-06-16T07:32:22.105+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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.\r\n\r\nWe tested this with multiple clients. All of those clients can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error at one point while investigating the issue:\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121" } ] }, { "id": "2823569", "author": "JIRAUSER752091", "created": "2023-06-16T07:33:07.363+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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.\r\n\r\nWe tested this with multiple clients. All of those clients can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error at one point while investigating the issue:\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. All of those clients can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error at one point while investigating the issue:\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121" } ] }, { "id": "2823571", "author": "JIRAUSER752091", "created": "2023-06-16T07:54:23.064+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update.\r\n\r\nAttached 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. All of those clients can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error at one point while investigating the issue:\r\n\r\nNetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}" } ] }, { "id": "2823572", "author": "JIRAUSER752091", "created": "2023-06-16T07:55:21.427+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting we upgraded from 1.20.10.21 to 1.20.10.23 directly." } ] }, { "id": "2823573", "author": "JIRAUSER752091", "created": "2023-06-16T07:55:33.185+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting we upgraded from 1.20.10.21 to 1.20.10.23 directly.", "to": null, "toString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly." } ] }, { "id": "2824530", "author": "JIRAUSER752091", "created": "2023-06-18T00:36:49.331+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Cannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly.", "to": null, "toString": "---\r\n\r\nUpdate: This issue has been mitigated by changing `server-authoritative-movement` to `server-auth` instead of `client-auth`\r\n\r\nEven newly generated worlds are broken in 1.20.10.23 using `client-auth`\r\n\r\n---\r\n\r\nCannot mine blocks or pick up blocks after latest update to 1.20.10.23\r\n\r\nAttached a video to demonstrate the issue. Blocks are not actually \"mined\" after mining them in the client.\r\n\r\nAfter 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.\r\n\r\nWe tested this with multiple clients and experience the same behavior on all. We can mine/pick up blocks on another server fine.\r\n\r\nI also encountered this error message at one point:\r\n\r\n{{NetworkChunkPublisherUpdatePacket has saved chunk size that is too large readNoHeader failed! packetId: 121}}\r\n\r\nAlso found this WARN level error:\r\n\r\n{{[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.}}\r\n\r\nIt may be worth noting the server upgraded from 1.20.10.21 to 1.20.10.23 directly." } ] }, { "id": "2824531", "author": "JIRAUSER752091", "created": "2023-06-18T00:37:18.797+0300", "items": [ { "field": "summary", "fieldtype": "jira", "from": null, "fromString": "Issues mining blocks and picking up items", "to": null, "toString": "server-authoritative-movement=client-auth causes Issues mining blocks and picking up items" } ] }, { "id": "2824532", "author": "JIRAUSER752091", "created": "2023-06-18T00:37:34.467+0300", "items": [ { "field": "summary", "fieldtype": "jira", "from": null, "fromString": "server-authoritative-movement=client-auth causes Issues mining blocks and picking up items", "to": null, "toString": "server-authoritative-movement=client-auth causes Issues mining blocks, picking up items, and actuating doors/traps" } ] }, { "id": "2832207", "author": "JIRAUSER648376", "created": "2023-07-04T12:52:57.821+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": null, "fromString": null, "to": "10001", "toString": "Awaiting Response" }, { "field": "status", "fieldtype": "jira", "from": "1", "fromString": "Open", "to": "5", "toString": "Resolved" } ] }, { "id": "2849094", "author": "arisabot", "created": "2023-08-08T20:55:48.071+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": "10001", "fromString": "Awaiting Response", "to": null, "toString": null }, { "field": "status", "fieldtype": "jira", "from": "5", "fromString": "Resolved", "to": "4", "toString": "Reopened" } ] }, { "id": "2867277", "author": "JIRAUSER648376", "created": "2023-09-15T13:00:39.681+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": null, "fromString": null, "to": "10001", "toString": "Awaiting Response" }, { "field": "status", "fieldtype": "jira", "from": "4", "fromString": "Reopened", "to": "5", "toString": "Resolved" } ] }, { "id": "2994981", "author": "JIRAUSER484247", "created": "2024-05-14T18:51:47.899+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": "10001", "fromString": "Awaiting Response", "to": null, "toString": null }, { "field": "status", "fieldtype": "jira", "from": "5", "fromString": "Resolved", "to": "4", "toString": "Reopened" } ] }, { "id": "2995085", "author": "JIRAUSER484247", "created": "2024-05-14T19:14:11.668+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": null, "fromString": null, "to": "4", "toString": "Incomplete" }, { "field": "status", "fieldtype": "jira", "from": "4", "fromString": "Reopened", "to": "5", "toString": "Resolved" } ] } ] } }