Why Do My Discord Commands Stop Working After Implementing `on_message()`?

Commands Disabled After Implementation of on_message()

When employing discord.py's on_message() event, users may encounter an issue where their commands stop working. This is due to the overriding nature of on_message(), which disables the execution of commands unless specifically enabled.

Addressing the Issue

To resolve this issue, it is crucial to add a call to bot.process_commands(message) at the end of your on_message() function. This line instructs Discord to process any commands present in the message.

Modified Code

Here is a modified version of your code that incorporates bot.process_commands(message):

import discord
import asyncio
from discord.ext import commands

bot = commands.Bot(command_prefix = '-')

@bot.event
async def on_ready():
    print('Logged in as')
    print(bot.user.name)
    print(bot.user.id)
    print('------')

@bot.event
async def on_message(message):
    if message.content.startswith('-debug'):
        await message.channel.send('d')

    # Process any commands present in the message
    await bot.process_commands(message)

@bot.command(pass_context=True)
async def ping(ctx):
    await ctx.channel.send('Pong!')

@bot.command(pass_context=True)
async def add(ctx, *, arg):
    await ctx.send(arg)

Explanation

The default on_message() event includes a call to bot.process_commands(message) internally. This line enables the execution of commands in the message. By overriding the default on_message(), you effectively block the processing of commands. Adding bot.process_commands(message) manually restores the desired functionality.

Conclusion

By implementing the aforementioned solution, you can ensure that both the debug output in on_message() and your custom commands function correctly.

The above is the detailed content of Why Do My Discord Commands Stop Working After Implementing `on_message()`?. For more information, please follow other related articles on the PHP Chinese website!