Describe the bug
When the bot is not connected (because of an updating process, restart or disconnect) to the server, but a dynamic voice event takes place, the bot loses all tracking information about the dynamic channels. Furthermore: When the bot process terminates (because of an updating process or restart), the bot stops tracking the channels and instead closes any open dynamic voice channel and its dedicated text channel.
To Reproduce
Steps to reproduce the behavior:
Create a dynamic voice channel by connecting to the corresponding "new private/public voice" channel
Stop the bot by running stop in an administrator channel as a user with administration rights
Start the bot again
Expected behavior
The bot should regain tracking information
Actual behavior
The bot behaves as if there were no open dynamic voice channels. Its corresponding voice channel, text channel and server role are now orphans and need to be removed manually by an server administrator.
(The bot closing all open dynamic channels on process termination is intended behaviour as of minimizing workload on bot update process. But it is definitely not expected behaviour for users as they get kicked on every update. This circumstance outlaws an update process while any member is connected to a voice channel)
Used bot version and device information:
Bot Version: v0.3.0 (65fd02d)
Additional context
Add any other context about the problem here.
Describe the bug When the bot is not connected (because of an updating process, restart or disconnect) to the server, but a dynamic voice event takes place, the bot loses all tracking information about the dynamic channels. Furthermore: When the bot process terminates (because of an updating process or restart), the bot stops tracking the channels and instead closes any open dynamic voice channel and its dedicated text channel.
To Reproduce Steps to reproduce the behavior:
stopin an administrator channel as a user with administration rightsExpected behavior The bot should regain tracking information
Actual behavior The bot behaves as if there were no open dynamic voice channels. Its corresponding voice channel, text channel and server role are now orphans and need to be removed manually by an server administrator. (The bot closing all open dynamic channels on process termination is intended behaviour as of minimizing workload on bot update process. But it is definitely not expected behaviour for users as they get kicked on every update. This circumstance outlaws an update process while any member is connected to a voice channel)
Used bot version and device information:
Additional context Add any other context about the problem here.