Thanks for your answer Kolbe.
In the next update 4.37, is it possible to have those informations for each config options? (standard);
- Min _Value;
- Inc_Step_Value (ex: 0.25, else N/A);
- MP_Critical (true/false);
- Host overwrite client (true/false).
This can be a simple line at the end of each option (in reverse video or another color) , all in the same format.
In many config options in the Technical Manual, we already have these informations (very helpful, thanks!), but some of them did’nt indicate the “max_value” or no indication if this option is overwrited by the host server, etc.
I know that each value type is already avail with g_b (boolean), g_n (Numeric), g_s (string), etc.
I think that if every options was having an lastline always showing every possible values listed here, will really help outside programmers to validate every inputs from the config files of our teammates (via a little validation program as we have in my VFS).
As a second question/suggestion: Do you still plan to maintain three separate configuration files files in 4.37 (… Base.cfg, User.cfg and Server.cfg)? I must admit that is a big issue now for a squadron manager. In my point of view, the filter option of Joel Bierling was a better way to maintain only one active current configuration file because it was so easy to compare all my teammate’s config file with a little home made program tool (home squadron validation tool). These three config files to scan now is a much harder way to maintain stability for all our squad members…
So your input will be appreciated, because I’m currently working hard for our VFS with a new “F4Patch” like program (as done by Joel Bierling in 2004, but now including all know Options listed in technical manual in 4.36.1. This is a Treeview (hierarchical list on the left side, with input user data on the right side. My program scan every config options in all three config file (Base, User and Server) to output the «final result» of the current active config for this user. So I will probably standby with this personnal project if the actual “config method” is going to change in 4.37…
Thanks for your input and also thanks for this very helpfull technical manual.