josys363

In my case it doesn't really matter as I converted this system to a water based system months ago. However, in 23 years of being a programmer I've learned that things don't resolve themselves. Something here has changed as the behavior has changed. In any event your other ticket should resolve issues if someone runs into something weird in the future. 

Thanks!

I have updated this ticket with a new link to the world download. @GoldenHelmet could you please confirm that this issue was already confirmed.

Jason

This issue was CONFIRMED months ago. Could you please read tickets before you close them?

The comment made by GoldenHelmet on the 11th of Feb states that he CAN reproduce this issue in the world provided. Please read the tickets before closing them. 

This issue is confirmed and you have a copy of the world where the issue is occurring. You tell me if it's still an issue on 1.20. I have a feeling that someone here is doing a ticket sweep, and trying to force close issues. 

With the fixing of MCPE-38963 we are now almost one step away from good item sorting systems. If this bug was fixed it would go a LONG way to achieve that goal. 

I re-uploaded the world and updated the link in the description.

You have a copy of the world already. If you need me to upload it again it will have to be this evening. Please let me know.

When there is an item stuck in the second slot of the hopper, bone meal is still being pushed to the end of the line. In my case it's a loop, so it will continue to push bone meal along, until the loop is full. It's as if the bone meal is bypassing the hopper it should be pulled from, and just continuing along the line.

I would also like to point out that what I described in the steps to re-create this problem, is something I've done a lot before 1.19.60 and had no issues. Occasionally an item will slip through the filer system, but I didn't experience the backup until 1.19.60 was installed.

I updated this ticket with a link to the world download, and also detailed steps to reproduce the issue.

With further testing I was able to get this to fail again. I am going to upload the world over night, and then I'll provide details instructions on how to reproduce this issue in the morning.

I tried to reproduce this issue with the same conditions as last night. However, with multiple attempts I was unable to do so. What has changed from last night to today is there was an update to Bedrock server from 1.19.60, to 1.19.61. With this update applied to my Bedrock server I may have resolved the issue. I will attempt to reproduce the issue again tonight, and if it happens again I will upload the world and provide details on how to reproduce the issue.

OK I sure hope I'm reading this wrong. 1.19.50 went into production today, and it looks like this issue, which is earlier then my issue flagged as a duplicate, was reported on the 6th of November! So you let an obvious flaw that was reported and confirmed go into production. As a software developer myself this makes me furious. Was Mojang just working on the assumption that no one would notice this? I noticed it in 5 minutes since I'm working on a huge remodeling project where I'm using structure blocks.

This does not work on the Switch either. And, it only seems to work on Windows 10 if you use your mouse and click inside the Y coordinates box. If you use the arrow keys it jumps right over it.

This issue appears to not just be a simple sound issue, but is a major lag issue. I've noticed since the July update in question, the amount of lag in my main world is worse. At first I noticed it as the sound issue, but then running other things like my mob farms, and even my villages is worse. It might even be time to just move my world to my own Bedrock server as the amount of lag, plus the nature of auto save is making this world unplayable.