Game Accounts

Show each member's Roblox, Steam and FiveM or RedM account on their tickets, use them in messages, and require them before a ticket opens

Game accounts put a member's Roblox and Steam accounts, and their player on your FiveM or RedM server, right on their ticket, so your staff know who they are in your game without asking. Roblox accounts come from Bloxlink, the verification bot most Roblox servers already use. Steam accounts are linked by the member through the official Sign in through Steam page. FiveM players come from your own game server, through the free TicketCord resource you add to it (see FiveM and RedM). It is for any server that supports players of a Roblox, Steam or FiveM game.

Game accounts work on every plan, Free included. Each platform is off until you turn it on, and nothing is shown or required before that. Only the bot owner can add, replace or remove the Bloxlink key and the FiveM key; dashboard staff see whether a key is saved.

What staff see

When a ticket opens in a server with a platform turned on, the bot posts a Linked accounts message in the ticket:

  • Roblox: Account (display name and username) and ID, Created (when, and how old the account is), Banned (Yes or No), and Group role in your Roblox group when you set a group ID (Not in the group when the account is not a member). A Roblox profile button opens the profile.
  • Steam: Account (profile name) and ID (the SteamID64), Created, VAC bans, Game bans, Trade ban (None, Probation or Banned) and Community ban (Yes or No). A Steam profile button opens the profile. Steam only shows the creation date for public profiles; a private profile shows Profile: private, and its bans still show.
  • FiveM (or RedM): labelled lines with the Player name, Character, Job and Gang, Last seen (when the ticket opened if they were in game, otherwise when they last left; Discord keeps the time current, for example "3 hours ago"), Playtime, Banned (No, until a date, or permanently, for an active txAdmin ban), and how many txAdmin Warns and Bans they have. The message does not show a ban's reason or the admin who gave it, because the member can see the message; the ticket's page in the dashboard does (see FiveM and RedM).
  • A member who has no account for a platform shows Not verified with Bloxlink in this server (Roblox), Not linked (Steam) or Not seen on the game server with this Discord account (FiveM). When Steam is on, the message has a Link Steam button the member uses to link, change or remove their Steam account (see Link Steam). Staff who press it get a link for their own account, not the member's. When Roblox is on and the member is not verified, the message has a Verify with Bloxlink button (see Verify with Bloxlink).

The same details show on the ticket's page in the dashboard, and they are saved with the ticket as they were when it opened. On Pro and higher plans, AI Help drafts and the ticket summary also use them, for example to explain to staff why a member is banned. Atlas never promises an unban or decides an appeal, and its answers to members do not use them.

To stop posting it, turn off Post linked accounts in new tickets (see Settings). Members use the Link Steam button on this message, so with Steam on and this off, they can only link Steam if you require it. On Basic and higher plans you can also reword it or hide its Link Steam button: it is Linked accounts on the Messages page.

Set it up

Open the settings

Open General → Game accounts in your server's settings.

Roblox: add your Bloxlink key

Bloxlink must be in your server, and members must be verified with it. Turn on Roblox; its settings open under the switch. On Bloxlink's developer page (Open Bloxlink's developer page under the key field), create a server API key for this server, then paste it into Bloxlink server API key and click Save key. TicketCord checks the key with Bloxlink before saving it; a key Bloxlink rejects is not saved. Saving the key turns Roblox on, with nothing else to save. Roblox cannot stay on without a key: until you save one, your changes on this card cannot be saved, and the group and requirement settings stay hidden. The key is stored encrypted and is never shown again: use Replace key to change it. Remove key also turns Roblox off and clears its requirement. If Bloxlink later stops accepting the key, the settings show Bloxlink stopped accepting this key and new tickets leave Roblox out until you replace it.

Roblox: add your group (optional)

To show each member's role in your Roblox group, enter the Roblox group ID: the number in your group's link on Roblox.

Steam: turn it on

Turn on Steam in the same card. Nothing else is needed: members link their own Steam account with the Link Steam button.

Choose what happens

Turn on Require a verified Roblox account or Require a linked Steam account if members must have that account before they open a ticket, and leave Post linked accounts in new tickets on to post the message described above. Save your changes.

