edit: woops. I mistook this for the buffer overflow problem where the config gets too big.
Anyway, it might help still since it might be the same issue although you might not know it. If you have too many vars set it causes an overflow error and the symptoms of this are..
- You will leave the game and return and find your config doesnt update with any previous changes (the config no longer accepts permanent changes).
- You find odd changes in config when connecting to different mods and some game vars do not show as being set. I notice it happen when config is at 16k +.
There are alot of defrag defaults so even if you put them in a seperate config these will get written to the q3config and the only difference you just have an extra config that doesnt get updated. If you try to exec a 'good' config it may not accept any new values if you have the overflow issue.
I didnt notice the noghost issue before, good to know. People will say that autoexec is the answer to all the config issues.
Well I don't think so and I've noticed some other strange things which has messed up a config.
====
I have the same issue too.
q3config.cfg will always be your main config, autoexec will write/update it.
This will help, but not fix it completely.
1) go through all your configs (except defrag) and remove all the defrag (df_) settings and save the files. That way you will keep most of your configs without losing anything.
2) In the defrag folder, search and replace to remove all the 'seta' entries, but keep all the settings. example: 'seta df_help' becomes 'df_help'.
This will stop defrag settings getting written in any other config.
3) Use your autoexec as normal. If you have changed alot of things use /writeconfig often to a new config and put the settings you need in your main clean config (as writeconfig writes loads of server crap you dont need).
4) Leave the mod before joining any other server, I think you might even need to quit the game to be sure.
I've seen people put /writeconfig q3config.cfg at the end of configs but I dont know if this would clear the old q3config.. I was going to try putting /writeconfig q3config.cfg at the start of my autoexec but dont know if this will work or have bad affects.
Number 2 above will help most I think and you should be able to read and write ok to all other q3config file without it getting too big.
