Summary

There is the potential that being connected to a voice channel prior to having VNext attempt to connect you could cause VNext to stall.

While VNext will give back a 'valid' connection, and subsequently, a transmit sink, attempting to copy data into this sink results in the data being sent to the void.

Details

This may or may not be to do with an issue @alexhorner pointed out in regards to permissions also breaking VNext, but I suspect Discord may have silently broken the voice gateway. The last I confirmed this working was roughly ~a month ago, when I was working on music for my bot. Disconnecting the bot from the channel allows it to properly join again, and audio works as expected.

Steps to reproduce

• Make the bot join a voice channel, via VNext or otherwise.
• Restart the bot, as disposing the VNext connection will disconnect from the channel.
• Attempt to join again
• Get the transmit sink from VNext, and copy audio
• Observe

Notes

As I'm rather flooded with work, my ability to test this theory is limited, and was noticed while debugging my own code.