[CSS/CS:GO] Weapon Restrict - Page 88

**Dr!fter** · *Last edited by Dr!fter; 11-09-2011 at 00:42.*

The offsets is cause he took them from CSS:Dm they arent used by this plugin at all. The sigs might have 2 bytes different but its still good 1 is wildcarded my end and 5C doesnt have to be. The sig that already existed is unique and correct still :3

X3S2 · 11-09-2011 , 13:03 Re: [CSS] Weapon Restrict (Beta 3.0 is here!)

Quote:

Originally Posted by Dr!fter

There was/is nothing wrong with the gamedata in the first posts zip. The Linux symbol hasnt changed and neither has the sig. The only difference in the sig from CSSDM and this is that I had to wildcard the first 9 bytes to work with CSSDM

Since I use the gamedate, I have no Laggs. Thats different`? ;)

But I think the Beta 3.0.1 is crashing my Server very often.

Quote:

L 11/09/2011 - 16:53:55: SourceMod error session started
L 11/09/2011 - 16:53:55: Info (map "de_dust2") (file "errors_20111109.log")
L 11/09/2011 - 16:53:55: [SM] Native "KillTimer" reported: Invalid timer handle 6b3b0534 (error 3)
L 11/09/2011 - 16:53:55: [SM] Displaying call stack trace for plugin "weapon_restrict.smx":
L 11/09/2011 - 16:53:55: [SM] [0] Line 16, restrictinc/warmup.sp::KillRespawnTimer()
L 11/09/2011 - 16:53:55: [SM] [1] Line 103, restrictinc/warmup.sp::WarmupCount()
L 11/09/2011 - 16:53:56: [SM] Native "KillTimer" reported: Invalid timer handle 6b3b0534 (error 3)
L 11/09/2011 - 16:53:56: [SM] Displaying call stack trace for plugin "weapon_restrict.smx":
L 11/09/2011 - 16:53:56: [SM] [0] Line 16, restrictinc/warmup.sp::KillRespawnTimer()
L 11/09/2011 - 16:53:56: [SM] [1] Line 103, restrictinc/warmup.sp::WarmupCount()
L 11/09/2011 - 17

6

6: Error log file session closed.

**Dr!fter** · 11-09-2011 , 14:58 Re: [CSS] Weapon Restrict (Beta 3.0 is here!)

Quote:

Originally Posted by X3S2

Since I use the gamedate, I have no Laggs. Thats different`? ;)

But I think the Beta 3.0.1 is crashing my Server very often.

What you are saying about lag doesn't even make sense. Also 3.0.1 doesn't even use gamedata so. I'm tired of arguing/discussing the gamedata issue and people blaming anything and everything for causing crashes. As for the error I will look into it. I think I know the cause. But as a note that wouldn't crash the server. Unless you want to blame it anyway.

TnTSCS · 11-09-2011 , 19:16 Re: [CSS] Weapon Restrict (Beta 3.0 is here!)

I'm not running version 3.0.1... I'm running the version from the OP.

I'll test it out though... the OP gamedata may in fact work - as does the one posted... I guess there are many different ways to skin a cat when it comes to gamedata signatures??

blue zebra · *Last edited by blue zebra; 11-10-2011 at 01:03.*

Dr!fter.
Not need forcing the basic sound download, in my opinion.
Your suggested weapon denied sound:

Code:

"WeaponRestrictSounds"
{
    "sounds"
    {
        "restricted"        "sound/admin_plugin/actions/restrictedweapon.wav"
    }
}

same as the original valve sound:

Code:

"WeaponRestrictSounds"
{
    "sounds"
    {
        "restricted"        "sound/buttons/weapon_cant_buy.wav"
    }
}

So if you use the original valve sound, then you dont need to download this sound. Works for me without any downloads.
-1 possible error.

**Dr!fter** · *Last edited by Dr!fter; 11-10-2011 at 13:46.*

Quote:

Originally Posted by TnTSCS

I'm not running version 3.0.1... I'm running the version from the OP.

I'll test it out though... the OP gamedata may in fact work - as does the one posted... I guess there are many different ways to skin a cat when it comes to gamedata signatures??

My 3.0.1 comment was directed at the person that said they were using 3.0.1 and getting lag till they updated the weapon restrict gamedata to the one someone posted. Which made no sense but w/e.

Yes, there is various ways to make a sig all it has to be is unique. Depending on your knowledge you have a better idea of what bytes to not wild card and which to wild card. Linux uses (most of the time) symbols.

Quote:

Originally Posted by blue zebra

Dr!fter.
Not need forcing the basic sound download, in my opinion.
Your suggested weapon denied sound:

Code:

"WeaponRestrictSounds"
{
    "sounds"
    {
        "restricted"        "sound/admin_plugin/actions/restrictedweapon.wav"
    }
}

same as the original valve sound:

Code:

"WeaponRestrictSounds"
{
    "sounds"
    {
        "restricted"        "sound/buttons/weapon_cant_buy.wav"
    }
}

So if you use the original valve sound, then you dont need to download this sound. Works for me without any downloads.
-1 possible error.

I dont suggest anything. It was the sound mani used and the original weapon restrict for sourcemod used. I kept the trend and used it also. I didnt know about the sound until someone mentioned it a few months ago. Ill change the default sound in 3.0.2

kdawgmaster · 11-11-2011 , 10:16 Re: [CSS] Weapon Restrict (Beta 3.0 is here!)

hmm odd, the awp wont restrict. iv typed it in and its still there.

Mysteria · 11-11-2011 , 18:29 Re: [CSS] Weapon Restrict (Beta 3.0 is here!)

Hi, I am using WR 3.0.1 Beta. But I think that found bug.
If I am on CT team and some weapon is restricted, I get message like "Weapon AWP is restricted to 0 per CT Team." a restrict sound.
But I am on T team I get only restrict sound (not this message)

Is it a plugin bug, or its something on my side?

**Dr!fter** · *Last edited by Dr!fter; 11-11-2011 at 23:27.*

Quote:

Originally Posted by kdawgmaster

hmm odd, the awp wont restrict. iv typed it in and its still there.

Please post the output of sm plugins list as well as sm cvars <plugin number> plugin number being the number it has in plugins list.

Quote:

Originally Posted by Mysteria

Hi, I am using WR 3.0.1 Beta. But I think that found bug.
If I am on CT team and some weapon is restricted, I get message like "Weapon AWP is restricted to 0 per CT Team." a restrict sound.
But I am on T team I get only restrict sound (not this message)

Is it a plugin bug, or its something on my side?

Can you be specific on what message exactly? Is when you buy? Try to pickup? When you restrict the weapon? Also is there any errors in the error log. I had a quick look didnt see anything out of place.

Mysteria · *Last edited by Mysteria; 11-12-2011 at 06:11.*

Yes, of course, i try explain it.
For example:

I restricted AWP weapon to 0 per both teams.

If I want to buy it (AWP) on CT team I get "Weapon Restrict sound" and this message:

Code:

"IsRestrictedBuyCT"
    {
        "#format"    "{1:i}"
        "en"        "is currently restricted to {1} for Counter-Terrorists and cannot be bought."    
    }

If I want to buy it on T team I get "Weapon Restrict sound", but I don´t get this message:

Code:

    "IsRestrictedBuyT"
    {
        "#format"    "{1:i}"
        "en"        "is currently restricted to {1} for Terrorists and cannot be bought."    
    }

And I have no error in SM error log.