WASD Breaks With SetCoreGuiEnabled

If you disable chat with SetCoreGuiEnabled and then try to type ingame, your WASD will no longer work until you reset. Your spacebar and other mouse keys do work however. Feels as if ROBLOX is denying the user movement, not that WASD gets unbound.

Could not reproduce - unless this requires that nothing can force capture of a TextBox when a key is pressed.

To assist, I’m using CoreGuiType 4 (all) and can confirm this happens ingame. Happened to all 5 players that I invited to test the game.

Local script →

will produce a game-breaking bug if you press the ‘/’ key → all movement/WASD is broken.

I am very surprised this hasn’t been addressed yet. I cannot think of a more gamebreaking bug than this right now.

[quote] Local script →

will produce a game-breaking bug if you press the ‘/’ key → all movement/WASD is broken.

I am very surprised this hasn’t been addressed yet. I cannot think of a more gamebreaking bug than this right now.[/quote]

Ahh, I keep chat enabled in my game. That must be why I don’t have this issue.