setting variables via commands not dialog box

setting variables via commands not dialog box

Postby ProductArchitect » 17 Jun 2012, 12:49

First, kudos for the big variables screens -- it's great to have so much control.

But, also tiresome to have to change every time I run the game. So, I watched the output, e.g. "NAME set pistoldelay1 to 20".

Back in the game, I tried "/pistoldelay1 20" ... but get "unknown command: pistoldelay1". I also tried "/set pistoldelay1 to 20" but get a similar error.

What's the trick? And: any different if I include in autoexec.cfg or one of the other .cfg files?

Thanks,

Scott
ProductArchitect
 
Posts: 10
Joined: 26 May 2012, 00:48

Re: setting variables via commands not dialog box

Postby qreeves » 17 Jun 2012, 13:55

You're just reading it wrong, there's no "pistoldelay" but there is "pistoladelay" (attack delay) and "pistolrdelay" (reload delay). They're just regular ol' variables. Use, for example: /pistoladelay1 20
Quinton "quin" Reeves | Lead Developer, Red Eclipse | http://redeclipse.net/ | http://www.facebook.com/redeclipse.net
User avatar
qreeves
 
Posts: 1294
Joined: 17 Mar 2011, 03:46
Location: Queensland, Australia

Re: setting variables via commands not dialog box

Postby ProductArchitect » 17 Jun 2012, 16:02

Ouch! Sorry, I didn't see the -a- inside. I usually try to do my homework and not ask dumb questions ... oh well.

Scott
ProductArchitect
 
Posts: 10
Joined: 26 May 2012, 00:48

Re: setting variables via commands not dialog box

Postby qreeves » 18 Jun 2012, 01:52

Eh, it happens :P
Quinton "quin" Reeves | Lead Developer, Red Eclipse | http://redeclipse.net/ | http://www.facebook.com/redeclipse.net
User avatar
qreeves
 
Posts: 1294
Joined: 17 Mar 2011, 03:46
Location: Queensland, Australia

Who is online

Users browsing this forum: No registered users and 1 guest