[PStar]

Originally Posted by YouzAMenace for admin commands? if so ill add it hopefully next version

Don't know, i thin for all.
Cause no i use perplayer to restrict weapons and if player count drops or riser weapons will be restricted and unrestricted, and if to many weapon restriction were changed it simply spams teh chat.

[Bacardi]

Originally Posted by YouzAMenace Ok heres a quick beta version. I fixed the drop the bomb for other players. It actually only worked if the player running the command had the bomb (oops was comparing client and not i) So that is now fixed see if you guys get an error again with sourcetv ingame. I tested with sourcetv and got no errors but i didnt get them the first time. If you guys dont get the error ill pull it out of beta and release it along with another change i plan on making.

Seems working fine now with bots/sourceTV
I haven't find any errors or problems... now

[Dr!fter]

Originally Posted by PStar Don't know, i thin for all. Cause no i use perplayer to restrict weapons and if player count drops or riser weapons will be restricted and unrestricted, and if to many weapon restriction were changed it simply spams teh chat.

Is this the seperate per player?

[PStar]

Originally Posted by YouzAMenace Is this the seperate per player?

Yes.

[Bacardi]

Originally Posted by PStar Don't know, i thin for all. Cause no i use perplayer to restrict weapons and if player count drops or riser weapons will be restricted and unrestricted, and if to many weapon restriction were changed it simply spams teh chat.

That is good idea silent cvars commands in chat.

I'm not coder , but I get one way silent these cvars_chat messages when perplayer-plugin make action if player count something pla pla plaa.

Look file
...addons\sourcemod\scripting\restrictinc\adm incmds.sp

If you have version 2.2.7 beta=#197, go/look lines 182 - 188
If version 2.2.6 = go/look lines 173 - 179

So what I did I disabled/comment few lines. Like this

/*        else
*        {
*            if(ammount >= 0)
*                PrintToChatAll("\x04[SM] %s was restricted to %i %s", weapon, ammount, action);
*            else
*                PrintToChatAll("\x04[SM] %s was unrestricted %s", weapon, action);
*        }
*/

Finally compile
...addons\sourcemod\scripting\compile.exe
and take new smx file in ...addons\sourcemod\scripting\compiled\weapon _restrict.smx

*edit
Not mean that this is right way to edit ^^

[Dr!fter]

Yes thats a good way to do it that only stops changes made from console(the server it self) to not be announced. I added a cvar already need to test all the changes. With the cvar you would be able to disable it in per player before any changes then just re enable at the end of the per player string

[xiloid]

Hello guys!
Can someone translate this plugin into russsian??
I try translate menu by myself on /restrictinc/adminmenu.sp but unsuccessful

[Snake60]

Уже всё сделано, смотри сюда

[xiloid]

Originally Posted by Snake60 Уже всё сделано, смотри сюда

Thank you very much!!! Great job!
(На русском запрещают отвечать, но всеравно спасибо! Все супер.)

[Dr!fter]

I decided to release 2.2.7 before i added any new features since im not sure how long it will be before i can finish adding the new features. The new release only fixes drop bomb command. Enjoy!

@Snake60 if you want to make another translation version (to make it easier for you) the only file that changed is admincmds.sp and only changed 2 things for the function DropC4. So you dont have to do everything over .

As a note my next major release (2.3.0) will have translations and a few other requests ive seen.