MyInputProcessor examines all shortcuts loaded in the game, even if they aren't currently active with an input context, and discards lower priority (fewer modifier) shortcuts. This means that registering a Ctrl+F shortcut on a rarely activated input context (for example, when sitting on a chair) will mean that a binding for just F will never receive an event when Ctrl+F is pressed.

This is debatably intended, in which case this should require an exact modifiers match all the time, or it's not intended, in which case this should start with the match closest to exact, and then ignore modifiers one at a time until a matching shortcut is found.

Making this worse, MyShortcutStorage.GetAllShortcuts doesn't filter out multimap entries that have an empty values set, causing shortcuts to be returned even if they have been removed from the user's bindings or if they are the default binding for the shortcut declared by a mod.