Ban Lookup

Ban lookup checks a ticket's opener against the ban lists you choose when the ticket opens, then shows staff a private card with what it found: banned or not, the reason, when, until when, and who issued it where the source says so. It is built for ban appeal categories, so staff can review an appeal without hunting through four dashboards.

Sources

Each source runs in parallel and gets 5 seconds. A source that is slow, rejects its key, or errors shows as Unavailable on the card with a hint. The ticket always opens.

When a support flow checks bans while the member waits for the bot to answer a button press, the check gets about 1.8 seconds instead, because Discord only waits 3 seconds for a reply. A source that misses that window counts as not checked, so the flow can send the member down a "couldn't check" path rather than telling them they have no ban.

Turn it on for a category

The opener never sees the card. It is not posted as a normal ticket message, so it never appears in a transcript or in the transcript DM.

Discord server bans

No connection is needed. The bot needs the Ban Members permission to read the ban list; without it the source shows as unavailable with a reminder to grant it.

With View Audit Log as well, the card adds the date and the moderator for bans still in the audit log (Discord keeps it for 45 days). Discord bans have no expiry.

BattleMetrics

BattleMetrics bans are matched by SteamID, so the opener needs to have linked their Steam account and shared it with your server. See Linked Accounts. Without one, the source shows No account and nothing is sent to BattleMetrics.

The card shows the newest active ban, its reason, when it was issued, when it expires, the admin who issued it and the server it was issued on.

Roblox

Roblox bans come from Roblox's Open Cloud user restrictions API for one experience. Ticket Tool finds the opener's Roblox account through Bloxlink first (see Roblox Lookups), then through a Roblox account they linked and shared.

The card shows the private reason (or the reason shown to the player), the start date, when a timed ban ends, and whether alt accounts are included.

Steam

Steam's global record comes from the Steam account the opener shared with your server. Steam reports counts and the days since the last ban, not reasons, so it is shown as context: for example "1 VAC ban, trade banned". Steam results follow the Steam profile cache, which refreshes daily.

Game server plugins

Minecraft, FiveM and RedM, Garry's Mod, Rust and CS2 bans are reported by a plugin on your own server, which answers over an outbound connection. Ticket Tool never connects to your server or its database. See Game Server Plugins for setup.

• How the opener is matched: Minecraft by the account they linked in game, FiveM and RedM by their Discord ID, and Garry's Mod, Rust and CS2 by the Steam account they shared with your server.
• What the card says when it can't check: Not set up with no plugin key, Unavailable when the plugin is offline or doesn't answer in time, and a note such as No Steam account shared with this server when there is nobody to look up.
• Ban source: the card names it, such as LiteBans, txAdmin, ULX, SAM or CS2-SimpleAdmin.
• Minecraft links made on another server are only a claim on yours, so their result is never counted as a ban or a clean record: {bans.minecraft.status} is claimed. See Verified here, claimed elsewhere.

Staff buttons

Ban results are not stored anywhere else. Save to notes is the only way to keep a record on the ticket.

Variables

Use these in the category's messages and in support flows. In messages the opener can see, keep reasons out unless you mean to share them.

• {bans.count}: How many checked sources report a ban
• {bans.any}: true if any source reports a ban, false if none do
• {bans.<source>.banned}: true or false for one source
• {bans.<source>.reason}: The ban reason, when the source gives one
• {bans.<source>.created}: When the ban started (YYYY-MM-DD)
• {bans.<source>.expires}: When it ends (YYYY-MM-DD), or never for a permanent ban
• {bans.<source>.actor}: Who issued it, when the source says
• {bans.<source>.status}: checked, unavailable, no_account, not_set_up or claimed (Minecraft only: the account wasn't verified on your server)

Replace <source> with discord, battlemetrics, roblox, steam, minecraft, fivem, gmod, rust or cs2, as in {bans.battlemetrics.reason}. If no source could be checked, {bans.count} and {bans.any} are empty, so an outage never reads as a clean record. The variables reference lists every variable in one place.

Ban appeal flows

Add a Condition node and pick the Is banned preset, then choose a source or Any source. Banned members take the Banned branch; everyone else, including members whose source was unavailable, takes the else branch.

The Ban appeal with ban lookup template, under Automations → Flows → Templates, is a ready-made appeal panel: it checks the member's bans, tells someone with no ban on record so, and collects the appeal in a form either way. See Ban appeals for a full walkthrough.

Troubleshooting