[SubStream]

Originally Posted by techwg One more thing, can you add other commands to the list at all ? how about name

I haven't found a way to restrict that command and even if I did, players could still use setinfo name "Player" to change their name to player. I tried to restrict setinfo and that was unsuccessfull as well.

If you want to block name change use One Name. I know it doesn't block the command but it keeps one name.

I tested about 300 commands before releasing the first version and I am pretty sure I got most of the commands you can block that are worth blocking anyhow. If you can think of any commands that I haven't already tried I will be more than happy to add them to the plugin if I can.

By the way version 1.2 is up and I added commands impulse 100 (flashlight) and impulse 201 (spray) to the list.

[techwg]

how about +voicerecord or whatever to stop voice comms . . .
Presently if people get too yappy, i rcon sv_voicecodec voice_speep

[SubStream]

Originally Posted by techwg how about +voicerecord or whatever to stop voice comms . . . Presently if people get too yappy, i rcon sv_voicecodec voice_speep

I tried blocking that and was unable to.

While the command +voicerecord itself cannot be blocked, you can use Voicecomm Ban to ban individual players from voice (and it saves the players into a file so they are still banned when they come back).

The actual command +voicerecord cannot be restricted (as far as I know).

[Bo0m!]

What about blocking voice_inputfromfile to stop HLSS users?

[SubStream]

Originally Posted by Bo0m! What about blocking voice_inputfromfile to stop HLSS users?

voice_inputfromfile is a setting not a command so I am not adding that to this plugin or even trying to. This plugin is for client side commands only. You can go download EKS cvar checker and add it to the cfg for that. Do a search for it and you'll find it.

[Bo0m!]

Ah my bad, was just tossing out a suggestion without thinking after reading about that +voicerecord.

[diamond-optic]

i use HLguard to lock voice_inputfromfile to "0"

so if you cant just block it thru this or whatever.. find something that will lock it at 0, there has to be a plugin that can lock commands at certain settings

[SubStream]

Originally Posted by diamond-optic there has to be a plugin that can lock commands at certain settings

Originally Posted by SubStream Originally Posted by Bo0m! What about blocking voice_inputfromfile to stop HLSS users? voice_inputfromfile is a setting not a command so I am not adding that to this plugin or even trying to. This plugin is for client side commands only. You can go download EKS cvar checker and add it to the cfg for that. Do a search for it and you'll find it.

Yah it's called Cvar Checker by EKS. You can probably use that to do what you guys are talking about. This plugin is only for restricting/blocking commands not settings/cvars.

[Martin1]

[es]
RC_LANG_INFO_STARTUP = %s version %s, Copyright (C) 2006 %s.  Este plugin viene sin ninguna garantia.  Es un programa gratis, y estas invitado a distribuirlo debajo las condiciones gpl. Tipia `amxx gpl' para mas informacion

RC_LANG_SERVER_MSG1 = [AMXX] [rc] restrictcommands.amxx plugin Empesado
RC_LANG_SERVER_MSG2 = [AMXX] [rc] restrictcommands.cfg executado.
RC_LANG_BLOCKED_MESSAGE = >> Este commando es illegal <<

[lubb]

hha i translated this plugin. feel soo good that its released