I haven't seen mention of this bug. It affects Xubuntu Trusty (14.04) at very least. I am using XFCE as the desktop with Metacity as the window manager.
The game seems to randomly fail to recognize most keys, including the following:
- All letter keys (A-Z);
- The space, quote, semicolon, comma, period, and solidus keys;
- The grave accent and the minus and equals keys (the ones appearing next to the number keys: keypad Add and Subtract are recognized);
- The Enter key (keypad enter is recognized), which registers as Digit 1 instead of Enter;
- The Escape key, which registers as Digit 2 instead of Enter;
- The Backspace key, which registers as Digit 3 instead of Backspace;
- The Tab key, which registers as Digit 4 instead of Tab.
If you engage the caps lock during game play, the game recognizes the caps lock, but the problem persists (as though it updates its state expectation in anticipation). If affected by this problem, you must
close Terraria completely, then engage the caps lock and re-launch Terraria. The game will then work correctly, even if caps-lock is deactivated.
This is a
really weird bug. How are you handling your input? I have seen similar cases to this happening before because Windows events report upper-case letters to listeners while X11 reports lower-case letters. That said, yours is the first where I've seen escape and enter not work. You can't be using XLookupString or XLookupKeySym because Space would give " ", which would work correctly. Plus, VK_ENTER and VK_ESCAPE on Windows are given their ASCII equivalents, just like on Linux. I looked at the dump of information given to your window for Escape and 2, and saw not a single nybble in common. I considered sign overflow since the keysyms for those four oddball keys are, respectively, 0xFF0D, FF1B, FF08, and FF09, but the keysym for Space is just 0x20, and the keysym for CapsLock is 0xFFE5, so the high bit being set is neither necessary nor sufficient for this problem. Moreover, only two of those keys are consecutive, and they'd be in the wrong order, anyway. So, um, what the hell?
EDIT: Originally I believed that starting the game with the caps lock engaged would work around the issue. I have since learned that this was a fluke. I have not found a procedure which is guaranteed to start the game with working input. String operations on keys which would correspond to a KeyTyped event
do work; for example, I can name a map "ABC abc`-=,./" even though I cannot use ANY of those keys in, say, the Controls menu (and the game will not respond to them). However, the text prompt will still not recognize escape and backspace, and presumably not enter or tab, either (don't remember if those did anything).
Anyway, best of luck on this issue. I'll just engage my caps lock before playing until build 3 or whatever. Happy to help further if needed.
Great to have a release on Linux! ☺
