[TnTSCS]

DESCRIPTION:
This plugin allows you to set a maximum number of kills a player can get using a sniper rifle. Sniper rifles are grouped together as AWPs and AUTOs - you can set the Scout as a sniper rifle if you want as well.

When a player reaches their maximum sniper frags, they will be forced to drop their sniper rifle and equiped with the weapon you specify in the config file. You can set the replacement to "none" if you don't want to give them any weapon when they reach their sniper frag limit. Just be sure to use primary weapon_names

The restriction for the player will remain in effect until the map changes or they disconnect and reconnect to your server.

This plugin is also compatible with CS:S DM

Changes in 1.6.1 add ability to turn off advertisement of plugin to joining players, ability to advise players via hint chat regarding sniper kills left and pending removal of sniper rifle (if you use Drop On Round End CVar).

New in 1.6.3.2 is a cooldown period where you can optionally set a number of rounds a player must wait before being allowed to use sniper weapons again after they've been restricted. No longer need the sound.txt, instead set the sound file you want to use with the new CVar (sm_SniperRestrict_sound which is defaulted to buttons/weapon_cant_buy.wav).

In-Game Commands:
sm_snipers (!snipers or /snipers if using default triggers)
- Will display the current status of the player's sniper kills

Overrides

"donot_restrict_snipers"
- Currently set to ADMFLAG_CUSTOM2 - players with this are immune to the restrictions this plugin imposes.

"sm_SniperRestrict_chat"
- Currently set to ADMFLAG_CHAT - players with this receive admin messages when other players reach their sniper limit.

Use sourcemod\configs\admin_overrides.cfg to set the above to whatever flags you want.

CVars

"sm_SniperRestrict_cooldown" = "0" min. 0.000000 max. 25.000000
- Number of rounds that must pass before a player is allowed to use snipers again after being restricted. Use 0 to not use this feature.

"sm_SniperRestrict_sound" = "buttons/weapon_cant_buy.wav"
- Path and file name of sound file to use for restriction sound relative to sound folder.

"sm_SniperRestrict_snipers" = "weapon_awp weapon_g3sg1 weapon_sg550"
- List of weapons to consider sniper rifles, seperate weapon names with a space

"sm_SniperRestrict_advise" = "1" min. 0.000000 max. 1.000000
- Advise to players how many remaining sniper kills they have used?

"sm_SniperRestrict_advertise" = "1" min. 0.000000 max. 1.000000
- Advertise this plugin to joining players?

"sm_SniperRestrict_droproundend" = "0" min. 0.000000 max. 1.000000
- Drop the sniper weapon for the player who reached their limit at the rounds end?

"sm_SniperRestrict_notifyplayers" = "0" min. 0.000000 max. 1.000000
- Notify all players when another player reaches their sniper kill limit?

"sm_SniperRestrict_useupdater" = "0" min. 0.000000 max. 1.000000
- Utilize 'Updater' plugin to auto-update Sniper Restrict when updates are published?
1=yes, 0=no

"sm_SniperRestrict_maintainrestrictions" = "0" min. 0.000000 max. 1.000000
- (0,1) Maintain restrictions until map changes? If set to no (0) then players can just reconnect to be able to purchase snipers again.

"sm_SniperRestrict_restrictforbots" = "1" min. 0.000000 max. 1.000000
- (0,1) Restrict applies to bots as well as hunans?

"sm_SniperRestrict_destroyweapon" = "0" min. 0.000000 max. 1.000000
- (0,1) Destroy the Sniper weapon the player is holding when they reach their MaxSniperKills?

"sm_SniperRestrict_adminnotify" = "1" min. 0.000000 max. 1.000000
- (0,1) Notify admins when a player reaches their sniper kill limit - default is yes (1)

"sm_SniperRestrict_adminnotifycooldown" = "1" min. 0.000000 max. 1.000000
- (0,1) Notify admins when a player finishes their cooldown after being restricted?

"sm_SniperRestrict_maxsniperkills" = "5" min. 0.000000 max. 100.000000
- (0 to disable, number) Sets the max number of kills allowed with Snipers, per map

"sm_SniperRestrict_sniperreplace" = "weapon_scout"
- (weapon_name, none) Weapon to equip player once they've reached their MaxSniperKills limit

REQUIREMENTS:
Sourcemod 1.4+
SMLib (if you want to recompile yourself)
Updater if you want to automatically receive updates to this plugin. BTW, leave the SMX in the root of PLUGINS folder until issue is resolved with Updater
SDKHooks

CREDITS:
dalto and RedSword for weapon drop stuff and gamedata file

Dr!fter and RedSword because I learned a lot looking at their plugins

berni for SMLib

GoD-Tony for Updater

I know there are probably more because I looked at a LOT of different code and started going crossed eyed

