Summary: /setblock doesn't work on first load in a world loaded prior to 1.17.30.23 or 1.17.30.22 and below when in 1.17.30.23 and above.
Steps To Reproduce:
Step 1: Export a World from 1.17.30.22 or 1.17.11 to 1.17.30.23 with Caves n Cliffs enabled in both versions.
Step 2: Load the World in 1.17.30.23 and Above.
Step 3: Compare /setblock command.
Step 4: Repeat.
Observed Result: /setblock doesn't work on the first time loading a world in 1.17.30.23 and above and the worlds from prior to that update.
Expected Result: /setblock should work on the first load into that world.
Comments 2
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.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki