-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
db!userinfo shows not a Nitro User, when i am one. #201
Comments
This is not a bug but a limitation from Discords end. Discord doesn't provide us with your nitro status so the only way for us to check if you are a nitro user is if you have a gif avatar. |
They must have just added it, or has not been implemented in JDA yet. Saw it in their documents now. | premium_type? | integer | the type of Nitro subscription on a user's account | identify | {
"id": "80351110224678912",
"username": "Nelly",
"discriminator": "1337",
"avatar": "8342729096ea3675442027381ff50dfe",
"verified": true,
"email": "[email protected]",
"flags": 64,
"premium_type": 1
} Thanks for the reply! |
That is not available to the bot API unfortunately, the bot API only receives the id, username, discriminator and the avatar. This can only be used via the OAuth API, the dashboard uses the OAuth API for example. |
Here is a real-world example that shows all the data with a fetch user request from discord https://documenter.getpostman.com/view/3863890/S1EWNaDW |
yep just missed the |
Describe the bug
db!userinfo
command on myself shows Discord Nitro User as "No", however i am a Nitro user.image of command and profile badge, can send Nitro page from profile if needed
https://imgur.com/ktg3KYy
To Reproduce
Steps to reproduce the behavior:
db!userinfo
w/ no argsExpected behavior
Unless there is a big api difference between Nitro and Nitro Classic (Early Supporter) it should show Yes in command
Screenshots
https://imgur.com/ktg3KYy
Additional context
The To Reproduce section i filled out may look sarcastic but its not i swear just following format :)
The text was updated successfully, but these errors were encountered: