[Dr!fter]

Originally Posted by Mister_Magotchi Sorry. I didn't notice you had just updated the plugin. Also, if you look at his call stack trace, it says the directory name is "version 2.3.3", with your latest version being 2.3.5. I don't know if that's really the version he's using or not; it could have just been the directory name on your machine when you compiled it.

It was the directory name i was using when i compiled. I reverted some changes i had made before (for cssdm).

[Jasperman]

Originally Posted by Dr!fter Can you post what OS, and the output of the following. meta list sm plugins list sm version version

While going through all the commands to give you all the info I suddenly noticed it had started working... went to the server tested and yes its working. I have no idea what occurred to make it work. (im assuming the off/on eventually fixed it)

Thank you for the super quick reply

Originally Posted by Mister_Magotchi Also, if you look at his call stack trace, it says the directory name is "version 2.3.3", with your latest version being 2.3.5. I don't know if that's really the version he's using or not; it could have just been the directory name on your machine when you compiled it.

That confused me too. Hence the posting of the stack trace (also the fact i couldnt fix it lol). I downloaded all the files and even attempted a recompile to no avail. Thanks for the help though.

[Dr!fter]

You can ignore the directory stuff. I usually do compile in a different directory for different versions (unless its really minor change like translations or something like a simple error) But for this version i was going backwards to a previous version. So i didnt create a new directory.

[mausetot]

hi drifter, i have al little problem, evertime if i install this plugin, the server does not restart, if i delete the weapon restrict smx, the server runs again. do you have any idea why?

best regards mausetot

[Dr!fter]

Originally Posted by mausetot hi drifter, i have al little problem, evertime if i install this plugin, the server does not restart, if i delete the weapon restrict smx, the server runs again. do you have any idea why? best regards mausetot

OS?

Server Type? CSS or CSS Beta

Output of the following (Can be without weapon restrict installed):

sm version
sm plugin list
sm exts list
meta list
version

Also is there any errors?

[gwhooooey]

Using normal CSS

SourceMod 1.3.7, by AlliedModders LLC

 "Admin File Reader" (1.3.7) by AlliedModders LLC
 "Admin Help" (1.3.7) by AlliedModders LLC
 "Basic Comm Control" (1.3.7) by AlliedModders LLC
 "SQL Admins (Threaded)" (1.3.1) by AlliedModders LLC
 "Basic Commands" (1.3.7) by AlliedModders LLC
 "Admin Menu" (1.3.7) by AlliedModders LLC
 "Basic Info Triggers" (1.3.7) by AlliedModders LLC
 "Anti-Flood" (1.3.7) by AlliedModders LLC
 "Fun Votes" (1.3.7) by AlliedModders LLC
 "Nextmap" (1.3.7) by AlliedModders LLC
 "Player Commands" (1.3.7) by AlliedModders LLC
 "Reserved Slots" (1.3.7) by AlliedModders LLC
 "Sound Commands" (1.3.7) by AlliedModders LLC
 "Team Bets" (2.6) by GrimReaper - Original by ferret
 "Bounty" (1.2.1) by Dr!fter
 "Weapon Restrict" (2.3.5) by Dr!fter


  [01] SourceMod (1.3.7) by AlliedModders LLC
  [02] CS:S Tools (1.3.7) by AlliedModders LLC
  [03] BinTools (1.3.7) by AlliedModders LLC
  [04] SDK Tools (1.3.7) by AlliedModders LLC


Protocol version 15
Exe version 1.0.0.60 (cstrike)
Exe build: 11:28:44 Apr 15 2011 (4539) (240)

Thought I'd do some of the things that were mentioned above before asking my question.

All I want is to permanently restrict AWP/g3sg1/sg550. I don't want anybody to be able to purchase them, but everything I try to change in weapon_restrict, doesn't seem to have an effect.

Using admin flag "z"... and restricting while in game through the menu works fine, but having to do that every map change is a bit of a pain.

