please note that this method will not work after localization. I hit a wall with this solution, just a mere week prior to production release.
Japanese and Chinese localized builds have different “Key display names” than the rest of the world. German and Russian are like english, where
- Space = Space
- Backspace = Backspace
- etc.
but for example getting the Spacebar value in Japanese version of “get display name” will result in スペースバー.
This method is therefore unusable for anything using a direct keyboard input. The proposed blueprint solution completely broke my hacking pc mini-game 
As of the moment I am searching for a better solution, probably going to look in the direction of reading the key values directly.
edit: found the solution. It is to compare the key structure directly and not the string value (which was stupid of me, I assumed the keycode display names are same everywhere…)
