[Byte]

Anti Voice Loopback (V1.02)
Block HLDJ/SLAM/Voice Loopback tools

By Byte

🔹 Description 🔹
Blocks voice loopback in game which should break most tools like HLDJ/SLAM.
Mutes and unmutes instantly unlike other solutions.
Fixes bypass caused by other plugins unmuting clients.

Please test on other mods and make feature requests if you have any.

🔹 Instructions 🔹

1. Download plugin
2. Copy plugin/translations to your server
3. Optionally configure settings in cfg/sourcemod/antivoiceloopback.cfg

🔹 Changelog🔹

1.02 Actually pass the client through the timer! Thanks Xines.
1.01 Add missing AutoExecConfig
1.00 Initial release

🔹 Downloads 🔹

Github Repo:

Source | Releases

AlliedModders Mirror (DL: 3):

[Byte]

Reserved.

[Byte]

FYI, functionality is limited if not using basecomms.
If using sourcecomms (part of sourcebans++), you'll also need this PR which fixes session mutes:
https://github.com/sbpp/sourcebans-pp/pull/384

Otherwise, session mutes act as 120 minute bans.

[Dr.Doctor]

Wow seems good, I will test on my servers!

[Ejziponken]

Thx, testing this

[Obyboby]

Originally Posted by Byte FYI, functionality is limited if not using basecomms. If using sourcecomms (part of sourcebans++), you'll also need this PR which fixes session mutes: https://github.com/sbpp/sourcebans-pp/pull/384 Otherwise, session mutes act as 120 minute bans.

Interesting plugin, thanks.
May I go a bit OT and ask a question about this matter: I currently have both basecomm.smx and sbpp_comms.smx loaded on my server, am I supposed to disable either one? (basecomm.smx I guess)
Thanks

[Byte]

Originally Posted by Obyboby Interesting plugin, thanks. May I go a bit OT and ask a question about this matter: I currently have both basecomm.smx and sbpp_comms.smx loaded on my server, am I supposed to disable either one? (basecomm.smx I guess) Thanks

No I mean if you aren't using basecomm or sourcecomms.
Sourcecomms relies on basecomm to function. So if you're using sourcecomms don't disable basecomm.

If you are using sourcecomms there is a bug with sessions as I mentioned so you'll have to update sourcebans++ to the latest version on git + then compile sourcecomms with my PR fix.

[Obyboby]

Originally Posted by Byte No I mean if you aren't using basecomm or sourcecomms. Sourcecomms relies on basecomm to function. So if you're using sourcecomms don't disable basecomm. If you are using sourcecomms there is a bug with sessions as I mentioned so you'll have to update sourcebans++ to the latest version on git + then compile sourcecomms with my PR fix.

My sbpp is 1.6.2, I guess I just need to compile the modified comm plugin then?

[Byte]

Originally Posted by Obyboby My sbpp is 1.6.2, I guess I just need to compile the modified comm plugin then?

There have been a few commits since V1.6.2:
https://github.com/sbpp/sourcebans-p.../sbpp_comms.sp

But yeah you just need to compile the modified comm plugin then session bans will work properly.

[Obyboby]

Originally Posted by Byte There have been a few commits since V1.6.2: https://github.com/sbpp/sourcebans-p.../sbpp_comms.sp But yeah you just need to compile the modified comm plugin then session bans will work properly.

Thanks. I'll look into updating my sbpp and then will try out your plugin