The difference between SET and SETA?

Post by **nightwing** » Mon Oct 31, 2005 1:29 am

Hello all,

What seems to be the difference between having 'set' instead of 'seta' before a console command?

I tried them both and they seem to do the same thing. Thanks in advance.

Post by **nightwing** » Mon Oct 31, 2005 2:18 am

Thanks riddla

Post by **xchaser** » Mon Oct 31, 2005 3:03 am

set sets a cvar
seta sets a cvar and flags it as archive
sets sets a cvar and flags it as server info
sett sets a cvar and flags it as tool
setu sets a cvar and flags it as user info

Post by **NitrousFlare** » Mon Oct 31, 2005 4:13 am

you nerd

Post by **nightwing** » Mon Oct 31, 2005 4:50 am

wow that's some good info xchaser. Thank you

Post by **Oeloe** » Mon Oct 31, 2005 10:35 am

In Q3, 'seta' is usually used for main config settings (binds, graphics etc. ) and 'set' is used for scripts because scripts don't need to be archived (config files with the scripts are loaded every time you startup Q3 when you use autoexec.cfg). Q3 doesn't archive variables you declare with set; only cvars you declare with seta are archived or when you changed them in the console.

I don't know Q4 if archives everything, could be...

Post by **hemostick** » Mon Oct 31, 2005 2:14 pm

seta is set with a Mario Accent.
(i.e. "itsa me, Mario !")

Post by **Foo** » Mon Oct 31, 2005 2:16 pm

xchaser wrote:set sets a cvar
seta sets a cvar and flags it as archive
sets sets a cvar and flags it as server info
sett sets a cvar and flags it as tool
setu sets a cvar and flags it as user info

Nice.

What is the end product of these, though.

I'm guessing 'seta' makes the cvar get written into the .cfg file. sets makes it get sent to the master server/sent in query. setu and t.... I dunno

Post by **xchaser** » Mon Oct 31, 2005 9:49 pm

I am not a nerd its a easy copy and paste from upset chaps:
http://ucguides.savagehelp.com/Quake4/fullcmdlist.htm

LOL