every time i am adding troops to an general, the moment i press 0 (Zero) it jumps to another camp.
when doing FT adv and setting up blocks it becomes tedious.
give us an option to disable keyboard shortcuts!
every time i am adding troops to an general, the moment i press 0 (Zero) it jumps to another camp.
when doing FT adv and setting up blocks it becomes tedious.
give us an option to disable keyboard shortcuts!
wow, thought it was me doing something daft
How is that happening exactly? I use the numeric keypad when assigning troops (if I'm not using the slider) and it works fine. Is is caused by using the regular numeric keys on top of the keyboard?
Sorry, but I've slept since then...
Both num pad and regular at top. Also it is not only an issue on adventures but also on home island (at least for me). Reason behind this seems to be that different sectors have key binds to quickly jump between sectors - generally a nice idea, but it interferes with typing unit numbers into the text field of each general.
Maybe worth noting: I don't use the browser version of the game, I play via Steam client.
I use the browser version. I've only noticed two such annoying things: one is typing 0 into the troop assignment fields which centres on some general (I couldn't figure out the rule for that because it seems to be a different general every time), and the second is typing a hyphen into the chat on the home island, which also activates the zoom command.
Generally, I think it could be solved if the keyboard shortcuts weren't active when the cursor is in an entry field.
During adventures, I dunno, I find that useful occasionally ... but while typing in a window, specifically while entering numbers in a number field box, it makes sense to disable number key shortcuts.
In the end, that's just a mis-placed event handler: It shouldn't be global, but have a div context.
Guys, just to get a better overview of this, can each of you please tell me the browser/ Steam/ Slim browser etc that you are using to access the game?
We need more details as not everyone is experiencing this.
Thank you!
I have this problem with Chrome Version 50.0.2661.49 beta (64-bit)(Linux)