#Only the slash command part of bridge commands works.

1 messages · Page 1 of 1 (latest)

burnt locust
#

As in title, only the slash commands work, the traditional/prefixed ones do not.
Here's my code in case you need to look at it

import discord
from discord.ext import bridge 
import dotenv
import os
dotenv.load_dotenv()
token = str(os.getenv("TOKEN"))

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

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

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

bot.run(token) 
stuck palm
#

did you also enable message intents in the developer portal?

#

and you should use discord.Intents.default()
not sure if it does that if you instantiate it that way too but just to be sure

burnt locust
burnt locust
stuck palm
#

but definitely enable message content afterwards manually

crisp vine
#

Pretty sure everything is disabled when you init it like that

#

since no value was passed

#

You should only enable the intents your bot requires

#

.Intents(messages=True, guilds=True, message_content=True) for example.

There are like 26, and they correspond to incoming events and cache, so you may save some RAM and bandwidth by disabling the ones you don't need.

stuck palm
#

default is fine and you should use it unless your bot is in a huge number of servers and you can't handle the number of events

crisp vine
#

Meh

#

Do you really events like on_typing

stuck palm
#

receiving a few extra events vs needing to needlessly debug very obscure errors or null values when you have no clue it could be intents anymore

#

there's a reason all those intents are default

burnt locust
crisp vine
#

still not a reason to just blindly get all

crisp vine
burnt locust
#

llllloooo'-87777777777777777777777777777777777777 9 =-l.[=xrk-=[s>l.\

#

ooops

#

keyboard acting up

burnt locust
stuck palm
burnt locust
#

anywho