[MindeLT]

Hi,

since some people are complaining about VIP only awp, i'm trying to do a little fix. The idea looks like this:

There is a limit of 1(free) awp per team. This means, in each team only one non-vip person, could shoot with it, vip persons are ignored(they can shoot awp as before).

Taken some examples from Restrict plugin, but it looks too difficult.

Can someone suggest me, how to check each team AWP holders, and then take some actions?

Thanks

[lokizito]

GetPlayerWeaponSlot(client, slot);
GetEntityClassname(entity, String:clsname[], maxlength)

[Dr!fter]

Originally Posted by MindeLT Hi, since some people are complaining about VIP only awp, i'm trying to do a little fix. The idea looks like this: There is a limit of 1(free) awp per team. This means, in each team only one non-vip person, could shoot with it, vip persons are ignored(they can shoot awp as before). Taken some examples from Restrict plugin, but it looks too difficult. Can someone suggest me, how to check each team AWP holders, and then take some actions? Thanks

FYI: Weapon restrict already does what you want. If you enable weapon restrict immunity and set restrictions for awp to 1 it ignores vip when it checks how many people have that weapon on the team.

PHP Code:

                new count = 0;
        for(new i = 1; i <= MaxClients; i++)
        {
            if(IsClientInGame(i) && GetConVarInt(AdminImmunity) == 1 && ((GetUserFlagBits(i) & ADMIN_LEVEL) || (GetUserFlagBits(i) & ADMFLAG_ROOT)))
                continue;
            
            if(IsClientInGame(i) && i != client && GetClientTeam(i) == clientteam)
            {
                new weaponindex = GetPlayerWeaponSlot(i, slot);
                new String:classname[100];
                if(weaponindex != -1 && IsValidEdict(weaponindex))
                {
                    GetEdictClassname(weaponindex, classname, sizeof(classname));
                    if(StrEqual(classname, weapon2, false))
                        count++;
                }
            }
        } 


Thats straight from weapon restrict (not that long) what becomes long is the ways you can bypass stuff. Or if the weapon is a grenade counting grenades isn't as simple. Ive since rewrote that function (and mostly everything else) for the new weapon restrict (I never noticed I have 2 if's when i can do it all in 1..) The new one will have a native for that function and other functions so you can call it straight from your plugin.

[MindeLT]

thanks!