Add reaction roles, autoresponder, moderation actions, and action log by Copilot · Pull Request #3 · BetterDiscord/BetterDiscordBot

Copilot · 2026-04-24T03:47:59Z

Replaces dyno.gg functionality the server currently depends on. Four feature areas were missing or incomplete: reaction roles, autoresponder, moderation actions, and action log.

Reaction Roles (`/reactionroles`)

add <channel> <message_id> <emoji> <role> — binds emoji→role on a message; bot self-reacts for discoverability
remove / list
Handles Unicode and custom emoji via stable ID-based normalisation; fetches partial reaction/message/user objects so it works on uncached messages

Autoresponder (`/autoresponder`)

toggle — per-guild on/off
add <trigger> <response> [match_type] — three match modes: contains (default), exact, startsWith
remove (with autocomplete) / list

Moderation Actions (`/mod`)

kick, ban, unban, timeout, untimeout — with kickable/bannable/moderatable guards
warn, warnings, clearwarnings — SQLite-backed warning history per guild+user
All actions emit to the existing modlog channel

Action Log (`/moderation actionlog` + `/moderation actionlogevents`)

New actionlog channel setting (separate from modlog)
Events logged: message delete/edit (before/after content), ban/unban, nickname change, role add/remove
Each event type is individually configurable via /moderation actionlogevents <event> [enable] — choose from message_delete, message_edit, member_ban, member_unban, nickname_change, role_change
All events default to enabled (opt-out model); omitting enable reports the current state for that event
Role-change diffing skipped when oldMember is partial to avoid false positives

Infrastructure

src/index.ts: fixed silent bug where array-export event files (e.g. existing joinleave.ts) were never registered; added GuildMessageReactions, GuildModeration intents and Partials.Message, Partials.Reaction
src/types/base.ts: added ReactionRole, AutoResponderEntry, Warning types; added ActionLogEvent union type and actionlogEvents per-event toggle map; extended GuildSettings with actionlog, actionlogEvents, and autoresponder
src/db.ts: added reactionrolesDB, autoresponderDB, warningsDB

Original prompt

Add more functionality to this Discord mod. We are looking to move off of dyno.gg. From that bot we currently use: reaction roles, automod, autoresponder, moderation, and action log. For some of those this bot has no equivalent, for others (like moderation and automod) it is woefully incomplete.

Created from VS Code.

…on log Agent-Logs-Url: https://github.com/BetterDiscord/BetterDiscordBot/sessions/c9e5628b-6776-4bf2-8736-3caa5d142525 Co-authored-by: zerebos <6865942+zerebos@users.noreply.github.com>

zerebos · 2026-04-24T09:43:30Z

@copilot can you make the action log configurable in some way? We don't always want to log all events. For example we might not keep join/leave logs on

Agent-Logs-Url: https://github.com/BetterDiscord/BetterDiscordBot/sessions/7f9c7049-cf46-4e7c-b033-be83da127060 Co-authored-by: zerebos <6865942+zerebos@users.noreply.github.com>

Copilot · 2026-04-24T09:48:03Z

@copilot can you make the action log configurable in some way? We don't always want to log all events. For example we might not keep join/leave logs on

Done in commit 3312ccb. Added a new /moderation actionlogevents <event> [enable] subcommand with a fixed choices dropdown covering all six logged event types:

Message Deleted (message_delete)
Message Edited (message_edit)
Member Banned (member_ban)
Member Unbanned (member_unban)
Nickname Changed (nickname_change)
Role Changes (role_change)

All events default to enabled (opt-out model), so existing setups aren't affected. Omitting the enable option reports the current state for that event type. Each event is checked independently in the handler, so nickname and role-change events can be toggled separately despite sharing the same Discord event.

Copilot

Pull request overview

Adds missing Dyno-like moderation features to the bot: reaction roles, an autoresponder module, a richer moderation command set (including warnings), and a configurable “action log” channel with multiple event types.

Changes:

Introduces new DB-backed modules for reaction roles, autoresponder triggers, and per-user warning history.
Adds /reactionroles, /autoresponder, and /mod commands, plus extends /moderation with action log configuration.
Implements new event handlers for reaction roles, autoresponder replies, and action-log event emission; updates client intents/partials and fixes event loader to support array-export event modules.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
src/types/base.ts	Extends `GuildSettings` and adds new feature types (reaction roles, autoresponder entries, warnings, action log event union).
src/index.ts	Adds intents/partials needed for new features and fixes event registration for array-export event modules.
src/db.ts	Adds new Keyv namespaces for reaction roles, autoresponder, and warnings storage.
src/events/reactionroles.ts	Adds reaction add/remove handlers to assign/unassign roles based on configured bindings.
src/events/autoresponder.ts	Adds message-create handler to match triggers and send configured responses.
src/events/actionlog.ts	Adds action log event handlers (message delete/edit, ban/unban, nickname and role changes).
src/commands/reactionroles.ts	Adds `/reactionroles add/remove/list` for managing bindings and self-reacting for discoverability.
src/commands/autoresponder.ts	Adds `/autoresponder toggle/add/remove/list` plus autocomplete for removal.
src/commands/moderation.ts	Adds `/moderation actionlog` and `/moderation actionlogevents` settings management.
src/commands/mod.ts	Adds `/mod` moderation actions and SQLite-backed warnings.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-24T10:01:35Z