FiveM and RedM

TicketCord shows each member's player from your FiveM or RedM server: their character, job, playtime, and the warns and bans your staff gave in txAdmin. Your game server sends this to TicketCord through the TicketCord resource, a small open-source script you add to the server. It runs on your server only: players never download it.

Connect your game server

Turn on FiveM

Open General → Game accounts, turn on FiveM & RedM and save.

Create a key

Click Create key. This also turns FiveM on if you have not saved it yet. The key is shown once: copy the lines under Your new key and keep them safe. Anyone with the key can send player details to your tickets. If it leaks, click Replace key: the old key stops working at once.

Install the resource

Click Download, unzip the file and put the ticketcord folder in your server's resources folder.

Add the key to server.cfg

Add the two lines you copied to server.cfg:

set ticketcord_key "tcfm_..."
ensure ticketcord

Use set. Never use sets or setr: they publish the value, and anyone could read your key from the server list.

Restart

Restart the server, or type refresh and then ensure ticketcord in the txAdmin console. Within a minute the settings show Connected to your server's name, with its framework, players online and how many players are matched to Discord.

Type ticketcord in the server console to see the resource's state: its version, when it last reached TicketCord, and the last error.

How members are matched

FiveM tells the server a player's Discord account once the player allows FiveM to read it, in a popup inside the Discord desktop app. TicketCord remembers it: a player matched once stays matched, even if they later play without Discord running. A member who opens a ticket is shown as the player your server last saw with their Discord account. If none is found and the member linked Steam (see Link Steam), the player with that Steam account is used.

Beyond allowing that FiveM popup, members link nothing with TicketCord for the Discord match, and nothing changes for players. Only the Steam fallback needs the member to have linked Steam.

What staff see

  • In the ticket: the Linked accounts message described in What staff see, plus Last downed or Last died (when, by whom when it was another player, and the weapon), Last left (why the player last left, for example a crash), Server restarted when your game server restarted shortly before the ticket opened, and Other accounts (how many, and how many are banned).
  • On the ticket's page in the dashboard: the same details, plus the newest warns and bans with their reason, the admin's txAdmin name, the date, and whether a ban ended or was revoked; recent sessions with why each ended; recent deaths and kills with the other player and the weapon; your game server's starts and restarts in the day before; and the member's other accounts.
  • In AI Help drafts and the ticket summary (Pro and higher): the same, so Atlas can tell staff, for example, who killed the member at the time they mention, or that the server restarted just before their items went missing.

While a ticket is open, its details follow the game: when the member joins, leaves or dies, or gets a warn, ban or revoke, the Linked accounts message and the ticket page update. Warns and bans count only while they are in force; a revoked one stays in the history, marked Revoked.

Warns and bans are known from when your server connected. To show a ban's reason in the ticket itself, add {fivemBanReason} to the Linked accounts message or a welcome message: the member will see it.

What your server sends

Always, to match players to members: each player's name, their Discord, Cfx.re and Steam IDs when FiveM has them, a fingerprint of their FiveM license (never the license itself), and when they join and leave, for playtime and last seen.

The rest is on unless you turn it off under What your server sends. Off means your server stops sending it, and it shows nowhere: not in tickets, messages, the dashboard or Atlas. When you save, open tickets drop it too; a Linked accounts message already posted catches up the next time that member's game details change.

SwitchWhat your server sends
Character and jobThe current character's name, job and gang, with Qbox, QBCore or ESX. Other frameworks show the player without a character.
txAdmin warns and bansWarns, bans and revokes: the reason and the admin's txAdmin name.
SessionsWhy each player left, as FiveM reports it (for example a crash or a timeout). Any address in it is removed first.
Deaths and killsWho downed or killed whom, when, and the weapon. With Qbox and QBCore a player is first downed (last stand), then dies if they bleed out; both are recorded. Who did it comes from the game server's own damage record, so a player cannot blame someone else.
Server restartsWhen your game server starts or stops, and restarts txAdmin announces.
Other accountsNothing extra: TicketCord finds the member's other players among those your server already sent, by their Discord or Steam account.

Never IP addresses, hardware IDs or chat. The resource only calls out to TicketCord and opens no ports. Every request is signed with your key, and the key itself is never sent.

Players not seen for a year are forgotten, warns and bans are kept for two years, and sessions, deaths and restarts for 30 days. To delete everything your server sent, including what tickets show of it, open Stored players under FiveM and click Delete FiveM data. Removing the key stops new data; it does not delete what was sent.

Members link Steam themselves. Each link is for one server: a member who opens tickets in two of your servers links Steam in each.

  1. The member presses Link Steam on the Linked accounts message in their ticket. The bot replies with a private Sign in through Steam link that only they can see. When your server requires Steam, the reply they get instead of a ticket already has this link.
  2. The link works once, for 15 minutes, and only for that member in that server.
  3. On the page that opens, they click Sign in through Steam and sign in on Steam's own site. Steam tells TicketCord only their Steam ID, never their password.
  4. The page shows Steam account linked, and new tickets show the account.

To change or remove the account, the member presses Link Steam again and opens the new link: the page shows the account linked now, with Link a different Steam account and Unlink Steam.

In a server with Roblox on, the Linked accounts message of a member who is not verified has a Verify with Bloxlink button. Pressing it asks Bloxlink again and answers privately:

  • Not verified yet: "Verify your Roblox account", with a Verify with Bloxlink button that opens Bloxlink's verification page. The member verifies there, or runs Bloxlink's /verify command in your server, then presses the button on the ticket again.
  • Verified: "Roblox account verified", with the account Bloxlink found. The Linked accounts message on their open tickets (up to 5) is updated to show the account, and the button goes away.

Pressing it again within a few seconds of a "not verified" answer shows the same answer without asking Bloxlink again, and a second "not verified" stands for a minute. ModMail tickets have no button, because the member is not in the channel. You can hide the button, or reword the reply, on the Messages page (Basic and higher plans).

Require an account to open tickets

With a requirement on, a member without the account gets a private reply instead of a ticket or a form:

  • Steam: "This server asks you to link your Steam account before opening a ticket." with a Sign in through Steam button. After linking, they open the ticket again.
  • Roblox: "This server asks you to verify your Roblox account with Bloxlink before opening a ticket." with a Verify with Bloxlink button that opens Bloxlink's verification page. They verify there, or run Bloxlink's /verify command in your server, then open the ticket again. A retry a few seconds later asks Bloxlink again, so a member who just verified gets through; a second "not verified" answer stands for a minute.

The requirement applies to every panel button in the server. If Bloxlink cannot be reached, Bloxlink no longer accepts your key, or TicketCord cannot check a member's Steam link, the ticket opens anyway: an outage elsewhere never stops members from getting help. ModMail tickets are never held back. A ticket refused for a missing account shows error TC020.

Use accounts in your messages

Welcome messages and welcome designs can include these variables. Each is empty when the member has no account for that platform. Under Use in your messages in the game accounts settings, click a variable to copy it.

VariableShows
{robloxUsername}Roblox username
{robloxDisplayName}Roblox display name
{robloxId}Roblox user ID
{robloxProfile}Roblox profile link
{robloxCreated}When the Roblox account was created
{robloxAccountAge}How old the Roblox account is
{robloxBanned}Whether Roblox banned the account
{robloxGroupRole}The member's role in your Roblox group ("Not in the group" when the account is not a member)
{steamName}Steam profile name
{steamId}SteamID64
{steamProfile}Steam profile link
{steamCreated}When the Steam account was created (public profiles only)
{steamAccountAge}How old the Steam account is (public profiles only)
{steamVacBans}Number of VAC bans
{steamGameBans}Number of game bans
{steamTradeBan}Trade ban state
{steamCommunityBanned}Whether Steam banned the account from the community
{fivemName}Player name on your game server
{fivemCharacter}Current character's name
{fivemJob}The character's job and grade
{fivemGang}The character's gang
{fivemStatus}Online, Offline or Unknown (your server is not reporting), when the ticket opened
{fivemLastSeen}When the player was last on your server
{fivemPlaytime}Total playtime
{fivemWarns}Number of txAdmin warns
{fivemBans}Number of txAdmin bans
{fivemBanned}Whether a txAdmin ban is active (Yes or No)
{fivemBanReason}The active ban's reason (the member sees it)
{fivemBanExpires}When the active ban ends, or Permanent
{fivemLastLeft}Why the player last left, for example a crash
{fivemOtherAccounts}How many other accounts the member has on your server

