Controls sometimes become unresponsive for a short time

I have noticed something similar on my desktop PC. After holding the same movement key for an extended period of time, I release it but the game acts as if I were still pressing it, as if it had a buffer full of keystrokes and was working its way through it. Pressing other movement keys, Shift, or Space does not interrupt it. After several seconds it stops and, I think, responds to subsequent movement keystrokes if you entered any.

It doesn't happen often, but has caused me to fall, for instance, and could potentially take the player into a fatal situation from which, with no control, he can't recover, such as walking into an open hole, deep water, or lava pit.

Yeah, I lost a SkyWars game on InPvP due to this issue

I think this might happen when the game is auto-saving.

It also happens on Xbox one if you want it to stop press the same key again

Yeah, that's how annoying this issue is

This is still happening on the latest version

Confirmed on Windows 10 release 1.2.11.4 on a desktop computer with no touch hardware. I was in a boat holding down A and D for a long time. When I released them, I continued rowing for at least 5 seconds before it stopped spontaneously. I have also seen this in Creative when flying a long distance by holding down W.

There may be a root cause connection between this report, MCPE-28255 (type and chat lag), and MCPE-25760 (opening chat keeps button presses). They all seem to have something to do with dropped key releases.

Affects 1.2.13.
I will record a video of the issue happening once I get a capture card for my laptop (because my laptop hardware that I specified in the description can not handle the Record clips feature).

One of my friends tested the 1.2.20.1 beta and found out that Xbox One Controllers were fixed in the beta, but not Mouse and Keyboard or Touch controls.

Finally, post about this. I experience this issue since 1.2 version, android. at first, i think my android touchscreen is broken. But no, other similar game are not affected. only on minecraft. Sometime when i'm walking around and swipe screen for looking around, touch control are stuck on "breaking block" and no i'm not touching screen when that happened. This "ghostly touch" are occured randomly without notice.

A temporary workaround would be to pause the game (via Menu button on Xbox One controllers, Escape on Keyboard and Mouse, Back touch button on Android, or on-screen touch pause button on Windows 10 touch controls) when the issue happens and then wait for a few seconds before returning to the game

I seem to have the most trouble when I'm in water. Like when working in the water streams of my iron farm floors.

It seems similar to the old bug where you would throw your items on the floor when trying to switch to a different item in your hand. When I get stuck in block placement mode, all I have to do is stop and tap the screen. It's like it's still reading that I'm long pressing the screen.

@Michael Gill The issue with water is separate from this issue, they do relate to each other, but they are two separate issues

The water ones have been marked as duplicates of this one so are being treated as the same problem by the powers that be although on my iOS the continual break block instead of direction problem has only occurred since the water update - along with other touch control issues e.g. Having to click the 'up' button to go faster in creative flying. Never had to do that before as the normal sprint action worked.

The moderators must be getting the water issue and the flying issue confused with this issue. They are separate issues, as proved by the steps to reproduce the issues.

@unknown: Having to click the 'up' button during creative flying is an unrelated issue, MCPE-32391. It's not an issue with the controls, but with the game mistakenly thinking you're on the ground.

I'm not sure which issues you're referring to as the "water issues". If it's MCPE-33587 and its clone MCPE-33588, those reports contain too little information for us to be sure what the problem is. Because they describe unintended block breaking while trying to use the controls for a different purpose, it was the moderator's best judgment that this was the closest issue describing it.

This issue isn't actually about the controls, exactly, it's about the game being so busy doing something (we don't yet know what) that it's losing or delaying inputs from the controls. Controllers, touch screens, and keyboards actually send a signal when you press and again when you release. The computer doesn't actually detect that you're pressing, it just remembers that you pressed until it gets the signal that you've released. The problem here seems to be that the release signal is being missed or delayed, so the game thinks you're still pressing when you aren't any more. But the underlying problem is that the game is too busy with something completely unrelated, and it should never be too busy to accept inputs for that long.

Thank you Auldrick. I was referring to another comment about 'the issue with water being a separate issue'. All I am saying is that the addition of the different movements in water i.e. Swimming, seems to be at the cause of my problem because the continual breaking of blocks only seems to happens in or around any water. Yes - the additional comment of another control not working the same way as before should not have been put on this fault.

I am using a LG K20(tm)V and have had this issue for a little bit now. When walking and correcting my path I start breaking blocks. I know my older phone it could have been a screen issue but I doubt that. I don't intentionally aim at a block when this is happening either. This is in 1.4.4 and haven't played much in 1.6.0.5 on my phone to figure out if it is in it.

This issue persists in tor official 1.5.0.14 release

Still happens on 1.5.3

I have tried to make a chart explaining which control options are affected on which platform since my little brother could not reproduce this issue on iOS with a Bluetooth controller

Is anyone able to reproduce this in Beta 1.7.0.5?

I don't generally install the betas, but for me (Windows 10 PC) this virtually disappeared in 1.6.0. It can still happen when the game is generating a lot of new chunks, especially in ocean biomes, but even then it's much less disruptive to play than it used to be. Chunk generation is an inherently CPU intensive process, so this is probably as good as it's going to get without redesigning the game engine.

I expect there have been similar improvements on other platforms, though of course devices with limited resources may still be affected.

One of my friends found out that some platforms were fixed in 1.7.0.7 for certain control options. I have added a yellow star (looks like :yellow_star:) to the fixed control options.

This appears to be mostly fixed in the beta, but still affects 1.6.1

I have tried to gather as much information from the duplicate reports, it has been confirmed that touch controls are affected on all platforms.

That glitch Still Works for Me 🤬🤬🤬

@Dylan Colangelo what version are you on?

I don't know about anyone else, but for me, this issue has disappeared in 1.7.0, if a control option has been confirmed to be fixed for a certain platform it will be marked with a blue star (:blue_star:) for that specific option and that specific platform. Platforms that are not marked are still affected.

To anyone that's been having trouble walking forwards with Touch controls (especially in the Beta), it may be the case that the lower half of the "walking forwards" button doesn't respond at all.

Here's a video showing that.

Aspergerian that might be a separate issue.

Please reopen this. It's gotten worse in the latest beta for windows 10 (1.9.0.0)

I guess the fix was not permanent

I have added some missing stars, and added red stars

1.9.0 release comment: This issue appears to be more noticeable in this update, red stars (:red_star:) now mean the issue is affected by the 1.9.0 update instead of meaning the issue affects the 1.9.0.0 beta

I know that this bug doesn't seem to be as major anymore, but I just happened to reproduce it in 1.14.0.52

Going through old reports, I can't reproduce this in the stable 1.14.60, but can reproduce it in 1.15.0.9 (the RTX beta, which didn't show up in the Affects Versions) and 1.16.0.59

