AWPRoundLimit

[Rabbi Bob]

As mentioned on FR25's boards, here is the zipped up .sma for Meathook's AWP limiter.  After looking at it, it appears coded to >5, but appears fair enough to alter.

AWP Round Limit

Meat was online but apparently AFK when I pulled it, was going to ask if he had a readme for it.  If needed, I'll ask him later on.

What it does:  Restricts awm and autosniper weapons to the lowest team score when a team goes to +5 wins and beyond.  We've run it in this fashion for near 8 months now with great success on our Pizza & Beer server.  As mentioned, it looks changeable to fit the scheme here with some thought.

Cheers

[Dr Sadako]

Cheers RabbiBob, I will alert the überadmins.  

[DuVeL]

Thanks Rabbi but I hoped the CoFRlads would put it on aswell. On our server we have the rule that if a loosing team is down by 4 they can buy AWM's autosnipers. It doesn't happen very often but once in a while it does.

[Rabbi Bob]

I agree and one can only make friendly suggestions where one is a guest  :lol:

I was tripped up once and politely warned ("hey..it's Rabbi with awm!!") based on the slight difference between our rule base, but after reading the TCS posts and other threads I respect the direction that you take here with the awm.

That being said, I still find myself buying it on our server if it is available and I feel I can spare the cash, but I seem to no longer feel the need to clutch it desperately throughout the entire round, discarding it along the way for rifle or smg.  There may be hope for me yet, who knows...

I also have a logscanner that I had been working on over the past year.  It requires PERL to run and the monthly filing at this point has to be done manually (i.e. seperate the logs on June 1 from May 30 before scanning), but I have hopes of coding a seperator this summer.  Why a logscanner?  The primary reason was an excuse to learn some PERL.  I'm a n00b at PERL and if anyone here codes it, there may be some strain eyesockets if you ever see the code  :lol: .  The secondary reason is that we try to run a fairly tight ship in regards to a 'family' environment at FoCA as far as server rules (TW, TK, language).  Many of the members have kids who play CS, so they like to know that there is a safe place their child can go and play.  Finally, basically everyone likes to see what led up to a kick or ban, but obviously we aren't giving the logs out (rcon passes, admin_talk, etc).

So Bob got geeky and the end result looks like this:

http://www.rabbibob.com/~foca-cs/logs/may2004/

I would be more than happy to let someone see/test the beta.  It is coded more towards AMX, but does have some basic clanmod and adminmod search strings.  The current package includes an FTP get script, a scan script and an FTP send script for hosting the results on the web.

I also had a banned.cfg joiner between multiple servers under the WONID system written in C++, but I haven't cared to recode it for STEAMID (silly colons...)

[GhostMjr]

gj rabbi! i think we have all had enough of awp users who r on the winning teams with and even greater advantage. This shud at last put an end to it!

[Norm]

Agree with you rabbi about needing to run a tight ship,my daughter plays on both cz and cs servers that I run(she also showing me how to admin it,lol).Most of the profanity I here is from kids tbh.The awplimiter is a really good idea ,as awp can destroy a flowing game as attacking team become super defensive(camping),then everyone gets board and leaves,lol.