The library doesn't allow for running two different bots in the same guild - voice connections are tracked only by a guild ID, so two bots are unable to share the same guild.
This should be resolved, e.g. passing an optional context parameter when creating/accessing voice connections to allow them to be separated.
This should be non-breaking and allow the current behaviour. The majority of users will probably only run a single bot in the process, and so forcing them to specify a context when creating these voice connections is unnecessary.
The library doesn't allow for running two different bots in the same guild - voice connections are tracked only by a guild ID, so two bots are unable to share the same guild.
This should be resolved, e.g. passing an optional context parameter when creating/accessing voice connections to allow them to be separated.
This should be non-breaking and allow the current behaviour. The majority of users will probably only run a single bot in the process, and so forcing them to specify a context when creating these voice connections is unnecessary.