Role Honeypot

What is it?

This system combats botted Discord accounts that join your server. Such bots often pick all the roles offered on the server’s onboarding screen. Because they pick everything, the last question can be a simple CAPTCHA where the bot effectively claims to be a bot — Archivian sees this and promptly kicks it from the server.

Prerequisites

Community mode

This system is built on top of Discord’s onboarding screen, which is only available to servers with Community mode enabled, so you must enable it first — anyone can. See our Community Mode guide, or Discord’s own article:

Discord Help CenterEnabling Your Community ServerDiscord's help article on turning on Community mode for your server.

Baseline onboarding configured

Since it builds on Discord’s onboarding screen, your server must already have the minimal onboarding configuration done.

Quick gotchas

Keep the answer required

Don’t make the question optional — always require users to pick at least one option. This forces bots to make a deliberate choice.

Keep answers multi-select

Don’t change the answer mode from “Select multiple” to “Select one”. Bots vary in implementation; with single-select they tend to pick the first or last option, whereas multi-select makes them more likely to select all options.

It triggers on self-assign

Someone else assigning the role to a user won’t trigger the honeypot — it triggers when a user gives themselves the role outside of onboarding. For example, if a moderator can assign this role:

• it does not trigger if the moderator assigns the role to another user;
• it may trigger if the moderator assigns the role to themselves.

This is because the bot checks whether the user who assigned the role is the same as the one who received it. Registered staff members never trigger it, regardless.