It would shut down the server through normal means due to the name, as it's
entering it in the console as separate lines. When you ban by the ID you
don't type the "name" anywhere in the console, thus avoiding the problem.
On Tue, Apr 20, 2010 at 12:24 AM, Christoffer Pedersen <
christof...@scanse
If you were to query the client with a convar every 20seconds, then if it
doesn't respond try three more times. If it doesn't send anything back after
the 3 trys kick the client (Similar to what Kigen Anti-Cheat does, if not
the same), setting sv_timeout to 120 should do the trick if the above is
i
Yes, I too have tried. You can even look in HLSW and they appear as a blank
space and usually have been on for a very long time.
On Wed, Apr 21, 2010 at 5:10 PM, 1nsane <1nsane...@gmail.com> wrote:
> You can not kick that which has no userid or name or index.
>
> On Wed, Apr 21, 2010 at 7:18 PM,
You can not kick that which has no userid or name or index.
On Wed, Apr 21, 2010 at 7:18 PM, Kyle Sanderson wrote:
> If you can remove players (kick them) without it causing the issue, this is
> easily fixable with SourceMod.
>
> Kyle.
>
> On Wed, Apr 21, 2010 at 4:06 PM, DontWannaName! >wrote:
We still experience this problem about once a day on our server with no
clear solution. 1 Ghost player slot appears and always has a 'connection
time' that counts back to 12:00AM PST -- even if the ghost player does not
actually appear until 5:00PM. There is no way to 'kick' the ghost player.
I'
If you can remove players (kick them) without it causing the issue, this is
easily fixable with SourceMod.
Kyle.
On Wed, Apr 21, 2010 at 4:06 PM, DontWannaName! wrote:
> If other plays are like me, I crash during map changes after 2-3 map
> changes. I even crashed when the overlay stopped respon
If other plays are like me, I crash during map changes after 2-3 map
changes. I even crashed when the overlay stopped responding when I was
trying to use it. Everytime this happens, it can cause the ghost issue.
sv_timeout is suppose to kick the crashed plays out and does but I dont
think the playe
There's multiple ways of causing it. A player who joins a server and crashes
might also
On Wed, Apr 21, 2010 at 6:26 PM, msleeper wrote:
> I use Sourcebans and I have the ghost player problem.
>
>
> On Wed, 2010-04-21 at 12:53 +0300, ics wrote:
> > Have a look at Claudio's post (posted after you
I use Sourcebans and I have the ghost player problem.
On Wed, 2010-04-21 at 12:53 +0300, ics wrote:
> Have a look at Claudio's post (posted after you on this list). He said
> if you would use somekind of SQL based system for bans (like
> Sourcebans), the gostplayer issue goes away. I do use Sou
http://www.prim.hostil.pl/home.php
_
Feeling the financial pinch? Check on MSN NZ Money for a hand
http://money.msn.co.nz
___
To unsubscribe, edit y
Hm,
dosnt seem to work very well, my L4D2 servers are located in Germany and right
now I have 8 players on from Japan, China, Taiwan, Malaysia etc.
- Original Message -
From: Zoid Kirsch
To: Half-Life dedicated Win32 server mailing list
Sent: Tuesday, April 13, 2010 11:19 PM
Have a look at Claudio's post (posted after you on this list). He said
if you would use somekind of SQL based system for bans (like
Sourcebans), the gostplayer issue goes away. I do use Sourcebans, maybe
that is it which prevents ghostplayers.
-ics
21.4.2010 7:45, hyp...@arcor.de kirjoitti:
>
Hi,
I've found a (partial?) workaround: clean your banned_user.cfg file and
switch to SQL bans or something like that.
Ghost players are added when a banned player tries to join the server.
You can easily verify my claim: ban yourself by steamid from rcon, then try
to join the server and you will s
13 matches
Mail list logo