+        const member = interaction.guild.members.cache.get(user.id);
+
+        if (!member) return await interaction.reply(Messages.error("That user is not in this server.", {ephemeral: true}));
+        if (!member.kickable) return await interaction.reply(Messages.error("I cannot kick that user. They may have a higher role than me.", {ephemeral: true}));


interaction.guild.members.cache.get(user.id) can be undefined even when the user is in the guild (member not cached), causing false "user is not in this server" errors and preventing kick/timeout/untimeout. Prefer interaction.options.getMember("user") (for cached interactions) or await interaction.guild.members.fetch(user.id) and reuse that for capability checks like kickable/moderatable.

Copilot · 2026-04-24T10:01:35Z

+    data: new SlashCommandBuilder()
+        .setName("mod")
+        .setDescription("Moderation actions.")
+        .setDefaultMemberPermissions(PermissionFlagsBits.ModerateMembers)


The command is gated by ModerateMembers, but the subcommands include kick/ban/unban which are separate permissions. As written, members who can timeout (but cannot ban/kick) may still be able to run these subcommands successfully. Add explicit permission checks per subcommand (e.g. KickMembers, BanMembers, ModerateMembers) and/or restructure commands so the default permission matches the most sensitive action.

Suggested change

.setDefaultMemberPermissions(PermissionFlagsBits.ModerateMembers)

.setDefaultMemberPermissions(PermissionFlagsBits.BanMembers)

Copilot · 2026-04-24T10:01:36Z

+    async clearwarnings(interaction: ChatInputCommandInteraction<"cached">) {
+        const user = interaction.options.getUser("user", true);
+        const key = `${interaction.guild.id}-${user.id}`;
+        await warningsDB.delete(key);
+        await interaction.reply(Messages.success(`Cleared all warnings for **${user.tag}**.`, {ephemeral: true}));
+    },


PR description says all moderation actions emit to the modlog, but clearwarnings currently only deletes from storage and replies to the moderator. Consider logging this action (including target user and moderator) via logModAction for consistency/auditability.

Copilot · 2026-04-24T10:01:36Z

+        const emojiInput = interaction.options.getString("emoji", true);
+        const role = interaction.options.getRole("role", true);
+        const normalizedEmoji = normalizeEmojiString(emojiInput);
+


Before storing the binding, validate that the bot can actually assign the selected role (e.g. role.editable / role not managed). Otherwise /reactionroles add can succeed but reaction handling will always fail at runtime when attempting member.roles.add(...).

Suggested change

if (role.managed || !role.editable) {

return await interaction.editReply(Messages.error("I can't assign that role. Please choose a non-managed role that is below my highest role."));

}

Copilot · 2026-04-24T10:01:36Z

+            if (message.content) embed.setDescription(message.content.substring(0, 4096));
+
+            await logChannel.send({embeds: [embed]}).catch(console.error);
+        },


These log messages may include user-generated content (message text, nicknames) containing mentions; channel.send({embeds:[...]}) can therefore ping @everyone/roles/users in the action log. Consider sending with allowedMentions: { parse: [] } to make logs non-pinging.

Copilot · 2026-04-24T10:01:37Z

+
+                        if (addedRoles.size) embed.addFields({name: "Roles Added", value: addedRoles.map(r => `<@&${r.id}>`).join(", ")});
+                        if (removedRoles.size) embed.addFields({name: "Roles Removed", value: removedRoles.map(r => `<@&${r.id}>`).join(", ")});
+
+                        await logChannel.send({embeds: [embed]}).catch(console.error);


Roles Added/Removed field values are built by joining all role mentions, which can exceed Discord's 1024-char embed field limit (causing the send to fail and the log event to be dropped). Consider truncating/splitting into multiple fields when the list is long.

Copilot · 2026-04-24T10:01:37Z

+        const description = current
+            .map(e => `**\`${e.trigger}\`** (${e.matchType})\n↳ ${e.response.substring(0, 80)}${e.response.length > 80 ? "…" : ""}`)
+            .join("\n\n");
+
+        const embed = new EmbedBuilder()
+            .setColor(Colors.Info)
+            .setTitle("Auto-Responses")
+            .setDescription(description);
+


