Overwritten keybinds and confirm

So, I've read a few comments here and there from others about how their keybinds have been overwritten by an update/patch. I've alway just brushed it off as an anomaly and moved along. As if to think, pfff, don't see what all the crying is about, I've not seen this."

Well, take a good guess why I'm here writing this. That's correct, I got bit ! :mad: Not a big deal, just frustrating since I don't modify (much) the default binds, just add my own. And since they're on a gamepad, I just locate the function and press the gamepad key and it's back. But even this screwup wasn't done correctly. Not every borked keybind was really borked. Some were still there but didn't work until I simply reassigned the same key over again.

And THIS is what reminded me of a major were they thinking, (or not thinking). Let say I wanted to assign a function to a key that makes sense to me. If that key is already bound to another function by default or not, there is ZERO warning that you're going to re-assign this already assigned key elsewhere. And unless you know where/what all the keybinds are at any given time, you'll not know that "X" function no longer works until you instinctively press the original button bind and get, wawawa (sad trombone).

Come on FD, really. You can do better than that. It's a standard thing to do. What did you do with all the player beta testing data? File it in the circular file cabinet?

[steps down from soap box]
 
Back
Top Bottom