Sniper control v1.2
 

Sniper Control 1.2
This plugin is slightly different from other 'sniper control' plugins that may be out there... Simply put, plugins that force you to auto drop the sniper rifle if the set limit has been reached are exploitable, and you can easily get around them...

So, I've developed this plugin that does not let you even pick up the sniper rifle if the limit has been reached.

All sniper rifles are included in the 'checking'
a special #define is in the code for including or excluding the scout from the count, but the AWP and auto snipers are included...

This plugin requires the engine module to be in use on your server...

Test it out, it's still in beta stages so PLEASE report any bugs to this thread... ( sorry if the code is slightly messy, i havn't had time to clean it up )

There is a config file needed ( or, rather, recommended for this plugin ):
it goes in 'addons/amxx/configs/' and is called 'sniper_control.cfg'
cvars to use in this version ( 1.1 ):

• mp_sniper_control // 1 = on, 0 = off
  sc_max_snipers_t // number of sniper rifles for the T team
  sc_max_snipers_ct // number of sniper rifles for the CT team

There is also an optional disabled maps file
If you choose to use this file simply create a file called 'sc_disabled_maps.cfg' in '/addons/amxx/configs/' and list maps in which you would like the plugin to be disabled.

* NOTE: if you DO use 'sc_disabled_maps.cfg' then you must add mp_sniper_control 1 to your 'sniper_control.cfg' file in order for it to re-enable the plugin on non-disabled maps.
Enjoy, and remember to PLEASE report bugs to this thread.. Thank you :)

/ - Changelog -------------------------------------- */
v1.0
Initial public release
v1.1
added per-map disabled via 'sc_disabled_maps.cfg'
de-hardcoded config file paths from plugin
v1.2
fixed issue with scouts being blocked with INCLUDE_SCOUTS 0

Nice

P.S

Do you plan on releasing your grenade control plugin, that was really usefully for smoke nade spammers :)

Yeah, I'll work on converting that over to amxX and post it up, as well :)

~will

wow I just requested this plugin and right after I browse here and find it :D

Is it just for the awp or all sniper rifles? I'll read the sma but updating the plugin definition would be nice too as most ppl could assume awp only even if it says sniper rifle :)

EDIT: ok it's all sniper rifle :D ..including scout! :shock: haha very good work I test it on my 24 slots pub and report back ASAP. Can i simply strip down on line 35 if I dont want to include the scout in the sniper limit?

EDIT 2 : OMG dude this plugin totally rocks there's a define to include the Scout or not! forgive me I was just so exited to find such a plugin I didn't read the whole sma :oops:

I played for a 2-3 hours tonight and didnt noticed any glitch, seems to be working very well :D

I gave it a 5/5 usefull!

possible to add on the 'sniper_control.cfg' or other files the possibility to disable this plugs for map awp_ or other map who use only sniper rifles ?

yes, that's a possiblity - or there is a plugin ( i don't know if it's been swotched over to amxX yet ) that lets you use per-map configs ... I'll look into adding support to disable for maps within a config file..

~will

yes i find this plug for map cfg ...

but if your plug can recognize awp_(map) or scout_(map) or in general all maps who dont begin by cs_ de_ as_ etc ... this can be very usefull :wink:

Plugin updated
per-map stopping of the plugin is now possible:)

nice
 

nice, now when I play awp_map I dont have to go through the hassle of changing everything!

thx i add this plug on my GS :wink:

it snt possible to check the beginning of a name map for find cs_ de_ as_ and also enable autamicaly the plugin only for this map ?

more usefull no ?

Sure, it's possible - but with the config you have more control as a server admin.

you get alot more control, but the de_ cs_ as_ thing, could be a nice idea also :)

yep, you just have to add the prefix name map on a cfg fil so ...

I have more than 100 maps ... it s more usefull for me if i have just to add cs_ and de_ or as_ in a file :wink:

in more if you forget to add you map awp actually ... => crash :lol:

well just copy and paste all the maps you got by doing a "dir *.bsp /b >sc_disabled_maps.cfg'" in your maps directory and delete those where you need the plugin to run plus the .bsp extension ...that isnt too much assle in my opinion and more flexible.

