[mohaa] Admin tool ready for testing

[[-SF-]Shockwave]

Hey Warren,

> It is.  I failed to add the dir in mohaa_admin to reflect the correct
> path.  It's Monday, you see.  I expect it'll work fine when the server
> restarts (or does this reload every level?... I'll look at that).
>

Command line options are checked only at the time the admin tool is
launched.  Unfortunately you'll have to kill and restart the server to
change them because they aren't part of the configuration file.  However, if
you do manage to put the ban.cfg file where the server expects it to be, it
will begin reading and processing it the next time a player joins and you
won't have to shut it down,

> Just to clarify, you are suggesting that the BAN_MSG_START and _END be
> commented out of the config if someone does *not* want customized
> messages, right?
>

That's correct.  If you execute "mohaa_admin --defaults" on the command
line, it will show you what the default ban message components are among
other things.  If this is cool, just be sure to comment out the
configuration file options and you're all set.  I made the start and end
message variables to give people a little more artistic license with the
message.

> Cool.  Not a problem at all.  I think we're all pretty confortable with a
> simple text exit, anyway.
>

If everything continues to run smoothly, I'll implement the ability for
clients to add entries to the ban.cfg file on the fly.  I would be
interested in hearing how you and others would like it to operate.  That
functionality goes along with another idea I wanted to try:  banning
foul-mouthed bad sports.  The last time I was monitoring my server, some
player was using the map exploit for Destroyed Village.  He told a bunch of
people who told him to stop to F*** off.  When I told him to "please watch
the language", he said "F*** you too".  Needless to say I exercised my admin
privileges and booted him, but it left me thinking it might be interesting
to have a language filter, fed by a user defined external list of bad words,
that could temp/perm ban players after X number of offenses.  Multiple
levels of warning messages could also be employed, possibly increasing in
severity with each subsequent infraction...

Anyway, I'm glad to hear that things are working better for you.  Keep me
posted!


Shockwave


----- Original Message -----
From: "Warren Woodward" <warrenw at xmission.com>
To: <mohaa at icculus.org>
Sent: Monday, September 09, 2002 7:05 PM
Subject: Re: [mohaa] Admin tool ready for testing


> On Mon, Sep 09, 2002 at 06:35:13PM -0400, [-SF-]Shockwave wrote:
> > The first thing I would do is check to see if you generate a " has
entered
> > the battle" message in the server output when you connect.  If not,
ensure
> > that you have the "developer" cvar set to either "1" or "2" and see if
that
> > fixes it.  It's pretty easy to spot because if this is set correctly,
every
> > time a player joins a status display gets printed to the output
> > automatically.  If this message isn't being generated, then that's
what's
> > wrong.
>
> It is.  I failed to add the dir in mohaa_admin to reflect the correct
> path.  It's Monday, you see.  I expect it'll work fine when the server
> restarts (or does this reload every level?... I'll look at that).
>
> > I did find something that I do want to mention.  The default server
> > configuration file "mohaa_admin.cfg" doesn't have the BAN_MSG_START and
> > BAN_MSG_END options commented out.  In this configuration you will only
see
> > the player's name print if a ban message is broadcast.  This is because
the
> > player name is sandwiched between these two variables in order to
generate
> > custom ban messages.  To get the default ban message to print correctly,
> > simply comment out the two options in the server configuration file by
> > placing a single "#" in front of each.  I've already made this change to
the
> > default server configuration file so this won't be an issue in the
future.
>
> Just to clarify, you are suggesting that the BAN_MSG_START and _END be
> commented out of the config if someone does *not* want customized
> messages, right?
>
> > There is no method for adding an IP to the ban.cfg file without manually
> > editing it ...yet.  That is one of the things I wanted to add but I
decided
> > to table it for this initial release.  The client doesn't have anything
to
> > do with the ban.cfg file at this point.  It is handled exclusively by
the
> > server monitoring process and is re-read with each player connection to
the
> > server.
>
> Cool.  Not a problem at all.  I think we're all pretty confortable with a
> simple text exit, anyway.
>
> >
> > I have tested this on my own RedHat 7.2 server and have seen it tested
on a
> > RedHat 7.3 box and a <Ctrl><C> effectively cleans up everything.  Let me
>
> And a few minutes after I sent this, I figured that out.  And that the
> tail is envoked by the admin for use.  I'm here now, you can start class.
>
> > Keep 'em coming, Warren!
>
> I can't.  You're answering everything.  I"ll be toying more tonight when I
> can concentrate and test more.
>
>
> --
> warren woodward
> XMission DSL
> Domo/Mailman
> warrenw at xmission.com
> (801) 303-0819
> (877) XMISSION
>
>
>
>