These are the only options I've edited, what could be the problem?

// If set to 1 it will NOT remove restricted weapons on pickup but rather on Round start, if set to 0 it will remove on pickup
// -
// Default: "0"
sm_allow_restricted_pickup "1"

// Restrict/Unrestrict -1 unrestricts awp for ct
// -
// Default: "-1"
sm_restrict_awp_ct "0"

// Restrict/Unrestrict -1 unrestricts awp for t
// -
// Default: "-1"
sm_restrict_awp_t "0"

// Restrict/Unrestrict -1 unrestricts g3sg1 for ct
// -
// Default: "-1"
sm_restrict_g3sg1_ct "0"

// Restrict/Unrestrict -1 unrestricts g3sg1 for t
// -
// Default: "-1"
sm_restrict_g3sg1_t "0"

// Restrict/Unrestrict -1 unrestricts sg550 for ct
// -
// Default: "-1"
sm_restrict_sg550_ct "0"

// Restrict/Unrestrict -1 unrestricts sg550 for t
// -
// Default: "-1"
sm_restrict_sg550_t "0"

// Enable warmup.
// -
// Default: "1"
sm_warmup_enable "0"

Any help would be appreciated.

[TnTSCS]

Originally Posted by Dr!fter Originally Posted by TnTSCS along those lines motto, it would be neat to set a certain number of kills (reset on each map change) a player is allowed with any given weapon (like 5 kills for awp/auto before those weapons are restricted)... And the ability to define what weapons are grouped as "sniper guns"... so we could include a scout in that bunch or not. No, this is a simple restrict what you are looking for is way more advanced then what i want this plugin to do. In future releases I might add forwards to make it easier to make more complex plugins.

Any update to the possibility of adding this feature to this plugin?

Here's some additional information that might help clarify what it was I was requesting:

The ability to block Sniper weapons (defaulted to AWPs and Autos) for a player after they have achieved "X" (configurable) number of kills with it and automatically force them to drop that weapon and (optionally) equip them with X (configurable) weapon. Once Sniper weapons are blocked for a player, that player cannot purchase (even through Autobuy) or pickup Sniper weapons for the remainder of the map (even if they reconnect) with a sound playing for if they try to pickup or purchase the restricted weapon. Sniper weapons would include AWP and AUTO by default, but a cvar could be included to include scouts in that list of sniper weapons too.

example cvars:
sm_restrict_MaxSniperKills 5 // (0 to disable, number) Sets the max number of kills allowed with Snipers per map
sm_restrict_ScoutIsSniper 0 // (0,1) Include Scout in the Sniper group (this must be 0 if sm_SniperReplace is "scout")
sm_restrict_SniperReplace "scout" // ("weapon_name" or "" to disable) Weapon to equip player once they've reached their sm_MaxSniperKills limit (if sm_restrict_ScoutIsSniper is 1, do not use "scout")

Things to consider:
If a player is restricted from using AWP or AUTO and they pick one up from the ground, should the gun be destroyed, re-dropped, or switched into the sm_SniperReplace weapon? You wouldn't want a player to go into a loop of pickup restricted weapon, drop it, pick it up, drop it, pick it up, drop it, etc...

[Dr!fter]

