15-05-2017/10:04 AM
(This post was last modified: 15-05-2017/10:12 AM by Byte. Edited 1 time in total.)
Its odd that this happened recently and not 3 days ago when sourcecomms was updated.
Anyway I wen't through WardenTools and made some updates:
https://www.invexgaming.com.au/showthread.php?tid=6881
However, I don't think it will fix this specific issue. (But it possible might).
My next approach is going to be going through every plugin that mutes at all and adding a little log message to them.
Then I can match up the times of the mute and get an idea which plugin is actually responsible.
Plugins we run using basecomms 'mute' functionality:
Anyway I wen't through WardenTools and made some updates:
https://www.invexgaming.com.au/showthread.php?tid=6881
However, I don't think it will fix this specific issue. (But it possible might).
My next approach is going to be going through every plugin that mutes at all and adding a little log message to them.
Then I can match up the times of the mute and get an idea which plugin is actually responsible.
Plugins we run using basecomms 'mute' functionality:
- smac_cvars
- sbpp_comms (this is sourcebans sourcecomms)
- wardentalk2 (this was just improved/merged into wardentools and is no longer a used plugin)
- basecomm (this is a standard sourcemod plugin, the bug won't be caused by this)