[Reported] [Switch] issue with controller button input

Platform, device version and operating system:
Switch, using pro controller input

Screenshot or image:
NA, see description

What you were expecting to happen, and what actually happened:
In battle, we hold L and press ABXY to access our own troops.

If we then release L /before/ releasing A or B, the game reads this as an additional A or B button press input, causing the A spell to misfire, or unintentionally backing out of the troop screen respectively.

How often does this happen? When did it begin happening?
As this is not really a bug, but rather an issue of unfriendly / confusing UI design / implementation, it happens 100% when the button sequence is pressed in battle. (In the case of L + A, the spell fires off if it is mana charged.)

Steps to make it happen again
See above.

Hello :slight_smile:

Thank you for telling us about this issue for the Switch console.

I’ve reported this to the development team

1 Like

Yup, can corroborate. I know it’s common practice to register inputs on the “keyup” type event, but for inputs that act as modifier keys, their keyup event isn’t (necessarily) a meaningful input.

  • L+X and L+Y are ultimately harmless (nothing happens, card popup remains onscreen).
  • L+A causes troop #3 to spellcast if at full mana, whether you intended to or not.
  • L+B is technically harmless (nothing happens, but the card popup disappears)

I suspect this isn’t limited to the Switch version, and should be tested on all platforms.

1 Like