Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicitly prevent the bot from connecting to two servers' voice channels at the same time #52

Closed
svioletg opened this issue Aug 15, 2023 · 1 comment
Assignees
Milestone

Comments

@svioletg
Copy link
Owner

It's currently advised in documentation to not use the same instance of bot for more than one voice channel at a time in different servers, as doing this causes issues that for the time being I am not able to sort out. It would be better to have the bot actually detect if this has been attempted, and prevent it if so. A config option can be created so that this is left optional.

@svioletg svioletg self-assigned this Aug 15, 2023
@svioletg svioletg added the enhancement New feature or request label Aug 15, 2023
@svioletg svioletg added this to the dev.34 milestone May 20, 2024
@svioletg svioletg changed the title [Feature] Explicitly prevent the bot from connecting to two servers' voice channels at the same time Explicitly prevent the bot from connecting to two servers' voice channels at the same time Jun 2, 2024
@svioletg svioletg removed the enhancement New feature or request label Jun 2, 2024
@svioletg
Copy link
Owner Author

svioletg commented Jun 8, 2024

Doesn't reference the server, but a check to see if the channel is the same has been put in, so this will work for checking servers implicitly. Although, it may be good to have a command to move the bot to a new channel in the future.

@svioletg svioletg closed this as completed Jun 8, 2024
svioletg added a commit that referenced this issue Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant