Daniel Rollins

Also affects 1.14.4. I also have similar machines that worked in 1.12.2 and all 1.13 versions and 1.14.0. I went through the snapshots one by one verifying exactly when it started. The first version with the issue is 1.14.1 Pre-Release 1. Something changed between 1.14.0 and 1.14.1 Pre-Release 1.

Easy way to repro:

/setblock ~1 ~ ~ minecraft:command_block[facing=down]{Command:"clone ~-3 ~-1 ~-3 ~3 ~2 ~3 ~-3 ~20 ~-3"}

/setblock ~1 ~1 ~ minecraft:stone_button[face=floor]

press the button, it will make multiple copies of the platform going up until it hits the height limit and you will see multiple clone outputs 

Confirmed in 1.14.4

Thanks for the info. I'll research GLFW as well and see if I can find anything. If MC-72390 (Rcon is not thread-safe) ever gets fixed, I would at least have a work around by using RCon. 🙂

Anyone?

Anyone going to look at this?

Here is the sample powershell script with some comments, just paste it into a .ps1 file.

I included 2 different sendkey methods. The both methods open the chat window and enter "/say testing" and press enter. Only the 2nd method can actually move a player (very short distance, less than half a block using the code below). Neither method does anything in 1.13 but if I open chat myself then all the sendkey presses will come into the chat (i.e. I'll see t/say testingwwww...) but the sendkey enter won't get pressed either. So chat can see the sendkey presses (except enter) but the key to start chat can no longer be pressed from sendkeys, even if I change the chat key to something else.

Script below:

sleep 10

# Method 1 - This method doesn't work for movement, only for chat (1.12.2). Doesn't do either in 1.13
$wshell = New-Object -ComObject wscript.shell;
$wshell.AppActivate('Minecraft 1.13')

$wshell.SendKeys("t")
Start-Sleep -m 500 # Add half second delay
$wshell.SendKeys("/say testing")
Start-Sleep -m 500 # Add half second delay
$wshell.SendKeys("~") # Presses Enter

Start-Sleep -m 2000 # Add 2 second delay

$wshell.SendKeys("wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddd") # Move forward slightly then right slightly

Start-Sleep -m 5000 # Add 5 second delay

# Method 2 - This method works for movement and chat in 1.12.2 but neither in 1.13
Add-Type -AssemblyName System.Windows.Forms
[System.Windows.Forms.SendKeys]::SendWait("t")
Start-Sleep -m 500 # Add half second delay
[System.Windows.Forms.SendKeys]::SendWait("/say testing")
Start-Sleep -m 500 # Add half second delay
[System.Windows.Forms.SendKeys]::SendWait("\{ENTER}");

Start-Sleep -m 2000 # Add 2 second delay
[System.Windows.Forms.SendKeys]::SendWait("wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddd") # Move forward slightly then right slightly

I agree with Jake. The limit was higher before the update. The update caused the fill limit to be lowered. This is a bug. Something was working and now doesn't. This broke several things on some of my worlds which use command blocks with large fills/replaces.

This also happens on Windows 10 Edition including latest 1.1.4.
Easy to reproduce:
1. Summon or find an entity (eg: villager)
2. Use a nametag to name the entity (eg: test)
3. Try to teleport the named entity (eg: villager named test) using @e[type=villager,name=test]
The result is "No targets matched search"
The result is the same with any entity and any name.