I have removed my computer's specs in the description as it is now redundant to include them in this report.

Nintendo Switch: Controller tab is not affected in my experience. Update the graph when possible.

From recent testing. I've noticed that many devices with higher end CPUs (especially over 1.6 GHz) are no longer experiencing this issue (including consoles). Any platform not affected is no longer included in the above chart

Affects 1.16.200.55 Beta

The issue returned after the 1.16.200 update. The chart now lists more consoles

Affects 1.17.40

1.18.0.22 beta

iOS & Amazon Fire both support Keyboard & Mouse in MC these days so that shouldn't be marked as 'Not Applicable'

Since (I think) 1.20.0 release, this seems to have gotten worse again on my PC, which runs at 2.10 GHz and previously didn't have the problem. But something else I've noticed makes me wonder whether it might provide a clue to the cause:

I use a wireless Logitech keyboard and wireless Logitech optical mouse. Both communicate through a single dongle in a USB port. When the issue happens, I've noticed that simply lifting the mouse off the mousepad seems to instantly let the keyboard resume. This leads me to wonder whether the Windows 11 USB adapter is contributing to the problem.

It would be helpful to know if other PC players can duplicate my experience.

@unknown I've noticed that if I plug my USB keyboard and USB mouse into a USB 2.0 hub plugged into my PC (that I built), the same issue occurs. Could they possibly be related? I've only tested with two USB 2.0 hubs, but with a few different brands of keyboards and mice. I'll have to test with other Windows 11 PCs that I have.

@unknown: Mojang has asked me if we can come up with repro steps so the devs can repeat this. I need your help to figure out if we can come up with steps that reproduce the issue on different PCs. Obviously, they can't build a PC to match your specs, but I can reproduce it on an off-the-shelf Dell with vanilla Logitech devices so if you and I can establish what factors are necessary and sufficient to cause the problem, they should be able to reproduce the issue and actually solve it.

Info I need from you:

1. Are you reproducing it with wireless USB keyboard and mouse? If so, are they using the same or separate dongles? Have you ensured the batteries aren't weak?

2. Is your mouse optical?

3. Can you reproduce the behavior of releasing the keyboard hang by lifting the mouse?

4. Do you know of anything else you can do with the keyboard or mouse that has a consistent effect on the hang—any reproducible effect (not just releasing the hang) could be useful information.

Sorry for not responding sooner, I spent a few days trying to get as much information as I could so that we can reproduce this on multiple computers.

1. I could reproduce this with multiple wireless Logitech USB keyboard and mouse combinations, using a mix of dongles (to make sure none of the dongles are defective), with the combinations using either the same dongle or two different dongles (one for the keyboard, and one for the mouse) plugged into a USB 2.0 hub. I could not reproduce this with two dongles plugged directly into the PC (either on the front panel or the motherboard). In all combinations, testing was done with fresh Alkaline batteries only, and no rechargeable batteries were used.

2. In every combination, all the mice tested were optical.

3. Lifting the mouse does remove the keyboard hang.

4. I don't know of anything else that can be done with a consistent effect on the hang.

So far, the only indicator is that the keyboard and mouse have to share a USB port in some way.

Jonathan, thanks so much for your careful testing! I really appreciate that you took time and so much care!

ALL: We now have confirmation of one cause of this issue that we can document for the devs, and it's likely that all the other causes were fixed years ago given that nobody else has actually reported being affected in going on 3 years now. But there still might be other causes, and if there are are, we need to split this issue into multiple reports. Therefore:

If anybody else (besides Jonathan and I) still has this problem after all this time, please let us know right away with a comment. Please mention whether you're using a wireless keyboard and/or mouse, and if so what brand they are. If you can, please also mention whether once the keyboard gets hung, lifting the mouse off the mouse pad allows normal operation to resume until the next time it happens. Thank you!

Jonathan: As nobody replied to my pinned request to say that they still have this problem, I can only conclude that you and I are the only users still able to reproduce this issue, and as it's probably not actually a bug in the game but a problem with USB drivers (presumably by Logitech), I will be resolving this issue now.

I will continue watching it for at least the next few days in case you have anything additional you want to communicate with me about. Thanks for your continued participation re this issue for so many years!