Tested on both iPad Pro 10.5 (iOS 11), with SteelSeries Nimbus MFI controller, and on Windows 10 with Xbox One controller. When doing actions that use the right trigger button (i.e. opening fences, placing blocks, filling/emptying iron bucket, and opening doors), they often happen too fast, causing them to occur more times than intended. Edit (2017/09/28): Upon further gameplay testing, I was able to determine that this only happens when the player is moving (foot-based movement) while performing the action.
For example, trying to open a door can cause it to open and close many times with a single short trigger activation. Things like doors and fences often end up closed, again. Sometimes selected blocks are unintentionally placed when opening doors and fences. This causes the iron bucket to be difficult to fill or empty at a water source. Blocks also place too fast, often causing misplaced blocks.
This is only an issue when using a controller.
Linked issues
duplicates
Comments
migrated
migrated
On Windows 10, this issue does not appear to occur after the update to 1.2,2.
migrated
On Windows 10, this issue does not appear to occur after the update to 1.2,2.
migrated
On Windows 10, this issue does not appear to occur after the update to 1.2,2.
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-26819.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-26819.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-26819.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-26819.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
migrated
I made this issue separate because the issue, at least with a controller, was well beyond block placement. It involved the actual activation of in-world items (fireworks, doors, and more) to the point where they activated an immeasurable amount of times per second, most likely as a result of movement causing the placement delay to reset. While likely the same issue, I wasn't certain if the root causes were the same. I'm glad it has been fixed. The patch notes did not mention a fix of this sort.
migrated
I made this issue separate because the issue, at least with a controller, was well beyond block placement. It involved the actual activation of in-world items (fireworks, doors, and more) to the point where they activated an immeasurable amount of times per second, most likely as a result of movement causing the placement delay to reset. While likely the same issue, I wasn't certain if the root causes were the same. I'm glad it has been fixed. The patch notes did not mention a fix of this sort.
migrated
I made this issue separate because the issue, at least with a controller, was well beyond block placement. It involved the actual activation of in-world items (fireworks, doors, and more) to the point where they activated an immeasurable amount of times per second, most likely as a result of movement causing the placement delay to reset. While likely the same issue, I wasn't certain if the root causes were the same. I'm glad it has been fixed. The patch notes did not mention a fix of this sort.
migrated
I made this issue separate because the issue, at least with a controller, was well beyond block placement. It involved the actual activation of in-world items (fireworks, doors, and more) to the point where they activated an immeasurable amount of times per second, most likely as a result of movement causing the placement delay to reset. While likely the same issue, I wasn't certain if the root causes were the same. I'm glad it has been fixed. The patch notes did not mention a fix of this sort.
On Windows 10, this issue does not appear to occur after the update to 1.2,2.