Dyno prefix commands stopped working? Your options

Before you start

• Identify whether your failing action is a Dyno default command or one you created in its Custom Commands module.
• For the hosted-bot option, use a Discord server you manage and a disposable text channel. Record its existing permission overwrites before testing.

1. What changed, and when?

   Dyno’s September 1, 2026 announcement says default prefix commands began redirecting to slash commands on September 22 and stop responding on October 13. Slash commands remain available; custom prefix commands and mention commands are exempt. As of this guide’s October 6 review, the final cutoff is still ahead.

   Dyno’s official prefix-command announcement

2. Option A: keep Dyno

   For a default moderation action, type / in Discord, select the command belonging to Dyno, fill in its fields and send it. Review Dyno’s command documentation and your server’s command settings if the action is unavailable.

   For a custom response, open your server’s Dyno dashboard → Modules → Custom Commands. Enable the module, open Settings, then Add Command. Choose a unique name, enter a response, review its permissions and save. Invoke that name with your server’s Dyno prefix. Follow Dyno’s custom-command documentation for advanced behavior and limits.

   Dyno command documentation · Dyno Custom Commands setup

3. Option B: create your own hosted bot

   Build Discord Bots currently supports typed Moderation commands: !lock [reason], !unlock and !ban <@user> [reason]. The default prefix is ! and is configurable. Free includes Moderation, Welcome, Tickets and basic Logging. Leveling, Reaction Roles and AutoMod require Pro; check Pricing for current limits.

   Sign up, open Create Bot, and follow its Discord Developer Portal setup: create an application, open Bot and copy your bot token using Reset Token → Copy. Keep the token private. Enter your bot name and token in the form, set Command Prefix to ! and select Moderation under Choose Modules.

   In your Discord application’s Bot → Privileged Gateway Intents, enable Server Members Intent and Message Content Intent for Moderation, plus any other switches marked by the form’s checklist. Save Changes, reload to confirm, then return to the form and complete its token check before Create Bot.

4. Invite the bot and check its setup

   Use the created bot’s invite action, choose your test server in Discord and authorize it. The invite action starts hosting; if you already invited it and hosting is stopped, use Start. Wait for it to be online and confirm it is in the intended server.

   Open that bot’s Modules tab and confirm Moderation is enabled. For an existing bot, enable it there and wait for any restart. To change the default prefix later, open Settings → Bot Prefix → Save Prefix. A saved server-specific prefix takes precedence over this default.

5. Test typed commands in a disposable channel

   With ! as the effective prefix, send !lock Prefix command test in the disposable channel. Both the moderator and bot need Manage Channels. Expect a Channel Locked reply and an @everyone Send Messages deny in that channel. Check with an ordinary member; a role or member overwrite can still allow sending.

   Send !unlock in the same channel. Expect Channel Unlocked. This clears the @everyone Send Messages overwrite to inherit; it does not restore a previous custom value. Reapply your recorded permissions if needed. With a different effective prefix, replace ! in both examples.

   If there is no reply, check the online status, effective prefix, enabled module, saved Message Content Intent and channel access. If the command is denied or fails, check the moderator’s and bot’s permissions. Ban commands additionally need Ban Members and suitable role hierarchy; do not ban a real member to test setup.

Compare Build Discord Bots and Dyno