Steps to reproduce:
-Set up a valid structure save area using corner blocks.
-Teleport yourself approx. 50 - 80 blocks away, starting from one of the corner blocks.
-Place a save block, use the same name (obviously), and click detect.
It'll detect the structure, but sets up an invalid savebox. The invalid part can manifest itself in multiple ways, but in all cases the save box won't involve the intended area.
Included screenshots show me standing on one of the corner blocks (to share coordinates), and the save block and its coordinates as well as the invalid set up savebox. Further in the background you can see the house (intended save area).
I've also added a 3rd picture which shows the intended savebox, so that you can rule out the option of me using an invalid sized area.
Attachments
Comments 4
Late reaction (I don't frequent the bug tracker); the problem still exists in the current snapshot of 18w14b but it's definitely improved. Instead of setting up a weird sized box the system now sets up a correct box where size is concerned but does so at the edge of the structure box limit. So it doesn't encompass the actual structure.
I've attached a file showcasing this new behavior:
[media]
So although it's still somewhat wrong (I'd expect an error or something) it does make a lot more sense than the previous behavior.
This happens because the maximum offset is 32 blocks, so being more than 32 blocks away will shift the save box over accordingly. Also, the save box will be rotated if a rotation is set under "load" mode then switched over to "save" mode.
Does this still affect the latest versions of the game (Stable 1.15.2 / Snapshot 20w21a)? If so, please update this ticket accordingly. Should the original reported be inactive and no longer contribute to the bug tracker, the reporter of the ticket can be changed to an active user.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Does this problem still affect Minecraft 1.11?