-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
<user>.tag returns username#0 if the user has the new username system #9644
Labels
Comments
Already resolved. Just needs a release. |
(#9512) |
Is there an ETA for the release? Currently handling displayName and globalName (if discriminator === "0") over ugly helper functions |
discord.js never gave an eta |
Adding onto here, @chocobearxo, this is intentional behaviour from the Discord API. See https://support-dev.discord.com/hc/en-us/articles/13667755828631#h_01H26BDRT8ASH1YVKG6HMGZ1J2 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which package is this bug report for?
discord.js
Issue description
Basically just have a user object as use the
tag
.E.g. if your username is "bob" and you are migrated into the new username system, then if you try to use
<user>.tag
where<user>
is your user object, it will return "bob#0".I am not really sure whether or not this is a discord.js issue or Discord issue. If this isn't a discord.js issue, then please let me know so I can create a different bug report for Discord itself instead. :)
Code sample
Versions
discord.js 14.11.0
node.js 16.15.1
Issue priority
Low (slightly annoying)
Which partials do you have configured?
No Partials
Which gateway intents are you subscribing to?
Guilds, GuildMembers, GuildVoiceStates, GuildMessages
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: