[TnTSCS]

If you set sm_kdrwl_useexempt to 1, players with the ADMFLAG_CUSTOM6 will not be affected by this KDR Weapon Limit plugin. You can change the flag by overriding the command "no_kdr_restrict" to whatever admin flag you want.

[TnTSCS]

Give this a shot... new CVars so delete your old config and let the plugin create a new one... let me know if you have questions about the CVars. Also, I added a new phrase in the translations file.

If it's good, I'll post it to the new plugins.

[pubhero]

TnTSCS
Thank you. Again. I will testing this new version tomorrow morning. Will write here my experiences.

[Noitartsiger]

It seems to work, but still testing.

2 thing I figured out so far:
- an edited cfg by windows editor doesn't work anymore (coz of line break signs I guess)
- on reconnect I could pickup a restricted weapon, and it also wasn't droped on next round, but when reaching next limit

still testing ... but looks really great so far
Thanks again!

[pubhero]

Originally Posted by Noitartsiger ... - an edited cfg by windows editor doesn't work anymore (coz of line break signs I guess) ...

The phrase file? If yes, you must be using the UTF-8 without BOM codepage. Use notepad ++ .

[TnTSCS]

I'll double check the restriction retention... if you're testing it on CS:GO and you're the only player then the restriction info gets wiped when the server hibernates (I think).

[Noitartsiger]

Yes, UTF-8 is fine. Thx. (ANSI doesn't work for the cfg)

Regarding chat messages:

-> Can you add a second "Off" message, so that there is one for each stage?
Like:
"Your KDR is below the second limit now. You are now restricted for: X, Y, Z only"
"Your KDR is below all limits now. You are no longer restricted"

-> For the public chat message "RestrictAnnounce",
a) there is a mistake with the {1} {2} {3} variables. Its 1, 1, 2, 3 instead of 1, 2, 3, 4.
b) I would prefer it without the list of all restriced weapons (too much 'unimportant' info for others) as I try to keep the chat as clear as possible. If I delete {4} it doesn't work anymore. For this public message I would also remove the KDR info. Keep it simple for public messages, like:
"{1}'s KDR is too high. They are restricted for some weapons now."

c) then, when he drops below the first limit, also a short public message:
"{1}'s KDR is below all limits again. They are no longer restricted."

Only a suggestion, as I think chat messages should be as short as possible.

Couldn't figure out any more issues, so looking forward the release or the next beta which I will test on productive server then.

Regards,

[pubhero]

Test done. Game CSS.
Plugin works well, but i found a bug. If you use sm_kdrwl_botkills "1" convar. But if you playing against the bots and reached the 2. restrict level, + log out and enter the server again, the plugin counting the bot kills like the human kills and restrict the configured weapon. Maybe it's my fault (cfg error?).

Here is my cfg:

// This file was auto-generated by SourceMod (v1.5.0-dev+3779)
// ConVars for plugin "kdr_weapon_limit.smx"


// Announce to all players when a player gets restricted
// 1 = Yes
// 0 = No.
// -
// Default: "0"
sm_kdrwl_announce "0"

// Ignore bot kills towards players KDR?
// 0 = No, count with KDR
// 1 = Yes, do not count with KDR.
// -
// Default: "0"
sm_kdrwl_botkills "1"

// When should player be forced to drop restricted weapon?
// 1 = Immediately
// 2 = Beginning of next round.
// -
// Default: "2"
sm_kdrwl_drop "1"

// Is plugin enabled?
// 0 = No
// 1 = Yes
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_kdrwl_enabled "1"

// Maintain restrictions until map changes?
// If set to no (0) then players can just reconnect to be able to purchase restricted weapons again.
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_kdrwl_maintain "1"

// Minimum number of kills required to start counting KDR.
// 0 = disabled, count KDR right away
// N = Number of kills required before counting KDR
// -
// Default: "0"
sm_kdrwl_minkills "10"

// List the primary weapon to give the player if the reach ratio1 and are forced to drop their weapon
// -
// Default: "weapon_scout"
sm_kdrwl_pw1 "weapon_mp5navy"

// List the primary weapon to give the player if the reach ratio2 and are forced to drop their weapon
// -
// Default: "weapon_scout"
sm_kdrwl_pw2 "weapon_tmp"

// KDR Ratio a player must meet before stage 1 weapon limit is enforced against them.
// -
// Default: "3.0"
sm_kdrwl_ratio1 "6.0"

// KDR Ratio a player must meet before stage 2 weapon limit is enforced against them.
// -
// Default: "5.0"
sm_kdrwl_ratio2 "9.0"

// List the weapons a player cannot use once they've reached the ratio1 limit
// -
// Default: "awp sg550 g3sg1"
sm_kdrwl_rw1 "ak47 aug awp flashbang hegrenade m249 m4a1 p90 scout sg552 smokegrenade"

// List the weapons a player cannot use once they've reached the ratio2 limit
// -
// Default: "awp sg550 g3sg1 m4a1 ak47 deagle"
sm_kdrwl_rw2 "ak47 aug awp deagle elite famas fiveseven flashbang galil hegrenade m249 m4a1 mp5navy p90 scout sg552 smokegrenade ump45"

// Path and file name of sound file to use for restriction sound relative to sound folder.
// -
// Default: "buttons/weapon_cant_buy.wav"
sm_kdrwl_sound "buttons/button2.wav"

// List the secondary weapon to give the player if the reach ratio1 and are forced to drop their pistol
// -
// Default: "weapon_p228"
sm_kdrwl_sw1 "weapon_p228"

// List the secondary weapon to give the player if the reach ratio2 and are forced to drop their pistol
// -
// Default: "weapon_p228"
sm_kdrwl_sw2 "weapon_glock"

// Use the exemption system?.
// -
// Default: "0"
sm_kdrwl_useexempt "0"

// Play sound to player when they reach KDR and are forced to drop their weapon?
// 0 = No
// 1 = Yes
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_kdrwl_usesound "1"

And here are the new HU + EN phrases file

[TnTSCS]

pubhero - In the new version posted below, I tested it and it no longer does what you described. Noitartsiger, all of your requests should be in this release.

This should be the final "beta" and if all is good, I'll post in new plugins section.

New CVar and new translation phrases in this version. Let the plugin create a new config for you so you know what they all are.

If this version is good, I'll need updated translation files in those languages so I can post with the plugin and include in the Updater support I'll add when I post as a new plugin.

[Noitartsiger]

Ok, thx for adding

But on a first test with bots I got a malfunction:
- CS:S linux Ubuntu
- SourceMod (v1.5.0-dev+3764)
- sm_kdrwl_botkills "0"
- sm_kdrwl_drop "2"
- sm_kdrwl_minkills "5"
- sm_kdrwl_ratio1 "2.0"
- sm_kdrwl_ratio2 "3.0"

[SM] Your KDR (1.60) is above the allowed limit (2.00) and you can no longer buy/use these weapons: awp sg550 g3sg1 m4a1 ak47 [SM] Your KDR is 1.60, so you're not allowed to buy that weapon - [m4a1]

It says 1.6 is above 2.00. 1.60 was right (8:5).
Then I made another kill next round

[SM] Your KDR 1.79 is below all limits. You are no longer restricted. Announcing from CheckKDR

It also happends on other situation like 15:8

[SM] Your KDR (1.87) is above the allowed limit (2.00) and you can no longer buy/use these weapons: awp sg550 g3sg1 m4a1 ak47

_______-

And is it possible to suppress the chat message: "Announcing from CheckKDR" ?

_______

Thanks again.
But due to the basic malfunction above I cannot test it on productive server. Or do you think its coz of SM 1.5.0 dev snapshot?

_______

Attached you'll find a German Translation.

Regardas,