[v49!]

this happened to me and i have no sprays in all the servers and my mic is disabled that from a different plugins though admins always do that and i dont like it very much and the ones they did to me were pernemante and now I have no mic :"(

[Wilson [29th ID]]

Sorry about that - I thougth 23 was simply "sprays" as I could never find a description of the message - not even in the message logger.

[Xanimos]

Put teame06's code in the first post as a .sma attachment or this is going into unapproved.

[DarkSnow]

There is already a plugin that does this, and alot more.

Restrict Commands [rc] by Substream

[teame06]

@ DarkSnow

IMO it a very bloated plugin if your only going to block sprays. It has block spray by person but still it too bloated if your only going to block sprays.

[OneEyed]

Originally Posted by DarkSnow There is already a plugin that does this, and alot more. Restrict Commands [rc] by Substream

That plugin has tons of features.

This one gets down and to the point. BIG difference.

[GHW_Chronic]

Originally Posted by Xanimos Put teame06's code in the first post as a .sma attachment or this is going into unapproved.

If you don't comply within 1 week, I will assume you do not like the idea of posting teame06's work and you this can become unnapproved. If you happen to be AFK for 1+ weeks, you'll have to repost your plugin.

[AndraX2000]

Is there a reason not to just use register_impulse(201 , "spray_block") ?
teame06's code would fire for each no-spray impulse (up to the if statement).

[SubStream]

Originally Posted by OneEyed Originally Posted by DarkSnow There is already a plugin that does this, and alot more. Restrict Commands [rc] by Substream That plugin has tons of features. This one gets down and to the point. BIG difference.

True, Restrict Commands has lots of features. I guess that means I should go and release 40 individual plugins for each command handled by Restrict Commands.

Or... maybe not.

If you're going to release a plugin that restricts spray, at least benefit from my code in Restrict Commands. Go there, copy all the code, and trim it down to just restrict impulse 201.

Restrict Commands is different because it bans by steam ID PERMANENTLY. If someone uses amx_rcplayer -=Joe=- impulse201, -=Joe=- will NEVER be able to come into your server and spray EVER again. That's a big difference.

If this doesn't at least have the option for a permanent ban based on steam id using nvault then its pretty much pale in comparison and usefulness--but that's just my personal opinion.

At the least, it would look good on your part to add permanent ability and server-wide ability--meaning a restriction for the whole server with an admin immunity option. Maybe a "spray block all in one" type plugin that can do everything Restrict Commands does, but only for impulse 201 spray. Then I could see it being worth-while to stick around. Of course my opinion doesn't matter--but I'm just trying to help. Good luck with this one.

[ImXinR]

Can someone edit this plugin to only admin can spray? Players cant spray.