TO DO LIST:
DONE - Clean up code - there is a lot of redundance in it right now, but the plugin works good - tested it on a production server

DONE - Add code to check if they bought a restricted weapon and refund their money if they did (or block it entirely)

DONE - Add translation file so it's not hard coded in english. Update - still need to get to this

Maybe add a higher number of allowed sniper kills for those with reserved status (configurable flag and number of sniper kills)

Known Bugs:
FIXED - The sound doesn't download - I'll fix that this weekend - it works now, thanks to Dr!fters :)


You'll have to download the attached SniperRestrict.smx file because the web compiler won't compile the .sp file due to smlib and updater includes. Also, the zip files has the needed gamedata file and sound file and translation file.

INSTALLATION:
- Put SniperRestrict.smx in your addons/sourcemod/plugins folder
- Put wpndrop-cstrike.games.txt in your addons/sourcemod/gamedata folder
- put sound.txt in your cstrike\addons\sourcemod\configs\restrict folder
- Put restrictedweapon.wav in your sound/admin-plugin/actions folder (don't forget to put it on your fast download folder if you have a FastDL server)
- When you start up the plugin it will create a config file in cstrike/cfg/sourcemod folder called SniperRestrict.plugin.cfg - edit to your heart's content - just don't set ScoutIsSniper to 1 and set replacement weapon as the scout as well.
- If you change the sound file, make sure you put change the addons/sourcemod/configs/restrict/sound.txt file as well. Just take note that the sound file listed there is also with the weapon_restrict plugin.

Also in attachments is the old version just for historical purposes... Updated to include old files for 1.0 and 1.2c

CHANGE LOG

Version 1.0
- Initial release

Version 1.1
- Fixed when player purchased restricted weapon. It now refunds them the money
- Fixed the sound file not being downloaded by clients

Version 1.2c
- Cleaned up the code quite a bit - now it's not so cluttered

Version 1.3
- Added a setting and config entry to destroy the weapon when MaxSniperKills is reached. This was done by request (Iggy). When upgrading to this, you should let the plugin create a new config file.

Version 1.5.5
I've skipped a few version just because I haven't been releasing some of the changes I've been making. I wanted to make sure they were all done before I released a new version.

- Updated method of dropping weapons to use CS_DropWeapon (hence the requirement for Sourcemod 1.4). This hopefully fixes the weapon drop issues for CSSDM
- Started using the CS_OnBuyCommand to handle the weapon purchasing for restricted weapons
- Changed from hooking item_pickup to using SDKHook_WeaponCanUse (SDKHooks is now required)
- Removed CVar DestroyPickedUpWeapon since SDKHooks will not allow a player to pickup a restricted weapon
- Added functionality to maintain the sniper restriction for players for the entire map even if the player disconnects and reconnects. The new cvar is sm_SniperRestrict_MaintainRestrictions
- Added Updater capability (see requirements for that on that plugins thread)

** It's probably best to delete your config file and let the plugin create a new one since I added a new CVar and removed an unused one.

Version 1.5.6
Now works with CS:S DM
- Enhanced plugin to give replacement weapon on respawns if running CSS:DM and player tries to get restricted weapon

Version 1.5.7
- Fixed [SM] Native "CloseHandle" reported: Handle 0 is invalid (error 4)

Version 1.5.8
- Bug fixes, translation file added, and immune player addition
* Fixed CheckTimer (now ClearTimer, thanks to Antithasys from http://forums.alliedmods.net/showthread.php?t=167160
* Added CheckCommandAccess and assigned "doNot_Restrict_Snipers" or ADMFLAG_CUSTOM2 to allow players to not be affected by this plugin.
* Inclusion of colors.inc for colored chat with translation files

Version 1.6.1
- Fixed sm_sniperrestrict_version from displaying old information contained in config file
- Added CVar for Updater - defaulted to off
- Added CVar to make weapon drop at round end instead of immediately
- Added CVar to notify all players when another player reaches sniper kill limit.
- Added CVar for player notifications for remaining sniper kills

Version 1.6.2 to 1.6.3.2
+ Added CVar so you can define your own sniper weapons.
* Fixed sound to work with CSGO
* Cleaned up client timer codes - now using client serials
* Went to 4 digit version numbers
* Updated and added translation phrases.
- Removed need for sound.txt

Version 1.6.3.3
+ Added CVar to control admin notifications for when players finish their cooldown rounds after being restricted.

If you have 1.5.5 (or newer) and Updater, then the plugin already updated itself (or will soon).

As of 1.6.1, the CVar for updater is defaulted to off.

New CVars in 1.6.3.3, so either add them manually or backup the old config file (rename it to .old) and let the plugin create a new config file, then edit that one.

[TnTSCS]

I will be changing this once Dr!fter releases v3 of the weapon_restrict plugin

...:: TnT Edit ::...
The change will be to use his forwards - the concept will remain the same Unless he incorporates this plugins idea into his weapon_restrict plugin

[TnTSCS]

Updated to 1.2c

Last thing I have to do is plug in a translation file

[TnTSCS]

Updated to 1.3

Added setting to destroy weapon once MaxSniperKills limit is reached instead of just dropping the weapon. This was done be request so that another player can't pickup that weapon and use it. Set this option in the config file. If you update to 1.3, delete the old config file and let the plugin create a new one.

[krzynek1]

TnTSCS, can you make your plugin compatible with CSSDM ? Now it doesn't drop weapon neither destroy it.

[TnTSCS]

So, when running this plugin with BAILOPAN's DeathMatch mod, the sniper weapon is not dropped or destroyed when the player reaches their max sniper limit?

I'll have to look at the CSSDM and see how it handles weapons

[krzynek1]

yes, that's how it is now

[TnTSCS]

are there any errors in your logs? This plugin uses a gamedata file - make sure you have wpndrop-cstrike.games.txt in your sourcemod/gamedata folder

[krzynek1]

yes, there are error logs

L 10/30/2011 - 19:17:18: [SM] Native "SDKCall" reported: Invalid Handle 0 (error 4)
L 10/30/2011 - 19:17:18: [SM] Displaying call stack trace for plugin "SniperRestrict.smx":
L 10/30/2011 - 19:17:18: [SM]   [0]  Line 391, C:\srcdsdm\orangebox\cstrike\addons\sourcemod\scripting\SniperRestrict.sp::RestrictDropRepay()
L 10/30/2011 - 19:17:18: [SM]   [1]  Line 230, C:\srcdsdm\orangebox\cstrike\addons\sourcemod\scripting\SniperRestrict.sp::Event_ItemPickup()

my server info :

sm exts list
[SM] Displaying 10 extensions:
[01] Automatic Updater (1.3.8): Updates SourceMod gamedata files
[02] Webternet (1.3.8): Extension for interacting with URLs
[03] CS:S Tools (1.3.8): CS:S extended functionality
[04] BinTools (1.3.8): Low-level C/C++ Calling API
[05] Top Menus (1.3.8): Creates sorted nested menus
[06] SDK Tools (1.3.8): Source SDK Tools
[07] Client Preferences (1.3.8): Saves client preference settings
[08] SQLite (1.3.8): SQLite Driver
[09] CS:S DM (2.1.5-dev): Deathmatch for CS:S
[10] SDK Hooks (2.1.0): Source SDK Hooks

sm version
 SourceMod Version Information:
    SourceMod Version: 1.3.8
    SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.3.8)
    SourcePawn API: v1 = 4, v2 = 3
    Compiled on: Jun 25 2011 00:30:59
    Build ID: 3157:cf41e7301d55
    http://www.sourcemod.net/

meta version
Metamod:Source version 1.8.7
Build ID: 772:99b7a0a11fec
Loaded As: Valve Server Plugin
Compiled on: Jun 23 2011
Plugin interface version: 15:14
SourceHook version: 5:5
http://www.metamodsource.net/

configuration of sniper restrict

sm cvars 23
[SM] Listing 8 convars for: Sniper Restrict
  [Name]                           [Value]
  sm_SniperRestrict_AdminNotify    1
  sm_SniperRestrict_DestroyWeapon  1
  sm_SniperRestrict_MaxSniperKill  2
  sm_SniperRestrict_ScoutIsSniper  0
  sm_SniperRestrict_SniperReplace  weapon_scout
  sm_SniperRestrict_sound          admin_plugin/actions/restrictedweapon.wav
  sm_SniperRestrict_version        1.3
  sm_SniperRestrict_version_build  1.3.8

my plugin installation is correct, addon notifies me that I reached the limit but nothing happens

[TnTSCS]

I'll look into it - it's strange though, on error, GetPlayerWeaponSlot should return -1 if no weapon in slot 0 (main weapon slot)

http://docs.sourcemod.net/api/index....ad=show&id=37&

which dev version of CSSDM do you have?
cssdm-2.1.5-hg73-linux.tar.gz
cssdm-2.1.5-hg73-mac.zip
cssdm-2.1.5-hg73-windows.zip
cssdm-2.1.5-hg75-linux.tar.gz
cssdm-2.1.5-hg75-mac.zip
cssdm-2.1.5-hg75-windows.zip
cssdm-2.1.5-hg76-linux.tar.gz
cssdm-2.1.5-hg76-mac.zip
cssdm-2.1.5-hg76-windows.zip
cssdm-2.1.5-hg77-linux.tar.gz
cssdm-2.1.5-hg77-mac.zip
cssdm-2.1.5-hg77-windows.zip