This action system wouldn't allow the user to be notified for multiple keys at once though...

Sure. Like I said, simply substitute "key" for "action".

"Multiple keys at once" => "Multiple actions at once".

 

Whatever client <=> server communication you did before with keys, you do now with actions. And on the client side you substitute in the keys for actions when sending and actions for keys when receiving.

 

 

So...for this jetpack example the user would have to create 5 actions?  That doesn't even work right, all the directional movement keyhandling has to be done in a single location.  This method is falling apart the more it's examined...

 

 

If you're wondering why I say it has to be done in a single location:  https://gist.github.com/izzyaxel/ca1483e034914dc43ddc2798be330ef2

Ok, got something I'm happy with:

 

 

https://gist.github.com/izzyaxel/ebd1a16d6146e317d0f5f6435164ff8c

 

 

Allows for users to register their own alias/keybind pairings for the system too.