[Obyboby]

Originally Posted by Ultralord for some reason when restricted items has reached the players CAN buy the restricted weapon and after the weapon drops.. and anyone crying for the money lost.. is possible to fix somehow..? to be blocked on buy menu if restricted weapon has reached with allowed number?

use the latest sourcemod build to fix that. 1.8 build 6027 ( I believe it was fixed by 6025 already)
Had the same bug but it's not occuring anymore on my server


Btw still trying to figure out why I can't play grenade warmups anymore.
It only happens with HE grenades.
You throw the first one, and then get stuck with your knife, u cant even swing the knife. Your only option is to rush to your enemy and get killed :C
Anyone else expierencing this? Most likely another plugin interfering but I have way too many to try and remove one by one :C
Any help would be appreciated. It's been more than a month that I had to keep he grenades disabled at warmup :C

[Muffik]

Hello, I have a question.
Is it possible to set this plugin up in the way that would "partially" restrict some weapons (e.g so that let's say awp will be restricted to two per team, although vips will be able to override that restriction) and at the same time restrict some weapons completely (so that not even vips or admins will be able to buy them) ?

I have the partial restriction configured correctly, although I would like to make few weapons not able to use at all. Is this possible ? If so, could someone please explain to me how to do it ?

I mean is it possible to configure so within this plugin, or do I need another one to do that ?

[Dr!fter]

Originally Posted by Muffik Hello, I have a question. Is it possible to set this plugin up in the way that would "partially" restrict some weapons (e.g so that let's say awp will be restricted to two per team, although vips will be able to override that restriction) and at the same time restrict some weapons completely (so that not even vips or admins will be able to buy them) ? I have the partial restriction configured correctly, although I would like to make few weapons not able to use at all. Is this possible ? If so, could someone please explain to me how to do it ? I mean is it possible to configure so within this plugin, or do I need another one to do that ?

You need to either modify lots of stuff or use the forwards in a new plugin

[Muffik]

Not sure that I understand how I would do that =/

[cheating_anime]

crashes my server for some reason

[chris1994Op]

How can i restrict everything for scouts maps that leave deagls and usps lying on map only scouts n knifes strictly

[unknownuser1339]

it crashs my server. any help pls

[Kammi_]

Originally Posted by unknownuser1339 it crashs my server. any help pls

any logs ? and what game ?

[Bacardi]

*bug
Don't use it. I fix later.


[CSS/CS:GO] Weapon Restrict - Admin weapon restriction v.0.1

Here is add on plugin beside Weapon Restrict plugin. Means you need both plugins.

Rant:

- This affect to players who have access to admin override sm_restrict_immunity_level
- Need enable cvar sm_weapon_restrict_immunity to get admin immunity work.
- This should work so it not affect to weapon restrict count, admins bypass this.

- Once you have loaded add on plugin test.smx in server,
players with sm_restrict_immunity_level access lose they immunity to get restricted weapons <- Read this twice and keep it mind!

- To give immunity back for specific weapon, use new admin overrides sm_restrict_immunity_*, replace *asterix with followed word
(new admin override is flagged to "root" by default)

			"p228",			"glock",		"scout",		
	"hegrenade",	"xm1014",		"c4",			"mac10",		
	"aug",			"smokegrenade",	"elite",		"fiveseven",
	"ump45",		"sg550",		"galil",		"famas",
	"usp",			"awp",			"mp5navy",		"m249",
	"m3",			"m4a1",			"tmp",			"g3sg1",
	"flashbang",	"deagle",		"sg552",		"ak47",
	"knife",		"p90",			"shield",		"vest",			
	"vesthelm",		"nvgs",			"galilar",		"bizon",
	"mag7",			"negev",		"sawedoff",		"tec9",
	"taser",		"hkp2000",		"mp7",			"mp9",
	"nova",			"p250",			"scar17",		"scar20",
	"sg556",		"ssg08",		"knifegg",		"molotov",
	"decoy",		"incgrenade",	"defuser"

- For example in admin groups override,
group called "Admins" get access to restricted weapons ssg08 and awp
admin_groups.cfg

Spoiler

Groups
{
	/**
	* Allowed properties for a group:
	*
	*   "flags"           - Flag string.
	*   "immunity"        - Immunity level number, or a group name.
	*						 If the group name is a number, prepend it with an
	*						 '@' symbol similar to admins_simple.ini.  Users
	*						 will only inherit the level number if it's higher
	*						 than their current value.
	*/
	"Default"
	{
		"immunity"		"1"
	}

	"Full Admins"
	{
		/**
		* You can override commands and command groups here.
		* Specify a command name or group and either "allow" or "deny"
		* Examples:
		* 		":CSDM"			"allow"
		*		"csdm_enable"	"deny"
		*/
		Overrides
		{
		}
		"flags"			"abcdefghiz"

		/* Largish number for lots of in-between values. */
		"immunity"		"99"
	}

	"Admins"
	{
		Overrides
		{
			"show_admins"	"allow"
			"sm_restrict_immunity_level"	"allow"
			"sm_restrict_immunity_ssg08"	"allow"
			"sm_restrict_immunity_awp"	"allow"
		}
		"flags"			"abcdefghi"

		"immunity"		"50"
	}

	"vip"
	{
		Overrides
		{
			"sm_admin"		"allow"
			"sm_who"		"allow"
		}
		"flags"			""

		"immunity"		"10"
	}
}

- Alternative way is override admin flags if you can't handle admin groups
admin_overrides.cfg

Spoiler

Overrides
{
	/**
	 * By default, commands are registered with three pieces of information:
	 * 1)Command Name 		(for example, "csdm_enable")
	 * 2)Command Group Name	(for example, "CSDM")
	 * 3)Command Level		(for example, "changemap")
	 *
	 * You can override the default flags assigned to individual commands or command groups in this way.
	 * To override a group, use the "@" character before the name.  Example:
	 * Examples:
	 *		"@CSDM"			"b"				// Override the CSDM group to 'b' flag
	 * 		"csdm_enable"	"bgi"			// Override the csdm_enable command to 'bgi' flags
	 *
	 * Note that for overrides, order is important.  In the above example, csdm_enable overwrites
	 * any setting that csdm_enable previously had.
	 *
	 * You can make a command completely public by using an empty flag string.
	 */

	 "sm_restrict_immunity_level"		"a"
	 "sm_restrict_immunity_awp"	"c"
	 "sm_restrict_immunity_ssg08"	"c"
}

- For compile this add on plugin source code test.sp, require:
restrict.inc
cstrike_weapons.inc

- For ready use, download compiled plugin test.smx



*edit
0.1v - BUG! there is little flaw, admin can't get restricted weapon even it have opportunity

[Dr!fter]

Originally Posted by Bacardi *bug Don't use it. I fix later. [CSS/CS:GO] Weapon Restrict - Admin weapon restriction v.0.1 Here is add on plugin beside Weapon Restrict plugin. Means you need both plugins. Rant: - This affect to players who have access to admin override sm_restrict_immunity_level - Need enable cvar sm_weapon_restrict_immunity to get admin immunity work. - This should work so it not affect to weapon restrict count, admins bypass this. - Once you have loaded add on plugin test.smx in server, players with sm_restrict_immunity_level access lose they immunity to get restricted weapons <- Read this twice and keep it mind! - To give immunity back for specific weapon, use new admin overrides sm_restrict_immunity_*, replace *asterix with followed word (new admin override is flagged to "root" by default) "p228", "glock", "scout", "hegrenade", "xm1014", "c4", "mac10", "aug", "smokegrenade", "elite", "fiveseven", "ump45", "sg550", "galil", "famas", "usp", "awp", "mp5navy", "m249", "m3", "m4a1", "tmp", "g3sg1", "flashbang", "deagle", "sg552", "ak47", "knife", "p90", "shield", "vest", "vesthelm", "nvgs", "galilar", "bizon", "mag7", "negev", "sawedoff", "tec9", "taser", "hkp2000", "mp7", "mp9", "nova", "p250", "scar17", "scar20", "sg556", "ssg08", "knifegg", "molotov", "decoy", "incgrenade", "defuser" - For example in admin groups override, group called "Admins" get access to restricted weapons ssg08 and awp admin_groups.cfg Spoiler Groups { /** * Allowed properties for a group: * * "flags" - Flag string. * "immunity" - Immunity level number, or a group name. * If the group name is a number, prepend it with an * '@' symbol similar to admins_simple.ini. Users * will only inherit the level number if it's higher * than their current value. */ "Default" { "immunity" "1" } "Full Admins" { /** * You can override commands and command groups here. * Specify a command name or group and either "allow" or "deny" * Examples: * ":CSDM" "allow" * "csdm_enable" "deny" */ Overrides { } "flags" "abcdefghiz" /* Largish number for lots of in-between values. */ "immunity" "99" } "Admins" { Overrides { "show_admins" "allow" "sm_restrict_immunity_level" "allow" "sm_restrict_immunity_ssg08" "allow" "sm_restrict_immunity_awp" "allow" } "flags" "abcdefghi" "immunity" "50" } "vip" { Overrides { "sm_admin" "allow" "sm_who" "allow" } "flags" "" "immunity" "10" } } - Alternative way is override admin flags if you can't handle admin groups admin_overrides.cfg Spoiler Overrides { /** * By default, commands are registered with three pieces of information: * 1)Command Name (for example, "csdm_enable") * 2)Command Group Name (for example, "CSDM") * 3)Command Level (for example, "changemap") * * You can override the default flags assigned to individual commands or command groups in this way. * To override a group, use the "@" character before the name. Example: * Examples: * "@CSDM" "b" // Override the CSDM group to 'b' flag * "csdm_enable" "bgi" // Override the csdm_enable command to 'bgi' flags * * Note that for overrides, order is important. In the above example, csdm_enable overwrites * any setting that csdm_enable previously had. * * You can make a command completely public by using an empty flag string. */ "sm_restrict_immunity_level" "a" "sm_restrict_immunity_awp" "c" "sm_restrict_immunity_ssg08" "c" } - For compile this add on plugin source code test.sp, require: restrict.inc cstrike_weapons.inc - For ready use, download compiled plugin test.smx *edit 0.1v - BUG! there is little flaw, admin can't get restricted weapon even it have opportunity

I'll just this now. There is a new version in the works for sourcemod 1.9 (that has lots of cs:go fixes) you can find it on the repo. Hopefully it doesn't break any third party plugin that uses it but heads up since you are one of the few that made another plugin using the restrict API.