The embed description is built from all triggers and can exceed Discord's 4096-char embed description limit in larger configs, causing the response to fail. Consider paging (you already have src/paginator.ts) or truncating the list output.

Copilot · 2026-04-24T10:01:37Z

+        )
+        .setTimestamp();
+
+    await logChannel.send({embeds: [embed]}).catch(console.error);


When sending modlog embeds, consider setting allowedMentions: { parse: [] } (and optionally disable replying-user mentions elsewhere) so user-provided reason text or IDs in fields can’t trigger @everyone/role/user pings in the log channel.

Suggested change

await logChannel.send({embeds: [embed]}).catch(console.error);

await logChannel.send({embeds: [embed], allowedMentions: {parse: []}}).catch(console.error);

Copilot · 2026-04-24T10:01:38Z

+        const description = current
+            .map(r => `${r.emoji} → <@&${r.roleId}> (in <#${r.channelId}>, msg: \`${r.messageId}\`)`)
+            .join("\n");


For custom emojis you store only the numeric ID (normalizeEmojiString), so the list output will show something like 1234567890 → @Role instead of rendering the emoji. Consider storing a display form too (original input) or resolving the emoji from interaction.guild.emojis.cache.get(id) when building the list.

Copilot · 2026-04-24T10:01:38Z

+
+        if (!match) return;
+
+        await message.reply(match.response).catch(console.error);


message.reply(match.response) will ping the author by default and will also allow @everyone/role/user mentions contained in stored responses. Consider using allowedMentions: { parse: [], repliedUser: false } (or a more targeted policy) to prevent mention spam/abuse.

Suggested change

await message.reply(match.response).catch(console.error);

await message.reply({

content: match.response,

allowedMentions: {

parse: [],

repliedUser: false,

},

}).catch(console.error);

Initial plan

ff7ff93

Copilot AI assigned Copilot and zerebos Apr 24, 2026

Copilot started work on behalf of zerebos April 24, 2026 03:48 View session

feat: add reaction roles, autoresponder, moderation actions, and acti…

9db9e57

…on log Agent-Logs-Url: https://github.com/BetterDiscord/BetterDiscordBot/sessions/c9e5628b-6776-4bf2-8736-3caa5d142525 Co-authored-by: zerebos <6865942+zerebos@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add functionality to Discord mod to replace dyno.gg features~~ Add reaction roles, autoresponder, moderation actions, and action log Apr 24, 2026

Copilot finished work on behalf of zerebos April 24, 2026 04:00

Copilot AI requested a review from zerebos April 24, 2026 04:00

Copilot started work on behalf of zerebos April 24, 2026 09:43 View session

feat: make action log events individually configurable

3312ccb

Agent-Logs-Url: https://github.com/BetterDiscord/BetterDiscordBot/sessions/7f9c7049-cf46-4e7c-b033-be83da127060 Co-authored-by: zerebos <6865942+zerebos@users.noreply.github.com>

Copilot finished work on behalf of zerebos April 24, 2026 09:49

zerebos requested a review from Copilot April 24, 2026 09:55

Copilot started reviewing on behalf of zerebos April 24, 2026 09:56 View session

Copilot AI reviewed Apr 24, 2026

View reviewed changes

	.setDefaultMemberPermissions(PermissionFlagsBits.ModerateMembers)
	.setDefaultMemberPermissions(PermissionFlagsBits.BanMembers)

+        if (role.managed || !role.editable) {
+            return await interaction.editReply(Messages.error("I can't assign that role. Please choose a non-managed role that is below my highest role."));
+        }

	await logChannel.send({embeds: [embed]}).catch(console.error);
	await logChannel.send({embeds: [embed], allowedMentions: {parse: []}}).catch(console.error);


		if (!match) return;

		await message.reply(match.response).catch(console.error);

-        await message.reply(match.response).catch(console.error);
+        await message.reply({
+            content: match.response,
+            allowedMentions: {
+                parse: [],
+                repliedUser: false,
+            },
+        }).catch(console.error);

Conversation

Copilot AI commented Apr 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reaction Roles (/reactionroles)

Autoresponder (/autoresponder)

Moderation Actions (/mod)

Action Log (/moderation actionlog + /moderation actionlogevents)

Infrastructure

Uh oh!

zerebos commented Apr 24, 2026

Uh oh!

Copilot AI commented Apr 24, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Apr 24, 2026 •

edited

Loading

Reaction Roles (`/reactionroles`)

Autoresponder (`/autoresponder`)

Moderation Actions (`/mod`)

Action Log (`/moderation actionlog` + `/moderation actionlogevents`)