Describe the bug
When you are running two bots or more simultaneously and you use the buttons, the bots are connected initially.
To Reproduce
Steps to reproduce the behavior:
Start the bot on Server A and queue 2 songs.
Make sure you are playing the 1st song
Start the bot on Server B by queuing 1 song
Make sure that song is playing
While in Server B, click the next button [1st button]
OR
Go back to Server A and click the next button [1st button]
Both bots will try to play the next song .
You should see the error
Expected behavior
The slash commands on each bot should be independent of one another.
Additional context
next , prev, shuffle, play-pause buttons are all connected between the two bots initially.
It seems that when you start a second bot and play the FIRST song , while the first bot is already playing music,
the buttons are somehow connected. But if you add a second song on the second bot, the buttons become unconnected
Describe the bug When you are running two bots or more simultaneously and you use the buttons, the bots are connected initially.
To Reproduce Steps to reproduce the behavior:
Start the bot on Server A and queue 2 songs.
Make sure you are playing the 1st song
Start the bot on Server B by queuing 1 song
Make sure that song is playing
While in Server B, click the next button [1st button] OR Go back to Server A and click the next button [1st button]
Both bots will try to play the next song .
You should see the error
Expected behavior The slash commands on each bot should be independent of one another.
Additional context next , prev, shuffle, play-pause buttons are all connected between the two bots initially. It seems that when you start a second bot and play the FIRST song , while the first bot is already playing music, the buttons are somehow connected. But if you add a second song on the second bot, the buttons become unconnected