Control on Gamepad fires Attack once, then stops responding

[Image Removed]This is chosen as the answer. From what I understood and “translated” into blueprint, it is checking if the command came from the Gamepad. I tried redoing it in BP:

[Image Removed]Is this the correct translation? If so, should we use this to check if the “rogue” command is registered as a click, but is in fact a wrong Gamepad command?

Thank you.