[cod] 1.5 CoD Upgrade has made scr_friendlyfire read only

[Mark J. DeFilippis]

I always thought the "set" is current, no config mod.
seta will modify the current running config and when you
execute a write config, seta cvars will be written back to the
config file, and "set" cvars will not.

So.. "set" cvars are temporary, and "seta" can be writtten back to the
config file on write. Yes/no?  Has always been a mystery to me and
I thought I had it.


Also... What is the deal with the patch Ryan provided.  Is it the fix for
the "Spectator server killer". I tried to follow the threads, but lost it when
it went to "This was for Steve only", and "I will wait until the next "Stable
release Ryan"?

Is it fixed? not?

Also one last thing... (Let me get it out of the system all at once:)

1. Since UO is an add on for COD, do I need to lead the COD 1.5 then the UO 
1.5.1?
2. So the install is now  - above (either COD 1.5 then UO 1.5.1 patch)
       Install the patch file for the patch file Ryan listed?

Thanks Guys...

I don't want to update the servers yet.  It would seem my servers for UO 
running older 1.4.1e
are still running at full most of the time, and near full... I would say 
they have not upgraded
their windows client... I suspect they are awaiting me to upgrade the 
servers. Of which is
still pending the answers here, and perhaps another day to play a bit with 
it first..



At 11:41 PM 12/21/2004, Geoff Goas wrote:
>commands to change those cvars:
>
>"setkillcam"
>"setfriendlyfire"
>"setdrawfriend"
>
>
>
>On Tue, 21 Dec 2004 21:48:30 -0600, Jay Vasallo <jayco1 at charter.net> wrote:
> > Good to know. I will make a note of this becasue I know a client will write
> > me an email   "Server Broken... it says read only..."
> >
> > Thanks.
> > ----- Original Message -----
> > From: [MgA]RockCrusher
> > To: cod at icculus.org
> > Sent: Tuesday, December 21, 2004 9:28 PM
> > Subject: Re: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read only
> >
> > Didn't work Jay.  I tried seta first to see if that was the case.
> > Apparently from further research I've just done,  you can only change
> > friendly fire upon server startup OR via VOTING.  What the heck?!?!?
> >
> > I think this must be a first, Voting is more powerful than RCON or sitting
> > directly in front of the console.  D'OH!
> >
> > =o)
> > ----- Original Message -----
> > From: Jay Vasallo
> > To: cod at icculus.org
> > Sent: Tuesday, December 21, 2004 10:07 PM
> > Subject: Re: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read only
> >
> > set scr_friendlyfire to "1".   This means that you cannot change via rcon
> > seta set scr_friendlyfire to "1"  Means you can change via rcon later.
> >
> > Well at least this is how the old q3 games worked.
> >
> >
> >
> >
> > ----- Original Message -----
> > From: [MgA]RockCrusher
> > To: cod at icculus.org
> > Sent: Tuesday, December 21, 2004 8:53 PM
> > Subject: [cod] 1.5 CoD Upgrade has made scr_friendlyfire read only
> >
> > Does anyone know why after upgrading a CoD 1.4 server to 1.5, I am no 
> longer
> > able to set scr_friendlyfire to "1".  The server says it is read-only.

S2-------------------------------------------------------------------------------
Mark J. DeFilippis, Ph. D EE          defilm at acm.org
                                       defilm at ieee.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20041222/27c35950/attachment.htm>