Whoop

Friendly Discord bot for the WebODM community.

Getting Started

Requirements:

• Node.js 18+
• A Discord bot token
• A Discord application ID

Install dependencies:

npm install

Create a .env file:

DISCORD_TOKEN=your_bot_token
APP_ID=your_application_id
MODERATOR_ROLE_NAME=Moderator

MODERATOR_ROLE_NAME is optional and defaults to Moderator.

Register slash commands:

npm run register

Start the bot:

npm start

For development:

npm run dev

Move Command

The bot includes a Move message context-menu command. When a moderator or administrator right-clicks a message and chooses Apps -> Move, the bot replies with an ephemeral channel/thread dropdown, replays the message through a webhook so the original author's display name and avatar are preserved, and deletes the original message after the replay succeeds.

Required bot permissions:

• Manage Webhooks in the destination channel, or in the parent channel when moving into a thread
• Manage Messages, View Channel, and Read Message History in the source channel

The command is registered with Discord's Manage Messages default permission so it is hidden from most members. Runtime access is still restricted to administrators or members with the configured moderator role name.

Mention Block

Moderators can revoke a member's ability to @ mention people without muting or banning them:

• /mentionblock add user:@someone - blocks the user from @ mentioning
• /mentionblock remove user:@someone - allows them to @ mention again
• /mentionblock list - shows who is currently blocked

When a blocked user posts (or edits) a message containing a mention in any channel, the bot deletes the message and sends the user a DM asking them not to @ mention people. The command uses the same access rules as Move: hidden behind Discord's Manage Messages default permission, and re-checked at runtime against administrators and the moderator role.

The blacklist is stored in data/mention-blocks.json and survives restarts. That directory is gitignored.

Required bot permissions: Manage Messages in every channel that should be policed. The bot silently skips channels where it cannot delete, and logs a warning.

Notes:

• Detection covers real Discord mentions only: @user, @role, and @everyone/@here. Plain text like @bob that Discord does not turn into a mention is not detected, by design.
• Replying with the ping toggle on does not count as a mention on its own.

Language Filter

The bot watches every new and edited message in the server for words from a blacklist. When it finds one it:

1. Re-posts the message in the same channel through a webhook, with the author's display name and avatar, and each offending word replaced by ****. Attachments are carried over.
2. Deletes the original message.
3. Sends the author a polite DM reminding them to keep the conversation civil.

Bots cannot edit other people's messages, which is why the message is replaced rather than edited in place. The re-posted copy loses its "replying to" reference and any reactions it had.

The blacklist lives in swear-words.txt in the repository root, one word per line. Matching is case-insensitive and whole-word (so class never trips on ass), automatically covers common endings (shitty, fucking), stretched spellings (fuuuck) and basic leet-speak (sh1t, a$$). Compound words need their own entry. The file is read at startup, so restart the bot after editing it. See the comments at the top of the file for details, and the disabled "milder words" section at the bottom if you want to be stricter.

Required bot permissions in every channel that should be policed:

• Manage Messages, View Channel, and Read Message History to delete the original
• Manage Webhooks (in the parent channel for threads and forum posts) to re-post the censored copy

If the bot can delete but has no webhook access it deletes the message anyway and includes a censored copy in the DM so the author can re-post it. If it cannot delete, it logs a warning and leaves the message alone.

The filter needs the privileged Message Content gateway intent. Without it Discord sends empty message text to the bot and nothing is detected. Enable it in the Discord Developer Portal under your application -> Bot -> Privileged Gateway Intents -> Message Content Intent. If it is not enabled, the bot fails to log in with a Used disallowed intents error.

License

Licensed under AGPLv3. See the LICENSE file.