You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an official stance has been made that voice receive is not officially supported for bots I see no point in trying to keep up with the continued breaking changes it is receiving.
At the time of opening this issue you can still use voice receive by manually setting a no-operation sending handler with canProvide() set to false. This will cause the send system to be started which is now a requirement for receiving to work (apparently). Turns out this was a breaking change to the UDP discovery that took a year to be documented by discord.
I will from now on see voice receive as low priority until discord decides to document its behavior and declare it officially supported. When something is broken without workarounds I will try to find time to fix it or look for a workaround but it will not be something I will prioritize my time on.
As an official stance has been made that voice receive is not officially supported for bots I see no point in trying to keep up with the continued breaking changes it is receiving.
At the time of opening this issue you can still use voice receive by manually setting a no-operation sending handler withTurns out this was a breaking change to the UDP discovery that took a year to be documented by discord.canProvide()
set to false. This will cause the send system to be started which is now a requirement for receiving to work (apparently).I will from now on see voice receive as low priority until discord decides to document its behavior and declare it officially supported. When something is broken without workarounds I will try to find time to fix it or look for a workaround but it will not be something I will prioritize my time on.
Official statements were made here: discord/discord-api-docs#808
Tracking issue for voice receive is here: discord/discord-api-docs#365
The text was updated successfully, but these errors were encountered: