#Transcript bug with username who opened ticket.
1 messages · Page 1 of 1 (latest)
Hi there @modest palm. This is not a bug. You can set this yourself if you go under the Transcript portion of the Advanced Settings for that panel. It is actually using {user_name}#{user_tag} by default. You will need to have
Premium, however, to do this.
It is a bug, because it just doesn't work if the user is not in the server anymore and it works normally if the user is in the server.
This is wrong
This is right
@long thunder <-- This is the "user" shown
With Discord, if they are not in the server that the bot is in then it is unable to pull information on that user. Same as us. We cannot see people not in the same server as us.
I know, i am just saying that tickettool doesn't handle left user correctly in the ticket
Ticket transcript*
Then why does it show the Username#Discriminator in the "Users in transcript" section
That doesn't make sense
If it can be shows there, then it can also be shown as the username
With username i mean this
It shows correctly when they rejoin.
What?
You don't get it, that is the whole issue, the user is displayed wrong, because they are not in the server and can be displayed correctly, if they use the "Users in transcript" Username#Discriminator as the username in the ticket transcript
“You can set this yourself if you go under the Transcript portion of the Advanced Settings for that panel.”
What I recommend is:
- With a Premium subscription navigate from the panel of choice > Advanced Settings > Transcripts > Edit Transcript Message
- Click the link to see the variables you can use
- Change the variables you are mentioning to what you feel they need to be to suit your needs
“It is actually using
{user_name}#{user_tag}by default.”
Not sure why the message was rejected for use of headers and warned me about hyperlinks (which were not used) but anyways, I’ll repost differently.
Discord bots (including TicketTool) fetch live data about users via the Discord API. When a user leaves the server, Discord restricts access to certain user information with whom you do not share a server or friendship with. This applies to bots also, leading it to fail to display correctly when the user has left the server.
You will need to change the variables to one of the other options available as instructed above for your use case instead.
I understand the confusion. You’re seeing a discrepancy because the ‘Ticket Owner’ field pulls user data directly from Discord’s API, which fails when the user leaves the server, resulting in the display you described as [UserID]#[UserID].
This isn’t technically a bug; rather, it’s a limitation Discord has implemented in its API.
