Monday, December 15, 2008

User Config Protection

We have a lot of engines but only one config.cfg file, which engines gleefully stomp all over. You run engine A, it writes it's own config, you run engine B, it writes it's own, and so on; and you need to go back in and reset all your options and keybindings every time.

NOT GOOD ENOUGH.

The config.cfg file belongs to the user, not to anyone's engine (aside from ID's, of course). So why not check the exec command, and if it's "config.cfg" silently exec "myengine.cfg" afterwards, then write everything out to "myengine.cfg" on exit?

Every engine's peculiar configurations can now be preserved, and nobody will get their settings thrashed just because they decide to try a different engine every now and then.

0 comments: