gl_coloredlightmaps 0

[Zeppelin]

check "Read Only" in your config.cfg
When you want to edit it, just open the file with txt, save and "Read Only" again.
Its how i do..
Yes, i know autoexec is better, but im used to this way   

If you dont check "Read Only" in config.cfg, when you open your client the command will disappear.

[l0ckp1ck]

check "Read Only" in your config.cfg
When you want to edit it, just open the file with txt, save and "Read Only" again.
Its how i do..
Yes, i know autoexec is better, but im used to this way   

If you dont check "Read Only" in config.cfg, when you open your client the command will disappear.

cool putting it on read only seems to be doing the job. cheers

[Zeppelin]

check "Read Only" in your config.cfg
When you want to edit it, just open the file with txt, save and "Read Only" again.
Its how i do..
Yes, i know autoexec is better, but im used to this way   

If you dont check "Read Only" in config.cfg, when you open your client the command will disappear.

cool putting it on read only seems to be doing the job. cheers

yes!
but dont forget, next time you add a command in the config, check "read only" again, or your config will screw up when you open the client!lol
back up your config in another folder too.

[no_life]

You just now are setting up an autoexec? Damn man! And you've been playing this for how long?? J/k 
It is an essential. There are more than one way to make settings stay permanently. If you still have probs, I know of more ways.

[ReCycled]

I found out long time ago that autoexec sometimes wouldn't work when I updated a new command to it. Or it might have worked but then the config.cfg file overuled it. The solution was to have that file in 2 places - c:\quake2  AND c:\quake2\baseq2. Naturally they have to be identical. It's a bit of a pain because every time I need to update it (new mouse settings for example) I need to update one and remember to copy it to the other location. But it's the only way I've found that it consistently works.
Try that....

[VaeVictis]

I found out long time ago that autoexec sometimes wouldn't work when I updated a new command to it. Or it might have worked but then the config.cfg file overuled it. The solution was to have that file in 2 places - c:\quake2  AND c:\quake2\baseq2. Naturally they have to be identical. It's a bit of a pain because every time I need to update it (new mouse settings for example) I need to update one and remember to copy it to the other location. But it's the only way I've found that it consistently works.
Try that....

just need one autoexec.cfg in baseq2 delete all other config.cfg files from mod folders, it will reference all cvars not listed in autoexec.cfg from the default.cfg in pak0.pak

that should work 100% of the time with no problems what so ever...

however, you can do something stupid inside your autoexec like the second line down "exec anotherconfig.cfg" at which point it stops executing commands in autoexec and moves over to anotherconfig.cfg... so if you plan on using autoexec to execute another config, it has to be the last line

[no_life]

That's why I like my custom coded cfg setup. There's no cfgs in every mod folder, one universal archiving cfg in "quake2/cfg" dir. It uses one single autoexec and config.cfg. Never any conflictions. If special binds are needed for a mod, I can just put a custom cfg in that mod's folder.