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
When attempting to play a song using the play command in the Discord music bot, the bot crashes and throws a DiscordAPIError with code 50035. This error specifically mentions "Invalid Form Body content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length."
Steps to Reproduce
Join any voice channel.
Use the bot command /play to play a song.
Bot attempts to play the song but crashes with the mentioned error.
Expected Behavior
The bot should successfully play the requested song without any errors.
Actual Behavior
The bot crashes and logs the following error: "Invalid Form Body content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length."
The issue seems to be related to the bot's inability to find or use ffmpeg properly, despite attempts to locate it via various methods as outlined in the error logs.
The text was updated successfully, but these errors were encountered:
When attempting to play a song using the play command in the Discord music bot, the bot crashes and throws a DiscordAPIError with code 50035. This error specifically mentions "Invalid Form Body content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length."
Steps to Reproduce
Join any voice channel.
Use the bot command /play to play a song.
Bot attempts to play the song but crashes with the mentioned error.
Expected Behavior
The bot should successfully play the requested song without any errors.
Actual Behavior
The bot crashes and logs the following error: "Invalid Form Body content[BASE_TYPE_MAX_LENGTH]: Must be 2000 or fewer in length."
Operating System: macOS 12.3
Node.js Version: v20.15.1
discord.js Version: 14.15.3
discord-player Version: 6.6.10
ffmpeg Version: Not specified
Additional Context
The issue seems to be related to the bot's inability to find or use ffmpeg properly, despite attempts to locate it via various methods as outlined in the error logs.
The text was updated successfully, but these errors were encountered: