In the situation where I discovered it, I put crafter blocks facing each other, disabled 8 places on one side and put 1 stack of iron ingots in it, and placed 9 stacks of iron nuggets in all squares without disabling any of the other blocks, and iron nuggets. If you press the shift key and left click on a certain crafter block at a certain timing, about 9 stacks of iron nuggets will disappear.
Linked issues
Attachments
Comments 4
Your report does not contain enough information to understand or reproduce the problem.
Please be specific about which crafter block and what "timing" is needed. The video is very blurry, and in any case, is not a substitute for including the steps in the Description.
Please add the following information to the Description, as shown here:
Steps to Reproduce:
1. (list every step carefully, so someone else can reproduce the issue)
2.
3.
Observed Results:
(briefly describe what you see happen, including any message(s) shown)
Expected Results:
(briefly describe what should happen)
Try following your steps to make sure you include everything and can still reproduce the issue yourself.
Use screenshots or video to help explain (but not replace) the above information
This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
Many players find this Bug Report Creation Form useful for filling in all helpful information.
Steps to Reproduce:
1. Build a setup like this.
2. Lock 8 slots in one of the crafter, and put a stack of iron ingot in it.
[media]3. In the other crafter, spam click Shift+LMB iron nuggets from your inventory.
Observed Results:
Sometimes all 9 stacks of iron nuggets will be deleted.
Expected Results:
Iron nuggets should never be deleted.
This the same issue as MCPE-166390, so I am resolving as a duplicate. I will update the summary of the other report to make it more clear, too.
Maybe it shares the same root cause with MCPE-166390?
Edit: Can confirm in 1.20.70.24 Preview.