Let's be clear on what constitutes modding: If you go into the cfg's or the JS code (if any) or anything else that is part of the systems/code base, and you do modifications to those... we are no longer responsible for your product working or not.
If all you're doing is "asking/requesting" the product to work using the codes that you want/expect to be the "correct" ones, there's no guarantee that will work and we do not agree to do this for you, or for anyone else. There are several reasons for this but, by far, the biggest one is fidelity/functionality. Our products are built to resemble as closely as possible the real thing. Without bugs (at least, as minimal as possible). To do this requires that we, sometimes, not be beholden to using the built in API's/calls/variables that Asobo has deemed fit for use. As their product is a moving target, doing so would seem... silly. So we only do so when we absolutely must.
All of this said, it is our intention to put a list (as complete as we can make it without actually giving away our code) of accessible variables in the back of the manual on release of the SP (service pack).
It's important to note that I am not exactly the best customer service person but... at least you will know if we can do something (or not). I won't hide that.
Also, wing folding WORKS now... not sure why it's not working for you but if you're trying to assign it to a "button" that may or may not work. Sorry.