although automatic disabling on awp_ maps would be nice.

why not include the two ideas ?

Add cvar for chose if we use listofmapsforbiden.cfg or prefixmapenableplug.cfg ...

For the next release I can modify it so it will check on partial and full mapnames in the .cfg file....

small update: removed hardcoding of config file paths ...

has anything changed since you added the per-map config in the sniper control part of the code?

I dont want to update to the per-map version of your plugin because I already uses map_configs by JustinHoMi (available for AMXX).

...and just to be frank, I dont see any need to complexify your plugin with the per-map config as most ppl will already run JustinHoMi plugin to remove freezetime and other cvars on awp map (and other custom "fun" maps) and all that is needed to comply with your plugin is to put the already available cvars in your first release. My two cents :wink: :)

Now the real question for you, I used the on my compile but just yesterday a player complained he couldn't buy a scout because of team limit... now I just commented on line 309 is that correct? Will that fix this possible problem?

the per map config thing is just for people looking to use one plugin - i use justinhomi's plugin too, but if people don't want to then using the one in here will help them out..

ah crap, that was a small error in the code on my behalf - if you grab the new version if you have INCLUDE_SCOUT 0 then it should work properly... Ther reason it wasn't working was because i still had it checking for scouts on vgui menus because i forgot to put it inside my precompiler if statement:) Sorry about that :([/code]

sorry if you downloaded this for the scout fix yesterday (april 7 ) i did something screwey when i was updating the thread and nothing new got uploaded....

So, the REAL fix is posted now - again, sorry about that..

NP :)

I have a question, on fy_iceworld if I put sc_max_snipers_t 0 and
sc_max_snipers_ct 0 in my custom map config (JGHG), will that make it impossible for people to use the awp as I would expect?

it will still allow the players to pick up the snipers, because i havn't coded that support into this yet - that would require checking for a different entity type ( armoury_entity )....

I'm going to code that in, as well as a limit per type of sniper rifle + the overall limit... it'll offer a bit more control over stuff :)

possible to add shield restriction with snipe restriction ?

both needs restrictions :wink:

my friend ryan did up a shield restriction plugin for amx ( not amxX ) I'll see if i can get him to port it over :)

When do you think this update will be ready? Also, the shield limit plugin.. I've been waiting a long time for these 2 as you describe them here.

I was going to start work on that tonight, actually - I've been pretty busy with classwork - 300+ page group reports suck $#1T!!!!!!!!!!!!!!!!!!!!!!!!!!

But yeah, I'll start work/testing on it tonight - and maybe, it'll be quick n' easy and up/out by tomorrow ( april 15 , 2004 )

Thanks Will..

Also, don't forget to talking to your friend Ryan to port over the shield plugin :wink:

I keep getting this error and then the server crashes

L 04/15/2004 - 14:46:59: [AMXX] Run time error 4 on line 142 (plugin "sniper_control.amx")

Good job , I myself am not a fan of the Awp.

hmm, ok - I'll look into that right now...

~will

I believe runtime error 4 is an array index out of bounds error, and I think my problem there was not taking into accoutn all the weapon id's possible in CS? Not sure, anyway - i increased the array size... this *should* fix the issue, but im still looking into any other possible causes...

bugfix uploaded - no new version number, still working on per-sniper blocking :)

Ok, I spoke with BAILOPAN and he told me that there's an issue with get user weapons, but he also told me about a workaround - that was the problem. it shold be fixed now :)

Thanks, I'll try again

Tried to compile the plugin and got the following

really sorry about that, I had changed the array sizes trying to fix it ( before i spoke with BAILO ) and i forgot to change them back ... should be good now... really sorry about that

No need to be sorry.. mistakes happen. I appreciate you making the plugin and as soon as I get the shield plugin, I'll be set :)

Are you going to enable checking to see if the max sniper weapons are already in hand at round start that it will disable the team from buying additional sniper rifles instead if making them waste money just to throw the weapon away.

can someone fix download for .20 version? thanks.

plz upgrade for latest amxmodx