Skip to main content

​
Adding Filters

Use /name-filters add to block usernames or nicknames that match specific words or patterns. Choose between phrase filters (simple text matching) or regex filters (pattern matching).
Phrase filters are easier and safer to use — they match any name containing the exact text. Matching is case-sensitive: scam won’t catch Scam. For case-insensitive matching, use a regex filter starting with (?i).
Regex filters are more powerful but require testing to avoid false positives.

​
Examples

Right after a filter is added, Hashbot previews any current members that match it and offers a Confirm and Ban button — so a bad filter can’t quietly hit your community, and a good one can clean up immediately.

​
Bulk-Generate from a Role (Subscribers only)

/name-filters add role:@Staff creates exact-match filters for every member of a role in one go — ideal for protecting your whole team from impersonation. Names shorter than 4 characters or shared by other members are skipped automatically, and nothing is added until you confirm.

​
Removing Filters

Use /name-filters remove with the exact filter text to delete it from your blocklist.
Browse your full filter list on the Hashbot Dashboard Text Filters page — you can search and remove filters visually there. /name-filters list gives a quick count and dashboard link.

​
Bulk Management

For bulk filter management, the Dashboard is the fastest option:
  • Search your filter list by keyword
  • Import filters from a JSON file (Subscribers)
  • Export your entire filter list (Subscribers)
  • Filter Optimizer — identifies redundant or overlapping filters
From Discord, Subscribers can also use /name-filters export and /name-filters import for file-based backup and restore, and admins can wipe the list with /name-filters reset-all (a backup file is generated first).

​
Tips

  • Use phrase filters for clear, specific keywords
  • Test regex filters on regex101.com (Java flavor) before adding
  • Run /name-filters test test-username:<name> to verify a filter catches what you expect
  • Run /cleanse after adding new filters to catch existing members