Settings

SettingWhat it does
RobloxShows members' Roblox accounts from Bloxlink. Needs a saved Bloxlink key.
Bloxlink server API keyThe key Bloxlink gives you for this server. Owner only.
Roblox group IDShows the member's role in this Roblox group. Optional.
Require a verified Roblox accountMembers must verify with Bloxlink before they can open a ticket.
SteamLets members link Steam and shows their Steam account.
Require a linked Steam accountMembers must link Steam before they can open a ticket.
FiveM & RedMShows members' players from your FiveM or RedM server. Needs a key and the TicketCord resource.
Create key, Replace key, Remove keyThe key your game server uses. Owner only.
What your server sendsSix switches, all on by default: Character and job, txAdmin warns and bans, Sessions, Deaths and kills, Server restarts, Other accounts. See What your server sends.
Delete FiveM dataDeletes the players, warns, bans, sessions, deaths and restarts your game server sent, and the FiveM details saved on tickets. Owner only.
Post linked accounts in new ticketsPosts the Linked accounts message when a ticket opens. The variables work either way.

Good to know

  • Roblox details come from Bloxlink's link for your server, so a member verified with Bloxlink in another server shows as not verified until they verify in yours.
  • Account details are refreshed at most every 30 minutes, so a ban or a renamed profile can take that long to show on new tickets. A ticket keeps the details from when it opened.
  • Bloxlink's free server keys allow a limited number of lookups a day. TicketCord looks each member up once per ticket and remembers the answer for 10 minutes; if Bloxlink stops answering, tickets still open and show no Roblox account.
  • When a server is moved with Server restore, its members' Steam links and its FiveM players move with it. Deleting the bot deletes its Steam links and FiveM data.

Troubleshooting

ProblemCauseFix
Save key says Bloxlink rejected the keyThe key is wrong or belongs to another serverCreate a server API key for this server on Bloxlink and paste it again
Save key says Bloxlink could not be reachedBloxlink did not answerTry again in a few minutes; nothing was saved
Every member shows Not verified with Bloxlink in this serverBloxlink is not in the server, or the key was removed or revokedAdd Bloxlink, ask members to run /verify, and check the key is still saved
A member verified on Bloxlink's site but still shows as not verifiedBloxlink has no Roblox account for them in your server yet, or the last answer is less than a minute oldThey run Bloxlink's /verify command in your server, wait a minute, then press Verify with Bloxlink on the ticket (or open the ticket again)
The Steam link page says This link has expiredThe link was used already or is older than 15 minutesPress Link Steam in Discord again for a new link
A Steam account shows no creation dateThe member's Steam profile is privateNothing to fix: bans still show
FiveM settings say Waiting for your game serverThe resource is not started, or the key is not in server.cfgCheck the ticketcord folder is in resources, the two lines are in server.cfg, and restart. Type ticketcord in the server console
The console says TicketCord did not accept the keyThe key was replaced or removed, or was copied wrongCreate a new key and update server.cfg
The console says the server clock is wrongThe game server's time is off by more than 5 minutesFix the machine's time (turn on automatic time sync)
The console says FiveM is turned offFiveM & RedM is off in the game accounts settingsTurn it on and save
A member shows Not seen on the game server with this Discord accountThey denied FiveM access in the Discord app, play on another Discord account, or never joinedAsk them to quit FiveM and Discord, start Discord first, then FiveM, and click Authorize when Discord asks. They are matched the next time they join
Online shows UnknownYour game server stopped reportingCheck the server is running; it shows again within a minute
No character or job showsThe server does not use Qbox, QBCore or ESXNothing to fix: the player still shows

Last updated on

On this page