I just got a new and hot request: Make the InputAction events fire in blueprint. Right now they do not work in blueprints at all. I guess the C++ code is consuming the input. Would be lovely if these events would work without overriding the original functionality of course. From what I remember that should be an easy change in code. Here is a screenshot of some of the events I mean: Screenshot - 1ef41f2a24eea43ba8fcc86f8f16f120 - Gyazo
And some of the direct Input events do not work. Like F1-F12. Might be a bug.