I know there is a way to set up an input with shift/control/etc. input on top of the base keybind for an input, but is adding a whole new input entry the best way to approach adding secondary function input? (For example, E does one thing, Shift-E does another).
Just wondering whether it’s best to do the shift-input in blueprints. I usually set up the base input as normal, and then set up a “Secondary Function” bool, which is true while shift is being pressed, false once released. Then just branch the base input and change the function depending on the current state of the bool.
I guess I’m just looking to see if there are any alternatives to this, or any ways that would be more efficient.