-
Notifications
You must be signed in to change notification settings - Fork 24
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
Unrelated, but #8
Comments
As far as I can tell this is some sort of new anti-sniping feature. Sadly don't know of any way around it other than to attach a valid payment source. I will leave this issue open for awhile on the off chance someone has more knowledge on it than I do. |
I have made some changes to the JSON payload that would properly reflect manually redeeming a code on Discord. Basically I nulled their values out. I haven't gotten any more reports on this error response from the people that were helping me pe-test this build. I will leave this open for a few more days just to confirm with the rest of the community here. See the latest release (3.2.9) to test the changes. |
Got bad news this morning, the issue still persists for some. The last release was kind of a last ditch effort so I'm just kind of scratching my head. |
Something was posted to another repo about this issue earlier this morning. Their claim is that this message is a false positive in relation to the xbox promo codes for 3 months nitro for $1. They go on to say that this is basically a case where people are posting these codes as redeemable gifts when they are in fact not redeemable via the regular discord api. Here's a link to the comment if anyone wants to read further, still not sold on that theory but it may be correct: |
So I finally got the error on another account and then tried the code on my legit account and the picture above was the server response. It would seem as if the error is indeed linked in with the 3 month promo they have with microsoft, as I have purchased it on one account and not the other. Closing this issue for good! |
issue #8 officially resolved. case handling updated to reflect our new understanding of the api.
issue #8 officially resolved. case handling updated to reflect our new understanding of the api.
So sorry if this isn't meant for issues, but I have a question.
It seems Discord is requiring a payment source now? I do have Nitro on my account but no matter what, the "valid" codes always require a payment source. Before, it wasn't like this, these codes would count as Nitro "credit"
Is this a new anti-sniping feature to get the payment info of accounts?
The text was updated successfully, but these errors were encountered: