Blocks a member, or everyone holding a role, from opening tickets in this server.
The bot first applies the server's Command Access rules for /tickets blacklist add, checks that Tickets is enabled ("❌ Tickets is not enabled for this server."), and requires the Manage Server permission: "You need Manage Server to do that." Fill in exactly one of member or role; both or neither answers "Pick a member or a role, not both."
The reason option is optional, kept to 500 characters, and is only ever shown to staff. The days option is optional too: from 1 to 365, the block lifts by itself that many days from now. Without it the block lasts until someone unblocks. The bot confirms privately, without pinging anyone: "🚫 @target can no longer open tickets." or, with days, "🚫 @target cannot open tickets until" the date and time, shown in each reader's own time zone. Blocking someone who is already blocked updates the stored reason and the end.
What blocked members experience: every way of opening a ticket answers "You are not able to open tickets in this server.", the panel buttons included. They never see the reason. The check runs before support hours, cooldowns and limits, and no role is exempt from it, not even the roles listed under "Roles that skip these limits". Staff can still open a ticket for a blocked member with /ticket open, which skips the blocklist.
Good to know
- Blocking does not close tickets the member already has open.
- A block on the member wins over a block on one of their roles when the reason is looked up.
- A block stops counting the moment its time is up. The bot then deletes it and records that it was lifted.
- /tickets blacklist list shows the current entries; /tickets blacklist remove lifts one.
- The dashboard lists, adds and removes entries too, under 1 Opening, Blocked from tickets, with the same choice of how long.