Title: Unset Wildcards Post by: 7 on April 08, 2011, 06:11:25 AM If you use the disable_ or replace_ cvars to disable or change map items, you have to unset those cvars before you change the map or the changes will act on the next map also. If you unset only the changed cvars before calling the next map it becomes impractical to change the map rotation, because if you put one map in another slot you have to edit 4 map calls. Therefor it's more practical to unset all of the cvars and not only those specified in the previous map, because this way you can change the map rotation without side effects.
Because there are 102 disable_ and replace_ cvars, it's better to keep all the unset commands in a separate file, and exec that file before you call the next map: File: unset-disrep.cfg Code: unset disable_weapon_chaingun Map call, disabling quad only: Code: exec unset-disrep.cfg;set disable_item_quad 1;map oa_dm4 In my opinion this is a terrible cludge because you have to unset 102 cvars individually. If you could use simple completion-wildcards you could cut that down to 2 unsets and you wouldn't have to use a separate file to store them in: Code: unset disable_* I think unset wildcards could have other practical scripting purposes too. What do you think? Title: Re: Unset Wildcards Post by: Gig on April 08, 2011, 06:48:59 AM Code: unset disable_* I think unset wildcards could have other practical scripting purposes too. What do you think? Title: Re: Unset Wildcards Post by: 7 on April 08, 2011, 07:13:42 AM Sounds interesting.... maybe a little "dangerous", too? Is an unset * more dangerous than a cvar_restart? ;) Title: Re: Unset Wildcards Post by: Gig on April 08, 2011, 03:53:06 PM I don't know that command... even if I can imagine it...
Title: Re: Unset Wildcards Post by: RMF on April 25, 2011, 03:40:41 AM Please warn next time, now i had to put back a backup of my config :P
Title: Re: Unset Wildcards Post by: 7 on April 25, 2011, 01:36:20 PM Oops, sorry there. :( cvar_restart only clears your cvar variables, so not much damage should be done unless you saved your config in q3config.cfg (which is managed by OA) and exit the game.
So for other people who type \cvar_restart in the console and didn't save their config: don't exit the game because this will overwrite your config in q3config.cfg, instead type \exec q3config.cfg to get your config back. Title: Re: Unset Wildcards Post by: RMF on May 02, 2011, 12:04:12 PM I already suspected as much and quit oa by killing it from the windows task manager (kill the process in the process list, I didn't close it via the applications tab). OA still it saved it before... Oh well, different configs for every mod finally are helpful :P
Title: Re: Unset Wildcards Post by: Gig on May 30, 2011, 02:00:00 PM Tried (obviously, I backupped the file first!)... the \exec q3config.cfg trick did not work.
Title: Re: Unset Wildcards Post by: 7 on May 31, 2011, 10:53:01 AM Tried (obviously, I backupped the file first!)... the \exec q3config.cfg trick did not work. I'm afraid you're right :( I could have sworn that used to work, but q3config.cfg is synchronized right after a cvar_restart. Teaches me to write things without checking, and others to create an autoexec.cfg in the baseoa folder with their basic configuration settings in it :P |