discord.ext.bridge – A module that bridges slash commands to prefixed commands

New in version 2.0.

This module allows using one command callback in order to make both a prefix command and a slash command. This page includes the API reference/documentation for the module, but only contains a short example. For a more detailed guide on how to use this, see our discord.ext.bridge guide.

Note

ext.bridge requires the message content intent to be enabled, as it uses the ext.commands extension.

Example usage:

import discord
from discord.ext import bridge

intents = discord.Intents.default()
intents.message_content = True

bot = bridge.Bot(command_prefix="!", intents=intents)

@bot.bridge_command()
async def hello(ctx):
    await ctx.respond("Hello!")

@bot.bridge_command()
async def bye(ctx):
    await ctx.respond("Bye!")

@bot.bridge_command()
async def sum(ctx, first: int, second: int):
    s = first + second
    await ctx.respond(f"{s}")

bot.run("TOKEN")

API Reference

Bots

Methods
class discord.ext.bridge.Bot(command_prefix=<function when_mentioned>, help_command=<default-help-command>, **options)

Represents a discord bot, with support for cross-compatibility between command types.

This class is a subclass of ext.commands.Bot and as a result anything that you can do with a ext.commands.Bot you can do with this bot.

New in version 2.0.

add_bridge_command()

Takes a BridgeCommand and adds both a slash and traditional (prefix-based) version of the command to the bot.

@bridge_command

A shortcut decorator that invokes bridge_command() and adds it to the internal command list via add_bridge_command().

Returns:

A decorator that converts the provided method into an BridgeCommand, adds both a slash and traditional (prefix-based) version of the command to the bot, and returns the BridgeCommand.

Return type:

Callable[…, BridgeCommand]

class discord.ext.bridge.AutoShardedBot(command_prefix=<function when_mentioned>, help_command=<default-help-command>, **options)

This is similar to Bot except that it is inherited from ext.commands.AutoShardedBot instead.

New in version 2.0.

Bot.add_bridge_command()

Takes a BridgeCommand and adds both a slash and traditional (prefix-based) version of the command to the bot.

@Bot.bridge_command

A shortcut decorator that invokes bridge_command() and adds it to the internal command list via add_bridge_command().

Returns:

A decorator that converts the provided method into an BridgeCommand, adds both a slash and traditional (prefix-based) version of the command to the bot, and returns the BridgeCommand.

Return type:

Callable[…, BridgeCommand]

Commands

Methods
class discord.ext.bridge.BridgeCommand(callback, **kwargs)
get_ext_command()

A method to get the ext.commands version of this command.

Returns:

The respective traditional (prefix-based) version of the command.

Return type:

BridgeExtCommand

get_application_command()

A method to get the discord.commands version of this command.

Returns:

The respective slash command version of the command.

Return type:

BridgeSlashCommand

add_to(bot)

Adds the command to a bot.

Parameters:

bot (Union[ExtBot, ExtAutoShardedBot]) – The bot to add the command to.

@bridge.bridge_command

A decorator that is used to wrap a function as a command.

Parameters:

kwargs (Optional[Dict[str, Any]]) – Keyword arguments that are directly passed to the respective command constructors.

class discord.ext.bridge.BridgeExtCommand(*args, **kwargs)

A subclass of ext.commands.Command that is used to implement bridge commands.

class discord.ext.bridge.BridgeSlashCommand(*args, **kwargs)

A subclass of SlashCommand that is used to implement bridge commands.

Context

Methods
class discord.ext.bridge.BridgeContext

The base context class for compatibility commands. This class is an ABC (abstract base class), which is subclassed by BridgeExtContext and BridgeApplicationContext. The methods in this class are meant to give parity between the two contexts, while still allowing for all of their functionality.

When this is passed to a command, it will either be passed as BridgeExtContext, or BridgeApplicationContext. Since they are two separate classes, it is quite simple to use isinstance() to make different functionality for each context. For example, if you want to respond to a command with the command type that it was invoked with, you can do the following:

@bot.bridge_command()
async def example(ctx: BridgeContext):
    if isinstance(ctx, BridgeExtContext):
        command_type = "Traditional (prefix-based) command"
    elif isinstance(ctx, BridgeApplicationContext):
        command_type = "Application command"
    await ctx.send(f"This command was invoked with a(n) {command_type}.")

New in version 2.0.

await respond(*args, **kwargs)

This function is a coroutine.

Responds to the command with the respective response type to the current context. In BridgeExtContext, this will be reply() while in BridgeApplicationContext, this will be respond().

await reply(*args, **kwargs)

This function is a coroutine.

Alias for respond().

await defer(*args, **kwargs)

This function is a coroutine.

Defers the command with the respective approach to the current context. In BridgeExtContext, this will be trigger_typing() while in BridgeApplicationContext, this will be defer().

Note

There is no trigger_typing alias for this method. trigger_typing will always provide the same functionality across contexts.

await edit(*args, **kwargs)

This function is a coroutine.

Edits the original response message with the respective approach to the current context. In BridgeExtContext, this will have a custom approach where respond() caches the message to be edited here. In BridgeApplicationContext, this will be edit().

class discord.ext.bridge.BridgeApplicationContext(bot, interaction)

The application context class for compatibility commands. This class is a subclass of BridgeContext and ApplicationContext. This class is meant to be used with BridgeCommand.

New in version 2.0.

Methods
class discord.ext.bridge.BridgeExtContext(*args, **kwargs)

The ext.commands context class for compatibility commands. This class is a subclass of BridgeContext and Context. This class is meant to be used with BridgeCommand.

New in version 2.0.

await delete(*, delay=None, reason=None)

This function is a coroutine.

Deletes the original response message, if it exists.

Parameters:

  • delay (Optional[float]) – If provided, the number of seconds to wait before deleting the message.

  • reason (Optional[str]) – The reason for deleting the message. Shows up on the audit log.