Platform: All
When a chest is constantly being /cloned to the same position by an active repeating command block, trying to take an item out of the target chest will 3/4ths of the time delete the item. This can be hard when you have a starter chest.
1/8ths of the time the item is deleted, it is delayed by 1-2s.
Affects dropped items too.
—
Hello Crimsidius, I noticed this on your "Project Imperium" map.
Comments 3
Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
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
The issue is likely that the contents are being cloned at the exact same moment they are being removed. You can fix this issue in a couple of different ways. The most reliable would be to make the clone rely on a button or pressure plate, but that's not always ideal. If you can't do that, then just add a small delay (1-5) to your repeating command block. That will drastically reduce the likelihood of a timing conflict between item removal and content cloning.