ehm, afaik, with the introduction of Portal 2 they made all new valve titles
individual VAC bans, for otherwise they can't sell new games to those
accounts...
From: Daniel Barreiro smelly.feet.you.h...@gmail.com
To: Half-Life dedicated Linux server mailing
Yes. If you get VAC banned, bans apply only to that particular game. No
longer if you get banned in CS Source, you won't get banned in
DOD:Source and HL2DM like in the previous years.
-ics
Mart-Jan Reeuwijk kirjoitti:
ehm, afaik, with the introduction of Portal 2 they made all new valve
Ah. I missed that update. Thanks.
On Mon, May 27, 2013 at 8:18 AM, ics i...@ics-base.net wrote:
Yes. If you get VAC banned, bans apply only to that particular game. No
longer if you get banned in CS Source, you won't get banned in DOD:Source
and HL2DM like in the previous years.
-ics
Hi,
if I understood correctly we should be still able to change sv_pure at
runtime, provided we set it at command line.
Is that assumption still valid or currently the only way to change it is
from command line and no more from rcon/console?
___
To
I don't think it has changed. You CAN change sv_pure after boot, provided
that you start with it on.
On Tue, May 28, 2013 at 2:55 AM, Marco Padovan e...@evcz.tk wrote:
Hi,
if I understood correctly we should be still able to change sv_pure at
runtime, provided we set it at command line.
You have to start with at least sv_pure 1 at start, then you can change it
to whatever you want at runtime.
I still think sv_pure 1 should be the default at startup, it seems it's
sv_pure 0 now. If that's changed to 1 everyone can set their pure setting
at runtime in their config, instead of
https://github.com/ValveSoftware/Source-1-Games/issues/198
and
https://github.com/ValveSoftware/Source-1-Games/issues/216
2013/5/27 Rudy Bleeker rblee...@gmail.com
You have to start with at least sv_pure 1 at start, then you can change it
to whatever you want at runtime.
I still think
yeah, I've -sv_pure in command line without parameters... I can change it
using rcon to any value I want, but when connecting to the server the
client always report that the server is running sv_pure 2 ... even if we
set it to 0 in console (and running sv_pure in console confirms it is set
to 0)
Thanks,
This has managed to reduce the number of spikes (less frequent) and reduced CPU
usage quite considerably (floats at 45-60% with 32 players, compared to 80-90%)
so spikes don't have much of an impact. Why the spikes still occur is beyond me
- at rare times it would just spazz and spike
I thought that was only post-Left4Dead that games were treated individually,
but previous games such as those you listed were still in groups. When did the
change to individual-game bans include pre-Left4Dead Source games?
On 27/05/2013, at 10:18 PM, ics i...@ics-base.net wrote:
Yes. If you
Well this is what valve has to say about vac bans:
https://support.steampowered.com/kb_article.php?p_faqid=589
It doesn't really say if bans are per game or not.
But it does say that if you get banned from any previous source engine game
you will lose all your tf2 items.
On Mon, May 27, 2013
I think that if it's Orange Box (TF2, CSS, etc) you're banned for
Orangebox, but if it's a modified engine (L4D, CSGO, etc) than it's
separate.
On Mon, May 27, 2013 at 5:58 PM, 1nsane 1nsane...@gmail.com wrote:
Well this is what valve has to say about vac bans:
I thought about making an entirely new post but we'll see how much
attention it gets in this one first.
We've also been experiencing some other behavior that I've just noticed in
the past few months. It's player warping. When you watch them after you're
dead they seem to skip several flames and
There is no orangebox anymore. All games are separate builds, but still
are build from same source code. Bans are per game, not per engine. I'm
not sure when this happened but it's beem 2-3 years already.
-ics
Daniel Barreiro kirjoitti:
I think that if it's Orange Box (TF2, CSS, etc) you're
14 matches
Mail list logo
