Not sure why it should matter. People complaining about a missing shortcut is more than worth it, to fix one of the biggest exploits in the game. EDIT: But even better you could just make it optional, explained below. Wouldn't disabling the reading of that key be literally like one line of code? If it's additionally disabled by default I really don't understand the problem. Because there would be no problem. Everyone goes home happy. Something like: Code: if (input) == ("A" ASCII code) then override_input_send; I find it ironic that in previous versions the CantSaveDuringCombat was enabled by default, which would piss a lot of people off or at the very least confuse them as to why something provided isn't working (just like you say would be the issue with the keyboard shortcut), but that you both feel the opposite is true for this issue. Personal taste in gameplay style should not dictate fixing of massive exploits. An exploit is an exploit is an exploit. Example: It took me while to figure out that I couldn't save during combat because of Sfall. When I found out, I was very frustrated. So your reasoning is valid. However, if the setting had come disabled by default, it would have been transparent and thus players and modders could choose whether to enable it. Like I said, everyone goes home happy that way. Best solution, I think: Players are given choice whether to PreventSaveDuringCombat or DisableKeyToStartCombat, but both disabled by default. Modders such as myself and killap could simply add each to the installer, letting users choose if they want to disable them.