Have certian users not be counted toward the user limit of a voice channel

dessertmonkeyjk
  • 編輯於

In a few servers I'm in, we've been having calls where we want certain users to be in the voice call but we also don't want it to get overcrowded. We made use of the user limit for voice channels and I know users with the Move Channels permission can bypass the limit (Mods, Admins, etc). However, they are still COUNTED toward said limit and can prevent other users from joining. 

For example, there could be a voice channel with a user limit of 5 and two mod users join. That means that 2 out of 5 are now counted toward the user limit. I would rather the count still be 0 out of 5 despite the mods being in the voice channel beforehand. 

Is there a way to make it where certain users are not counted by the user limit so they don't hog slots for other users? Otherwise I think it could be a handy feature.

1

評論

1 條評論

日期 投票數
  • Sindrah

    I am currently looking into achieving this very concept using our in-house bot. It actually isn't difficult at all to program this functionality - simply catch every VoiceStateUpdate (triggers on many things) and specifically check the channelIDs of the old and new states to determine where a user joins/leaves, compare it to a configured list of voice channel IDs and their expected limits without bypassers, and modify the channel limit for when a bypassing user joins or leaves (and never going below the configured user maximum of the channel).

    The only reason I am hesitant to add this functionality to our in-house bot is because we have over 6000 members, and at times we can have upwards to over 200 people in VC at once throughout our channels, which means our bot will get voiceStateUpdate triggers for every time anyone starts/stops speaking, starts/stops/changes-source for video and/or stream, any kind of mute/deafen (self or server), and whenever they connect/disconnect/move to/from a voice channel - this could easily flood the bot if a group of users decided to spam the voiceStateUpdate event quickly in a short period of time, which could cause other listeners of the bot to get passed over and some events could get missed due to an effective DDoS on the bot. Sure, the effective way to handle that is to ensure the bot host has enough bandwidth, RAM, and enough CPU power to overcome the theoretical maximum possible data the server could be expected to handle, but that might get expensive.

    I'll be honest, I have no idea how many users it could take doing reasonable things to overload the bot, and I have not tested it yet, but I feel this shouldn't be something a server owner/admin should be forced to have to manage via a bot, since limits are able to be overidden by mod roles it stands to reason they shouldn't have even been counted in the first place (or at least give server managers the option to count limit-overiders as part of the user counts or not on a per-channel basis).

    TL;DR I support this feature request - help keep custom server bot code to a minimum!

    0

請登入寫評論。