[cod] 1.5 CoD Upgrade has made scr_friendlyfire read only

[John Sherrit]

Yeah for me this is one of the downsides to the patch.

That and killcam.

We have our server open to the public most nights sometimes we like to 
have a practice war on it or an official match.

I used to type 

g_password
then

scr_killcam 0
scr_friendlyfire 1

amongst other things.

Now I have to set the password (that only I know)

empty the server enable voting, vote, disable voting (not allowed in 
Clanbase wars) then let everyone know the password 

I think the old way was better and wonder what the makers thought when 
doing that.

Other that than I have to say our GSP's installed the new version 
yesterday and our server running fine and has been all evening with 30 
players on it ;)

JAS

 
> 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.
> 

--