<html>
<body>
<br>
I always thought the "set" is current, no config mod.<br>
seta will modify the current running config and when you <br>
execute a write config, seta cvars will be written back to the<br>
config file, and "set" cvars will not.<br><br>
So.. "set" cvars are temporary, and "seta" can be
writtten back to the<br>
config file on write. Yes/no? Has always been a mystery to me
and<br>
I thought I had it.<br><br>
<br>
Also... What is the deal with the patch Ryan provided. Is it the
fix for<br>
the "Spectator server killer". I tried to follow the threads,
but lost it when<br>
it went to "This was for Steve only", and "I will wait
until the next "Stable<br>
release Ryan"?<br><br>
Is it fixed? not?<br><br>
Also one last thing... (Let me get it out of the system all at
once:)<br><br>
1. Since UO is an add on for COD, do I need to lead the COD 1.5 then the
UO 1.5.1?<br>
2. So the install is now - above (either COD 1.5 then UO 1.5.1
patch)<br>
Install the patch file for the patch file
Ryan listed?<br><br>
Thanks Guys...<br><br>
I don't want to update the servers yet. It would seem my servers
for UO running older 1.4.1e<br>
are still running at full most of the time, and near full... I would say
they have not upgraded<br>
their windows client... I suspect they are awaiting me to upgrade the
servers. Of which is<br>
still pending the answers here, and perhaps another day to play a bit
with it first..<br><br>
<br><br>
At 11:41 PM 12/21/2004, Geoff Goas wrote:<br>
<blockquote type=cite class=cite cite>commands to change those
cvars:<br><br>
"setkillcam"<br>
"setfriendlyfire"<br>
"setdrawfriend"<br><br>
<br><br>
On Tue, 21 Dec 2004 21:48:30 -0600, Jay Vasallo
<jayco1@charter.net> wrote:<br>
> Good to know. I will make a note of this becasue I know a client
will write<br>
> me an email "Server Broken... it says read
only..."<br>
> <br>
> Thanks.<br>
> ----- Original Message ----- <br>
> From: [MgA]RockCrusher <br>
> To: cod@icculus.org <br>
> Sent: Tuesday, December 21, 2004 9:28 PM<br>
> Subject: Re: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read
only<br>
> <br>
> Didn't work Jay. I tried seta first to see if that was the
case. <br>
> Apparently from further research I've just done, you can only
change<br>
> friendly fire upon server startup OR via VOTING. What the
heck?!?!? <br>
> <br>
> I think this must be a first, Voting is more powerful than RCON or
sitting<br>
> directly in front of the console. D'OH!<br>
> <br>
> =o)<br>
> ----- Original Message ----- <br>
> From: Jay Vasallo <br>
> To: cod@icculus.org <br>
> Sent: Tuesday, December 21, 2004 10:07 PM<br>
> Subject: Re: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read
only<br>
> <br>
> set scr_friendlyfire to "1". This means that
you cannot change via rcon<br>
> seta set scr_friendlyfire to "1" Means you can
change via rcon later.<br>
> <br>
> Well at least this is how the old q3 games worked.<br>
> <br>
> <br>
> <br>
> <br>
> ----- Original Message ----- <br>
> From: [MgA]RockCrusher <br>
> To: cod@icculus.org <br>
> Sent: Tuesday, December 21, 2004 8:53 PM<br>
> Subject: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read
only<br>
> <br>
> Does anyone know why after upgrading a CoD 1.4 server to 1.5, I am
no longer<br>
> able to set scr_friendlyfire to "1". The server says
it is read-only. </blockquote>
<x-sigsep><p></x-sigsep>
<tt>S2-------------------------------------------------------------------------------<br>
Mark J. DeFilippis, Ph. D
EE
defilm@acm.org<br>
defilm@ieee.org<br><br>
<br>
</body>
</html>