Summary: Manually typing in the tilde character (~) for relative coordinates results in the player being unable to affect the game in any way, whether they are composing the command in the chat box or in a command block GUI. For example, beginning to type /tp @s ~ ~1 ~
results in the player often not being able to finish typing the command, followed by the player being unable to exit the chat/command block GUI or affect the game through any inputs.
Expected vs. Result: Intuitively, the player should not be soft-locked while composing a command, and I expected to be able to continue to write the command or exit the chat/command block GUI by means of pressing Escape, Enter, or clicking Done or Cancel in the case of the command block. All of these methods did not work, and the game seemed to ignore these inputs, effectively soft-locking the player. However, the game did not appear to be frozen, as my framerate continued to fluctuated and mobs still moved in the background (if I wasn't in a command block)
Steps to Reproduce:
(Optional) Create a new world to ensure no other influencing factors. Ensure the player can run commands in this world
Open the chat prompt to being composing a command that can take relative coordinates as arguments (e.g. setblock, tp). For example, typing up to
/tp @s ~ ~
(at least in my testing), resulted in any further keyboard inputs failing to register. Similar results occurred for/setblock ~ ~
After restarting the game and reopening the world, the player is no longer softlocked. Run
/give @s minecraft:command_block
to try out the command block GUI.Typing in
/setblock ~ ~
will yet again result in the aforementioned softlock
Further Notes:
I tried to reproduce this bug on my laptop (Windows 10 Home, Intel i7-770HQ @ 2.8 GHz, GTX 1050, same Java edition) and could not replicate this at all.
Related issues
Attachments
Comments


Please try to find the logfile of the time that issue has happend and attach it here, maybe there's something logged.

I tried out your steps to the letter and I didn't get softlocked...?
Does MC-123968 describe your issue? (Discord overlay)

Apologies for not providing more information or being more active about reading replies. At any rate, the bug appears to have been fixed in 1.13 Prerelease 1, so I am okay with the bug being marked as resolved. With regards to @Kumasasa's request to examine the logfile, nothing was logged, but I have attached the logfile here regardless. MC-123968 does not describe my issue, as I am unable to click back into the game to resume normal operation.
[media]EDIT: MC-123968 may actually be the issue I had, as I just checked and my overlay key was somehow reset to the tilde key, which I didn't think to check since I had a different keybind before. I have set the Overlay Lock keybind to something else and the issue has vanished. Thank you @tryashtar for realizing what the issue might be!

The exact locking isn't the most important part of the behavior; did you have the discord overlay running at the time? Can you still reproduce in 18w221c or has the issue stopped occurring there?

To be clear, it was the Discord Overlay causing the issue. I have tested having the Overlay keybind set to Shift + ` (which makes ~ in-game but also triggers the overlay, causing the issue) and an alternative keybind (Ctrl + Numpad Period, which doesn't trigger the issue) in 1.13 pre-1.