FuhQuake

[Massa]

I really like the configuration management of v0.25.

Now I thought about things which I either do not understand or like to be enhanced

First, is there a difference between "exec name.cfg" and "cfg_load name.cfg"?
If not (or only the directory), why not adding the fuhquake/configs directory to the algorithm of used configuration directories, so that there will be also searched for configuration files at startup?

I really have some problems with the configurations when using multiple quake/qw-engines. One overwrites the config of the other or cannot read it or it contains a lot variables which the engine does not know...

So I think it would be nice, if you could add some features to the configuration management which makes it possible to split "original" parameter and fuhquake specific ones.
So one thing to do would be to generally add the subdirectory fuhquake and/or fuhquake/configs to the search algorithm in every possible directory.
So it will search for config.cfg, autoexec.cfg, etc. first in the usual places (e.g. gamedir, qw, id1) and then if exists, in corresponding fuhquake subdirectory (gamedir/fuhquake, qw/fuhquake, id1/fuhquake, fuhquake)
And it should automatically load any fuhquake.cfg files which it founds at the coresponding places.

The second thing to do would be to add commands for splitting the configuration parameters in a fuhquake specific parts and a "common" part (e.g. with a new flag "cfg_save_specific").
Then I could save my common settings seperately from my fuhquake-specific parts and copy the common ones to places (and filenames) which other engines also load and the fuh-specific to places where only fuhquake find and load them.

Does somebody understand (in principal) what I suggest ? Or am I totally incomprehensible ?

[dkure]

yeap i understand

wouldn't this also need to be done for the other clients you use?

or would you make your config.cfg read only?

[Massa]

It would be nice if every client would split the reading (and writing of course) in two parts: common for all clients and special for that client.

But for the beginning it would be enough, when I could use the common settings of fuhquake in other clients too.
So I would generate the settings and then write them as autoexec.cfg in qw or id1...

And as far as I know, the autoexec.cfg will be read after the config.cfg?!