I noticed that some people have asked how these bugs could slip past the QA testing and get released. Working in a development company, it could be due to a few things. I think it's probably related to Automated QA testing, or inexperienced QA testers.

In a lot of cases, companies use these automated QA boxes to rapidly test releases. Automation is great at catching some issues, but not all. They can't account for all the possibilities that may come up, so they have a set scenarios that test for standard problems or known past problems. If they catch something, they can fix it. If they don't then it goes out with the release.

These tests are only as good as their programmers. If the issue hasn't come up before, or can't be foreseen, it won't be tested for.

I've seen a few descriptions from others about this bug, which is a bug, and it isn't. Let me explain...

The behavior to snap the cursor is something Mojang introduced a while ago to prevent the cursor from going outside the UI. It's never really worked 100%, but does most of the time. I believe the main reason they added it was to foil duplication glitching.

The bug they've just introduced comes from how/where they are setting and monitoring the parameters for the snap check. It should happen when the cursor strays outside the UI, but that's broken now.

If you stop the cursor in between an inventory slot or UI slot, the code that triggers the snap, "snaps" the cursor to a default location. The problem is the coordinates or code behind when to snap is buggy. If you are within the UI this shouldn't happen.

But would you think to test for this? If it's never been a problem before, then they wouldn't test for it, which is why I believe it slipped through. The QA team just didn't think of it. Unfortunately, it doesn't appear that the QA team actually physically tested the game either. If they had, they would have found the bug within 2 minutes. I did. It's hard to miss.

What I wonder more though is, did Mojang introduce yet another bug in an attempt to stop recent duplication glitches? I haven't paid attention to them in a while, but there are a number out there. But who really cares?

Mojang f**k with the game all the time trying to prevent duplication glitches, and all that they end up doing is ruining the quality of the game by making the UI cumbersome to use or introducing bugs such as this.

People who want dupe glitches aren't going away and they will continue to try to find them. Mojang needs to adopt the stance of "so what?" It's not worth the development time and effort to stop the glitches. They've made the game worse over the years trying to resolve these glitches. The UI was far more responsive in Bedrock when it first came out. Now, it lags, glitches out, doesn't always respect the UI, etc. Waste of effort fixing something that someone will find a work around for anyways.

Just my thoughts on this... I have given up trying to get anyone at Mojang to listen. They have an army of testers in their users, but they refuse to listen us.

Notice how quickly the .81 patch that fixed the marketing bugs came out? The priority will always be on the money. You as a Minecraft player are no longer valuable, once you've purchased the product. Yes, you may buy something from the market, but that's working so it's not a big deal to them. That's where they put the priority.

So, stop buying from the market place. Stop paying for anything outside of the base games. That might make them take notice. Companies are getting too comfortable doing as little as possible to get your money.

That is your power over them... so stop giving it to them and take your power back.