The InputSystem plugin looks good, and the author seems to have responded with fixes when bugs were found.
But it is still beta, and loading the 3rd example that comes with the plugin shows a strange behaviour when detecting a click on a text field.
It seems to be miscalculating where the text field is, and you need to click above the text for it to register.
This is why I mentioned a simple plugin that gave us access to the same drop-down choices we have in the editor.
Plugins that try to do everything are great, but obviously they are prone to a lot more bugs, and most of the time they are overkill when you're just looking for a single feature.
I was hoping that one of the devs (or caretaker devs) would join in this discussion.
I will test InputSystem to destruction, and hopefully find it'll do the job without any problems, and then consider adding it to my project.
For anyone who doesn't know what I'm referring to when I talk about the player controls at edit-time, I'm talking about the drop-down lists at the bottom of the left panel in the Application Properties, where you choose which key is used for left, right, jump, etc.
If we just had access to those drop-down choices during runtime, user-defined keyboard controls would be simple to implement without the need for plugins.
If I'm honest, it's one of the things that I thought should have been in Construct from the very beginning, because it's something that almost every game has.