-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help #3
Comments
Is there any news? Was someone able to solve the problem? |
I'll be attempting to repair the error using a bypass today. It could be a good strategy if the error is hard to fix otherwise. However, it's important to keep in mind that a temporary bypass may not completely solve the problem and may create additional issues. Make sure to understand the implications of using a bypass before proceeding. |
So how'd that go? |
Same error, seems like its broken |
Your both bots work with the official api, which is a paid. This bot worked on an access token, and did not require api tokens. |
I tried all the steps to the letter, but the bot continues to send an error: "Couldn't send message: Couldn't get access token: failed to decode response: invalid character '<' looking for beginning of value". I think it may be a problem with the bot's configuration on Discord or with the bot's permissions to send messages in the channel where I am trying to do it. Is there anything I can do to solve this problem? ooopoison
The text was updated successfully, but these errors were encountered: