Steps to reproduce
On a flat surface, place chests in an arrangement corresponding to the diagram below: place a copper chest on the red block, and wooden chests on the yellow blocks.
[media]Spawn a copper golem on the blue block.
Expected result
The copper golem moves to the copper chest to check for items.
Observed result
Most of the time you try these steps, the copper golem does not move. The copper golem may move if it happens to randomly pathfind before it detects the copper chest. If it detects the copper chest before random pathfinding, it gets stuck.
I created 18 chests. 17 chests had single items in them. 1 chest was empty. I placed 18 items in the chest. 17 of the items had matching chests. All chests were within 25 blocks of the copper chest. So according to your release notes, they were within the 32 block limit.
I wanted to do a test to see how the golem would sort these items and see what it would do with the 18th item that didn’t have a matching chest. I wanted to see if it would put the extra item into the empty chest.
What I observed was not what I expected. The copper golem did have issues sorting. It would go through 10 chests, then pause for a time and then try again. But from the release notes, it’s supposed to do that. It took a while but eventually sorted 13 items into 13 corresponding chests. But then it stopped sorting. I thought it was pausing, but it just stopped. It never went back to it’s chest to grab more items. And it just stood on the same block and never moved off. I’m guessing it could not pathfind back to the copper chest that it was removing the other items from.
Is this a bug or design that it will only sort 13 items and then you have to make another golem?
Linked issues
Attachments
Comments 12
We do not have enough information to find the cause of this issue.
Based on the screenshot and description, this sounds like it may be more of a pathfinding issue like MCPE-223948. Could you get a close picture of the place where the golem is stuck, or record a video of if happening and attach it to this report?
In case the resulting video file is too large to be uploaded to the bug tracker directly, please upload it elsewhere (e.g. as unlisted video on YouTube) and link to it here.
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
When the copper golem was working, it would even climb on top of some chest and check them. So the path finding was working over the chests. But once it was in this position, it stopped.
I understood your comment about the bug and yes, I understand the difference. I work for a software build company as well. However, your bug ticket seems a bit different that what I provided in the video above. I’m not punching the golem or doing anything other than observing behavior.
If you can review my video above an see where it is stuck and if you feel that without interacting with the golem, it is still the same bug that you reported, then please close out this support ticket. I don’t know if you work for Mojang or not. So I don’t know if you can resolve this ticket. If you are not Mojang, then I will leave this support ticket open and maybe one of the devs will see it and create a bug ticket from it.
At least, that is how it works at my software company. Support tickets give birth to bug tickets.
Please let me know if this is not the process at Mojang.
Thank you for replying. I think you’ve misunderstood me: this is not a support ticket. Mojang has a separate site for account support (support.mojang.com), and for technical support issues we refer to our community support Discord. However, the process for the bug tracker is similar to what you have outlined. Mojang has an internal issue tracker separate from this public bug tracker. After a report is confirmed by volunteer staff or Mojang QA, then QA copies it to the internal tracker and lists the ADO number on the public report. Helpers and Moderators like me are volunteers who have been authorized to update reports on the public tracker by confirming, resolving, linking, etc.
Reports here get handled more readily when they have steps to reproduce the issue. Video showing how to reproduce the bug is also very helpful. Your video shows that the golem is stuck, but unfortunately it doesn’t show how it is getting stuck. I have figure it out now, but it took some time.
Cool. Yes, the process sounds similar to ours. I apologize that I didn’t capture the steps to reproduce. Honestly, I didn’t expect the glitch. The golem had been working fine up until that point. LOL. I had been watching it because a friend of mine said that the golem had issues. However, when I tried what he said, I was never able to reproduce his issue and never ran into it as he described. I’m guessing that Mojang fixed it in a preview version. However, as I watched the golem, that’s when I saw a different issue (the one that i described here in this thread).
Sorry. I know the first rule of troubleshooting is to be able to reproduce the issue. But I honestly didn’t expect what happened. I guess I could have remade the world and tried again. Next time I’ll do better for you, other moderators and the DevOps and Engineers.
But I really appreciate the assist with this one.
If you have what you need for internal tracking, you can probably just close this one out.
Thanks. Since this report is confirmed as a unique issue, it will stay open until assigned an ADO and the internal report gets resolved. Copper golem has only existed since the current Preview version, so nothing has been fixed yet!
I created 28 double chests on both sides of a copper chest, there was only 1 building block between the chests and the copper chest. the chests were stacked in 2 rows. the furthest chest from the copper chest was 14 blocks away. the golems only spread out to one side and some golems did not check all the chests even on one side, 3 checked 13 on one side and 4 checked 14 but on the wrong side. all of them got items from the last chest in the higher row (row 2). after checking 13 chests (some) did not check 14 and all of them started checking random chests on the side they were on. they did not want to change the side of the warehouse to the one on the 2nd side of the copper chest.