When in any inventory, whether the player's inventory or otherwise, hovering the cursor over an inventory space or craftable item and then quickly moving it somewhere that is not an inventory space or craftable item will cause the cursor to jump back either to the space it was on or to a nearby space. This issue can be easily seen by using a controller, opening the inventory menu, hovering over an item, quickly flicking the left stick so the cursor moves off-screen, and quickly releasing the left stick after flicking it.
I do not remember this being an issue in 1.16 and I am unsure of which 1.17 changes may be causing this bug.
Edit: This bug is most inconvenient when trying to quickly drop several stacks of items from the player's inventory.
Linked issues
is duplicated by 8
Attachments
Comments 8
I'm experiencing the same issue too. I play on Console using an Xbox remote. Whenever I'm navigating through my inventory whether it be in creative or survival my cursor will quickly jerk suddenly if I don't land perfectly on an item slot. This causes inventory navigation to become tricky at times and it definitely makes sorting through your inventory a lot harder. Please fix this by making it so that the cursor does not rebound back to item slot that is was on previously if it doesn't land perfectly on the item slot you are trying to navigate to.
A good example of what I'm hoping for is the cursor control from xbox 360 edition. When moving the cursor it does not rebound/jitter back to where you had it. It will simply stop in the open space where you left it or it will automatically go to the nearest item slot.
This is happening for a friend who plays on Xbox. She describes it as suddenly becoming another item. This causes her to drop items out of her inventory (I'm assuming it is a code/lag failed swap attempt and her inventory is full.) This is occuring 1.20.51. In the same world, im seemingly not affected as it hasn't happened to me.
I can confirm that I’m also seeing this on an iPhone with the Razer Kishi in 1.17.0. I don’t remember this being an issue before 1.17.