Originally Posted by TnTSCS Any update to the possibility of adding this feature to this plugin? Here's some additional information that might help clarify what it was I was requesting: The ability to block Sniper weapons (defaulted to AWPs and Autos) for a player after they have achieved "X" (configurable) number of kills with it and automatically force them to drop that weapon and (optionally) equip them with X (configurable) weapon. Once Sniper weapons are blocked for a player, that player cannot purchase (even through Autobuy) or pickup Sniper weapons for the remainder of the map (even if they reconnect) with a sound playing for if they try to pickup or purchase the restricted weapon. Sniper weapons would include AWP and AUTO by default, but a cvar could be included to include scouts in that list of sniper weapons too. example cvars: sm_restrict_MaxSniperKills 5 // (0 to disable, number) Sets the max number of kills allowed with Snipers per map sm_restrict_ScoutIsSniper 0 // (0,1) Include Scout in the Sniper group (this must be 0 if sm_SniperReplace is "scout") sm_restrict_SniperReplace "scout" // ("weapon_name" or "" to disable) Weapon to equip player once they've reached their sm_MaxSniperKills limit (if sm_restrict_ScoutIsSniper is 1, do not use "scout") Things to consider: If a player is restricted from using AWP or AUTO and they pick one up from the ground, should the gun be destroyed, re-dropped, or switched into the sm_SniperReplace weapon? You wouldn't want a player to go into a loop of pickup restricted weapon, drop it, pick it up, drop it, pick it up, drop it, etc...

There is no update, im still in the process of rewriting this plugin. Even if i do add what i said i planned to add I wouldnt have the time to maintain another plugin. I have too many projects at the moment.

Originally Posted by gwhooooey Using normal CSS Thought I'd do some of the things that were mentioned above before asking my question. All I want is to permanently restrict AWP/g3sg1/sg550. I don't want anybody to be able to purchase them, but everything I try to change in weapon_restrict, doesn't seem to have an effect. Using admin flag "z"... and restricting while in game through the menu works fine, but having to do that every map change is a bit of a pain. These are the only options I've edited, what could be the problem? Any help would be appreciated.

What file are you editing? Also any errors at all?

[gwhooooey]

The weapon_restrict.cfg file, as I don't want it on per-player basis, I want those guns restricted permanently. Not getting any errors other than it not actually restricting the weapons.

All the changes I've made since installing it were mentioned in my above post.

[mausetot]

Hi drifter,

my provider is strato, with linux server, OS? i don´t know...
here is the rest:

Protocol version 15
Exe version 1.0.0.60 (cstrike)
Exe build: 11:28:44 Apr 15 2011 (4539) (240)

SourceMod Version Information:
SourceMod Version: 1.3.7

[SM] Listing 16 plugins:
01 "Anti-Flood" (1.3.7) by AlliedModders LLC
02 "Nextmap" (1.3.7) by AlliedModders LLC
03 "Quake Sounds" (2.7) by dalto, Grrrrrrrrrrrrrrrrrrr, and psychonic
04 "SoDStats" (1.0.11) by ]SoD[ Frostbyte
05 "Rulez_Mod" (1.0.1) by {7~11} Troll
06 "Admin Menu" (1.3.7) by AlliedModders LLC
07 "Admin Help" (1.3.7) by AlliedModders LLC
08 "Basic Commands" (1.3.7) by AlliedModders LLC
09 "Admin File Reader" (1.3.7) by AlliedModders LLC
10 "Basic Comm Control" (1.3.7) by AlliedModders LLC
11 "Basic Chat" (1.3.7) by AlliedModders LLC
12 "Basic Info Triggers" (1.3.7) by AlliedModders LLC
13 "Basic Ban Commands" (1.3.7) by AlliedModders LLC
14 "Basic Votes" (1.3.7) by AlliedModders LLC
15 "Client Preferences" (1.3.7) by AlliedModders LLC
16 "Hostage Penalty-Slay" (0.1) by Bacardi


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



Listing 4 plugins:
[01] SourceMod (1.3.7) by AlliedModders LLC
[02] CS:S Tools (1.3.7) by AlliedModders LLC
[03] BinTools (1.3.7) by AlliedModders LLC
[04] SDK Tools (1.3.7) by AlliedModders LLC

Metamod:Source version 1.8.6
Build ID: 762:c9e30df8fd84
Loaded As: GameDLL (gameinfo.txt)
Compiled on: Apr 15 2011
Plugin interface version: 15:14
SourceHook version: 5:5
http://www.metamodsource.net/


no other errors

best regards
mausetot