Author Topic: "say" command nonfunctional after improper cfg  (Read 3260 times)

KillerWhale

  • Spam Killer
  • *
  • Posts: 469
  • Turrets: +63/-26
"say" command nonfunctional after improper cfg
« on: August 03, 2009, 03:28:55 pm »
This morning, my neighbour who plays Tremulous tried to create a cfg to store her clan's bind, thereby allowing her to free up a key.
She used "seta say" instead of "say" in the cfg.
"say" got broken.
I got called at 7:20AM to fix this broken "say".

The obvious route in my mind was just "\reset say", but that didn't work.
I tried a few more things, such as making a cfg that's just "seta say", and nothing has really worked.

Am I going to have to reset the autogen/replace the client for such a simple thing as "seta"ing the "say"?


Info that is mostly irrelevant:
Tremfusion 9_r3
Linux Mint 32-bit

Bissig

  • Posts: 1309
  • Turrets: +103/-131
Re: "say" command nonfunctional after improper cfg
« Reply #1 on: August 03, 2009, 03:40:25 pm »
Find any instance where it might be bound and also look in the file autogen.cfg and autoexec.cfg

You could of course backup the config file(-s) and ingame do a "reset cvars" or whatever the command was called.

David

  • Spam Killer
  • *
  • Posts: 3543
  • Turrets: +249/-273
Re: "say" command nonfunctional after improper cfg
« Reply #2 on: August 03, 2009, 05:43:16 pm »
remove that line from autogen.cfg and all should work.

I thought commands overrode cvars, and I seem to recall their being talk of adding a /print because they did.
Any maps not in the MG repo?  Email me or come to irc.freenode.net/#mg.
--
My words are mine and mine alone.  I can't speak for anyone else, and there is no one who can speak for me.  If I ever make a post that gives the opinions or positions of other users or groups, then they will be clearly labeled as such.
I'm disappointed that people's past actions have forced me to state what should be obvious.
I am not a dev.  Nothing I say counts for anything.

KillerWhale

  • Spam Killer
  • *
  • Posts: 469
  • Turrets: +63/-26
Re: "say" command nonfunctional after improper cfg
« Reply #3 on: August 04, 2009, 06:27:47 am »
remove that line from autogen.cfg and all should work.

Worked beautifully, thank you.

Hopefully I won't have any more early-morning wakeup calls to fix a Tremulous client. :P