[mohaa] Server control programs for Linux

[scratch]

Again, this all sounds great, but I'm confused about the console output.  Am
I the only one who receives completely munged scoring info in the console?
And I don't mean gibberish, I mean it's simply incorrect.  I remember this
being a bug developers have had with other games using the Q3 engine, so I
assumed it was a known issue.  Also, Crow's AutoKick does not have
tk-banning enabled yet for what I assumed to be precisely this reason.  One
can't kick negative scores when the scores reported are inaccurate.  Like I
mentioned before, I have to join the game and check the score as spectator
to see what the hell is really going on -- which is particularly difficult
to do as often as necessary, especially considering I'm running multiple
dedicated ports (thank God school is back in session here... now I only have
to monitor from about 4 to 10 pm.. heh).

So, is it just me?

FYI, Shockwave, Crow's uses RCON to enforce bans simply by running an "rcon
status" at whatever interval you decide and kicking any name or IP it
recognizes as banned.  Works OK, I guess, but I'd be much more happy with
something that was native to the server and handled multiple ports.

scratch-

----- Original Message -----
From: "[-SF-]Shockwave" <shockwave at clanshortfuse.com>
To: <mohaa at icculus.org>
Sent: Thursday, September 05, 2002 11:11 AM
Subject: Re: [mohaa] Server control programs for Linux


> Hello all,
>
> I want to thank Rodney and scratch for pointing out the "clientkick"
> command.  I've been trying to use "kill" because I didn't know there was
any
> other command available.  This makes everything so much simpler!
>
> As far as determining which players are on what team, I have noticed that
> setting "developer 2" shows more detailed information, however it only
> displays the command invoked and doesn't indicate whether it was
successful
> or not.  As a test, I removed the localization file from my global
directory
> and it helps a little because it will yield a "localization error" message
> with text stating either that the join took place or the error encountered
> while executing the command.  Another idea I had was to track every kill
and
> check it against the team scores.  With the developer cvar set greater
than
> 0, every kill message is broadcast to the log.  If the team score is
> decreased after a kill that isn't a suicide, then it makes sense that a
> player killed a teammate.  I'm going to have to play around with it a bit
> and see if I can get it to work reliably.
>
> Regarding scratch's question about how banning would work, here's my idea.
> Each time a player joins, the list of players and their IP's would be
> refreshed and tabled.  I figure that a common file of banned IP's can be
> read and kept in memory for comparison.  If there is a match, the player
> would be kicked.  Since I'm already intercepting the server log output and
> have the ability to interrogate it, this should be possible.
>
> I also like the idea of changing maps and game types dynamically.  There
is
> a server variable "sv_maplist" that I have manually edited via the server
> console to make the map rotation change without forcing a restart, but I
> didn't try changing to a map that wasn't applicable to the game type
already
> set.  I'll play around with that and see what specifying a map that
belongs
> to a different gametype will do when I get a chance.  Thanks for the
> suggestion, Hammer.
>
> For the record, I haven't seen Crow King's utility but I hear that a lot
of
> people like it.  I guess I should download it and give it a try at some
> point.  I personally didn't want to be forced to use a Windows PC to
handle
> that function which is part of the reason I wanted to develop something
that
> would run under Linux.
>
> I want to be sure to say that I really appreciate all the feedback.
Anyone
> who is interested in kicking the tires will definitely get the
opportunity.
> I do have a stable version of the programs currently running on my own
> server, but as I said before they only have the limited functionality I
> mentioned earlier.  Once I smooth some of the rough edges, I'll release
them
> for testing.
>
>
> Shockwave
>
>
>