I literally posted that DCS lists what you would have to test for.
First you would need a list of the installed modules and mods
We got that next you would need a list of the mods a server requires
That is included in the mission file and lastly you would need the abiility to determine if the lists differ
We got that too. Now to get all of this to work, your copy of DCS would have to query the servers to find one which only uses what you have installed. This same filter might also enable player to look for a server that has their favorite module. This guys arguments against having a frequently used controls preset is that controls aren't 100% the same for everything (never mind the fact the idea is to get you enough set up for a free flight). His argument against having a graphics configuration wizard was that ED would need a Cray to run a billion copies of DCS to get every possible configuration when you could use an old-style graphics wizard and ask users if they wanted to contribute their bench mark scores to a database.
I think the best thing to do with SharpXb is to put him on your ignore list.
I've got a little more personal connection. Prior going to medical school my dad was an EWO and had time on the Thud and EB-66. He trained on the Thud but deployed on a EB-66
I want the Thud to live again.
Thud.