Unable to set non-conflicting keybinds with conflicting keys

For now this is a game limitation which really sucks. It also means that multiple mods that add extra key bindings to one vehicle will ALWAYS conflict no matter what.
It would be cool if key bindings could be defined in a LUA controller file or a Jbeam file of a certain part, this way only 2 vehicles that have the same controller name or part name would conflict which wouldn't happen very often. The UI would also look a lot cleaner without all of these hydraulics bindings for every Bluebuck config that doesn't use them.

 

It IS a game limitation, it just doesn't warn you because writing a conflict detection code that would only be used to warn you and say that the bindings were removed would be such a waste of code and not worth it at all. Also, even manually adding the code to inputmaps still causes this to happen, I have tested it.

 

Did YOU even read what I said????? Probably no. I don't want to continue this nonsense, you clearly know nothing about game development and what a "game limitation" is.

 

Ok then try to actually explain WHY you think this isn't a game limitation. A game limitation is something caused by the way something in the game is coded that causes unintentional behavior which can't be fixed without recoding the system significantly, and a "glitch" is either something caused by the game limitation or a small thing the developers missed and can be fixed easily. The way this is coded is that key bindings are recognised PER VEHICLE, each vehicle only "sees" its own bindings and not any others. This means the game will only "know" about the bindings of the current vehicle at the time and ignore all others. It will overwrite them if it doesn't know they exist. It DOES give a warning if it's the same vehicle or common bindings because it can see them. The system I was talking about would have to detect conflicts for EVERY VEHICLE and it would be impossible to code and a huge mess, this is why it's a game limitation. What I had in mind for a different system would be that the key bindings are not stored in the data of the whole vehicle but instead in controller files or Jbeam files of specific parts that use those bindings. This way the game would have to check every Jbeam file of every spawned car and store the key binding data of them somewhere. That COULD affect performance a little bit when switching between many vehicles but it would remove the need of implementing the key binding collision detection system that I talked about because all the bindings would already be stored somewhere and the game would see all of them at the same time.
You may know more about how the game is coded than me but the fact that you only noticed it when making a mod doesn't make you any better than me. And I don't spread any wrong informations, I just say what I learned from testing stuff.

 

For this specific thing I haven't looked into the code because I have no idea where it is, probably somewhere in the game engine C code and I haven't ever gone there. But I have run many tests on that and what I have written is my conclusion. I also tested conflicts between multiple mods that add bindings to the same vehicle and that seems much more random. Disabling/enabling the mod can create a huge mess and even delete default in-game bindings. For some reason that usually doesn't happen if the mod you are disabling/enabling has the screen displaying order set higer than the vanilla bindings and the bindings of the other mod. I guess that's why some modders set their binding orders to a ridiculously high value like 9856 to make sure it will never cause this glitch. Overall this system is very messy and I would prefer a different one.
--- Post updated ---

That obviously wouldn't happen because even the common key bindings don't work like this, using throttle on 1 vehicle doesn't give throttle to all of them. As I said the game only sees and uses the current vehicle bindings, probably if it saw all it would happen, but then all the common bindings would have to be an exception, and then backwards compatibility would be messed up for mods that use the old way of setting bindings... as I said this system is a mess.