[Dr. McKay]

Originally Posted by Peace-Maker Nice idea. Some notes: The boolean tag is lowercase in sourcepawn. "bool:" instead of "Bool:". When using #tryinclude, make sure to mark the autoupdate natives as optional in askpluginload2 to have the plugin compile if the include fails. PHP Code: if(StrEqual(buffer, "@all") || StrEqual(buffer, "@red") || StrEqual(buffer, "@blue") || StrEqual(buffer, "@alive") || StrEqual(buffer, "@dead") || StrEqual(buffer, "@humans") || StrEqual(buffer, "@bots") || StrEqual(buffer, "@ct") || StrEqual(buffer, "@t")) {     ReplyToCommand(client, "[SM] Usage: sm_mutecheck [target]");     return Plugin_Handled; }  You don't want those group targeting features? Consider using FindTarget to allow a single target only. For performance reasons, don't declare new variables in a loop, but do it beforehand.

Thanks for the help! As you can probably tell, I'm just learning SourcePawn.

I've updated it with the stuff you said.

[Dr. McKay]

Updated to v1.3 to fix sm_mutecheck [target] not working. My bad, I mixed up the muter and mutee in IsClientMuted().

[Dr. McKay]

Plugin has been updated to v1.4. Removed immunity check from sm_mutecheck [target].

[snelvuur]

if there are xx players on the servers and xx players have muted 1 particular person then mute the person for the other players too.. might be a idea.. (but maybe too much for now)

[Dr. McKay]

Originally Posted by snelvuur if there are xx players on the servers and xx players have muted 1 particular person then mute the person for the other players too.. might be a idea.. (but maybe too much for now)

That's another plugin in and of itself, but it could be done relatively easily. Just a question though, why exactly do you want that? The few that haven't muted said player might want to hear what he or she is saying. The ones that have muted aren't going to hear them either way.

[snelvuur]

Well if somebody is spamming the mic, if you suddenly have 5 people muting a person that usually is a dead giveaway that he is spamming. But like you said it would be another plugin then, but hey it was just a suggestion

[Dr. McKay]

Updated. The version cvar now has an "A" appended to it if autoupdate is functioning.

[Dr. McKay]

Updated. Now uses the newer, better supported Updater, added sm_mutecheck_tag to change the tag prepended to Mutecheck responses, and typing sm_mutecheck in the console without any parameters now return a usage message.

[Dr. McKay]

Updated to 1.7.0. Fixed an issue where the plugin wouldn't be added to the Updater pool. If you are running Updater and you want to automatically update, simply execute "sm plugins reload mutecheck" followed by "sm_mutecheck_forceupdate" in the console/rcon.

[Atreus]

Firstly, is there any particular reason for disallowing the group targetting (eg @all, etc)? It could be really useful to see, at a glance, who is muted by who. If you just feel it's too much work, this plugin by necavi makes the process REALLY simple.

Secondly, any chance you could add an option for what flag someone needs to use sm_mutecheck itself? I don't want non-admins to have access, because seeing other people have muted them may cause unneeded drama. But it's a great admin tool

edit: i managed to edit and recompile the plugin to fix the second issue I brought up. Would love to see that and/or the targetting thing in the official copy as well so I could let it autoupdate.