[mohaa] multi ports

Mazzic mazzic at yahoo.com
Thu Sep 12 00:18:14 EDT 2002


I'll just throw this out there.  I added one feature to my program that
serves two purposes...it was Name Protection.

I added a file with Nicknames and their IP's.  So that no one was able to
impersonate certain named individuals (provided they had something like
cable modem which pretty well gives you a consistent IP).

So simply by added a name that you wish to ban in that list, with a bogus
ip..such as 0.0.0.0  .. since the ip would never match, the player with that
name would get kicked.

So I had added like

console,0.0.0.0

So that no one could come into the game named console..

-Mazzic


----- Original Message -----
From: "[-SF-]Shockwave" <shockwave at clanshortfuse.com>
To: <mohaa at icculus.org>
Sent: Wednesday, September 11, 2002 6:07 PM
Subject: Re: [mohaa] multi ports


> Hi Warren,
>
> > My primary reason on banning by name is to keep certain words and
phrases
> > taboo.  You know how it is, you spend all this time running a good,
clean,
> > fair server that everyone enjoys, and suddenly someone named "CuntFace"
> > joins and kinds throws all your work out the window.  There are also
some
> > clan-based idiots I like to keep away.  For example, there is some group
> > named (kor) that likes to join as a bunch and start mowing down their
> > teammates.  With CrowKing's, I simply entered (kor) as a banned name,
and
> > that way they at least can't play as a group which seems to be
> > discouraging enough.  I just found the name banning to be useful for
> > things like this.  Thought I'd toss it out there for ya.
> >
>
> You make an excellent point.  I had thought about possibly adding the
> ability to ban players like this, but I wasn't sure how far I should go
with
> it.  I could theoretically allow a simple case-insensitive string match,
or
> I could go to the other extreme and try to implement a more robust pattern
> matching capability.  I'd like to get some more feedback on what kinds of
> matches you would like to have the program make.  Should case make a
> difference?  Should case sensitivity be an option?  Should there be
options
> for matching only at the beginning or end of a player name?  Should
options
> be applied to individual entries or for the file as a whole?  Let me know
> what would work best for you.  If you can give me a few more details, I'd
be
> happy to add that functionality.
>
> > One other side note, Crow's also has the ability to auto-kick nick
> > stealers, which is really nice, too.  Something you might want to
consider
> > for future releases.
> >
>
> I'm not sure if I understand the term "nick stealer".  Could you explain
> this a little further?
>
> Regarding the multiple occurrences of status messages to the client, I
have
> thought of a way around this and am currently working on a better method.
> It's going to require that I tweak the way the server processes operate
with
>  each other, but I think I can stop the spamming of status messages.  As
far
> as the spamming of extra kick messages after the level reloaded is
> concerned, that is a new one to me.  I've seen it spew out a single extra
> kick message on occasion.  It usually happens when the server is initially
> launched after I have just killed it testing ban message printing.  I
always
> figured it was unflushed data and never gave it much thought.  The fact
that
> it was issued more than once to the console output is a real surprise.
I'm
> going to take a closer look at the logic that handles this and see what I
> can do.  Thanks for the additional info.
>
> > I suppose a newbie step-by-step walkthrough would help people...
>
> It's already in the works.  Please don't hesitate to offer any
suggestions.
> Sometimes what I think is straight-forward isn't to someone else.  An
> external perspective would be appreciated.
>
> > Again, this rules.  I'm really pleased with it.  We have a slew of other
> > MOH servers here at XMission, and I'm turning the other admins onto this
> > tool.  They're pleased with the features in this early release.
> >
>
> Excellent!  Make sure to tell them to send any feedback they have my way.
> I'd even love to see a prioritized list of desirable features/fixes so I
can
> align my programming efforts with administrative needs.  Thanks again for
> all your help and patience.  It's helped a lot.
>
>
> Shockwave
>
>
> ----- Original Message -----
> From: "Warren Woodward" <warrenw at xmission.com>
> To: <mohaa at icculus.org>
> Sent: Wednesday, September 11, 2002 12:26 PM
> Subject: Re: [mohaa] multi ports
>
>
> > My primary reason on banning by name is to keep certain words and
phrases
> > taboo.  You know how it is, you spend all this time running a good,
clean,
> > fair server that everyone enjoys, and suddenly someone named "CuntFace"
> > joins and kinds throws all your work out the window.  There are also
some
> > clan-based idiots I like to keep away.  For example, there is some group
> > named (kor) that likes to join as a bunch and start mowing down their
> > teammates.  With CrowKing's, I simply entered (kor) as a banned name,
and
> > that way they at least can't play as a group which seems to be
> > discouraging enough.  I just found the name banning to be useful for
> > things like this.  Thought I'd toss it out there for ya.
> >
> > One other side note, Crow's also has the ability to auto-kick nick
> > stealers, which is really nice, too.  Something you might want to
consider
> > for future releases.
> >
> > Now the other thing.  I may have been unclear.  What seems to be
happening
> > is that the admin tool appears to randomly send multiple commands to the
> > console.  When I said it then "locks up", I was referring specifically
to
> > the "status" command it sends at regular intervals, which occasionally
> > spews out in 5 to 10 immediately successive executions (so the console
> > suddenly gets pages of status) and then stops sending that command
> > altogether for an undetermined period of time.  Perhaps a better example
> > is something I observed last night.  "MadIrishman" was pouring lead into
> > his teammates at the spawn point, so I took the chance to test out the
ban
> > in public, which worked perfectly.  And I had altered the Kick message
in
> > the admin file (not the config)to say "is now a banned l0ser.".  When
the
> > level reloaded and he was removed, this happened:
> >
> >
> > broadcast: print "MAD IRISHMAN was kicked\n"
> > Going to CS_ZOMBIE for MAD IRISHMAN
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> > broadcast: print "^Bconsole: MAD IRISHMAN is now a banned l0ser.\n"
> >
> > 12 instances of it.  Which, frankly, was kind of cool, because everyone
in
> > the server definately saw it. :)  But still, it's a good representation
of
> > the way these commands are getting send in multi-sequence to the console
> > for some reason.  I did find two instances of the client and the tail
> > running during these periods, but can't observe a direct correlation
> > between this.
> >
> > Anyway, I can provide whatever specifics you would like.
> >
> > As to the installation, nah, I think it was pretty straightforward.
Lord
> > knows I was having a busy day, and the half-attention I could provide to
> > the project was 80% responsible to my misunderstandings of it's
function.
> > I suppose a newbie step-by-step walkthrough would help people, but
outside
> > that I really have no suggestions that you aren't probably already
> > considering.
> >
> > Again, this rules.  I'm really pleased with it.  We have a slew of other
> > MOH servers here at XMission, and I'm turning the other admins onto this
> > tool.  They're pleased with the features in this early release.
> >
> >  --
> > warren woodward
> > XMission DSL
> > Domo/Mailman
> > warrenw at xmission.com
> > (801) 303-0819
> > (877) XMISSION
> >
> >
> >
> >




More information about the Mohaa mailing list