Open cool-aid-man opened 2 months ago
Sounds like the person that ran disconnect is a priviledged user like a server owner or a mod or admin set through Red.
Also another thing to note is that the permissions system for audio will not adhere to restrictions if there is no one in the channel or if they are alone.
Sounds like the person that ran disconnect is a priviledged user like a server owner or a mod or admin set through Red.
Hi aika, I can confirm that this is not the case here,
set
command - In fact the user doesn't have any perms besides send_message.permissions
cog, I had cleared all the permissions just to be extra safe.DJ
role set through the audioset dj
.audioset vote 0
(If the audioset vote is set to any percentage then it would have asked the user - "There are other people listening - vote to skip instead.")I also have this issue. I can summon
my Red instance to a voice channel, and my alt account (with only the @\everyone role) can disconnect
the instance despite the user not being in the voice channel.
Edit: clarification, accidental ping, the sky is now on fire...
can confirm that it's the same for me also
What Red version are you using?
3.5.9
Cog name
Audio
Command name
disconnect
What did you expect to happen?
summon
command - thedisconnect
cmd should also check if the user (who is invoking the command) actually is in the VC before letting them disconnect the bot from the VC - where it's already playing songs along with other humans.What actually happened?
It lets anyone who is not in the VC, run the command resulting in the bot getting disconnected from the VC, leading to an unpleasant experience.
How can we reproduce this error?
audioset vote 0
<p>mock
anyone to run<p>disconnect
Result - It should let that user x disconnect the bot without having to be there in the VC.Same result with or without the human. (Meaning if the bot is alone or with other users doesn't matter)
Anything else?
N/A