Privileged MessageContent intent limits after deploying a discord.js bot past 100 servers

Question

I maintain a discord.js v14 bot that uses prefix-based message commands, which means it relies on the privileged GatewayIntentBits.MessageContent intent, declared in the Client options and toggled on in the Developer Portal. It works correctly in my test guilds: the client logs in, messageCreate fires, and message.content is populated.

My concern is what changes as the bot grows past the roughly 100-server threshold, where Discord requires verification and approval for privileged intents. I want to understand the failure behavior before it happens in production rather than diagnosing it from logs afterward.

The documentation describes the approval requirement, but I am unclear on the operational details: whether an unapproved bot that crosses the threshold keeps working with the intent it already has, starts receiving empty message.content silently, or fails at login with a disallowed-intents error. I also want to know whether the startup warning discord.js emits about missing privileged intents reliably distinguishes "not enabled in portal" from "enabled but not approved at this scale", since the log signatures seem similar.

Specifically:

Does intent approval status change runtime behavior for a bot already connected, or only at the next login/session?
Which exact log output should I alert on to detect an intent-related regression versus a token or sharding fault?
Is migrating to slash commands the only way to remove this scaling dependency entirely?

Tasadduq Burney · Answer

Direct answer
The privileged MessageContent intent is enforced only when the gateway session is (re)identified. A bot that is already connected will continue to receive message content until it disconnects and attempts a new IDENTIFY. At that point Discord will close the session with close code 4014 (Disallowed intent(s)) if the intent has not been approved for the bot’s current guild count.
Confirmed facts

Discord requires both the Developer Portal toggle for MessageContent and explicit approval during verification once a bot reaches roughly 100 guilds.
When the limit is enforced, the gateway sends a Close frame with code 4014; discord.js surfaces this as an error during login or shard reconnect (e.g., "Shard #0 received WS Close with code 4014: Disallowed intent(s)").
The startup warning about missing privileged intents only reflects the local client view; it cannot distinguish "not toggled in portal" from "toggled but not approved at scale".
Interaction‑based commands (slash commands, buttons, modals) do not need the MessageContent because their payload is supplied in the interaction data.

Likely explanation
Already‑connected sessions are not retroactively stripped of an intent; enforcement occurs on the next IDENTIFY. Therefore a running bot may appear healthy until a restart, shard re‑identify, or resume failure forces re‑authentication.
What to monitor

Watch for the 4014 disallowed‑intents error on client login or shard ready events.
Log any messageCreate where message.content is empty while the message has no embeds or attachments – this catches partial intent loss in guilds where the intent is not granted.

Steps to verify

Open the Developer Portal for your application and check the "Bot" section: is the MessageContent toggle enabled and does an approval banner appear (e.g., "This intent is approved for verified bots")?
If you cannot see the approval status, that is the missing diagnostic detail that changes the recommendation – you must confirm whether the intent is approved before deciding to pursue verification or migrate to slash commands.

Privileged MessageContent intent limits after deploying a discord.js bot past 100 servers

1 answer

Direct answer

Confirmed facts

Likely explanation

What to monitor

Steps to verify

Your perspective belongs here.

0 question comments