Сommands in chat via a prefix do not work

[makarasty]

To hide some errors, you can use the argument --trace-warning or --trace-warnings, but it does not solve the problem, the bot does not read the command files, so it does not respond to commands.

edited: splash commands work fine

strange but if you print out the client.commands, all the commands are there

[Simpleboy353]

Make sure you have the latest version of this bot (v14) and also make sure that the MESSAGE_CONTENT intent is enabled in developer portal (this is happened with me too when I was testing the update) and also thanx for the embed error report.

[makarasty]

Make sure you have the latest version of this bot (v14) and also make sure that the MESSAGE_CONTENT intent is enabled in developer portal (this is happened with me too when I was testing the update) and also thanx for the embed error report.

I have the latest version of discord.js installed

[Simpleboy353]

These packages will be removed in the coming updates. Have you checked the message intent?

[makarasty]

I just used the help command, Yes, it's on.

my opinion the error is that the bot can not find the command.enabled because it is undefined, as a solution you can try to set a value

[Simpleboy353]

Just check the intents bit value. It should same as in the ss. If it still doesn't work, instead of adding values in each command, just make it to check if command.enabled is undefined or not. Like:

if (command.enabled !== undefined || command.enabled !== "") { 
    // code
}

This is easier than adding value to each command imo.

[makarasty]

It's strange...

[Simpleboy353]

Try using the bot my mentioning the bot instead of using the prefix. Like @Bothelp. That will make sure whether the bot can access the message content or not

[makarasty]

it works! Is this prefix bad?

[Simpleboy353]

So yes, its an issue with the message content. You bot is not able to access the message content. Can you show the intents bit number from the index.js file?

[makarasty]

I didn't change anything. const client = new Client({ allowedMentions: { parse: ["users", "roles"] }, intents: 47007 });

[Simpleboy353]

i think the message content intent is not enabled

[Simpleboy353]

thats all I can think of

[makarasty]

thats all I can think of

But

[Simpleboy353]

thats strange... it should work fine...

[makarasty]

Another bot on discord 12 works

[makarasty]

I'm waiting for a fix, but I don't understand what the problem is.

[Simpleboy353]

find the intent bit value that suits your bot: https://discord-intents-calculator.vercel.app/

[makarasty]

find the intent bit value that suits your bot: https://discord-intents-calculator.vercel.app/

I changed this value to 3276799, it did nothing

[Simpleboy353]

last thing i can say... try using a different bot

[makarasty]

The other bot works

[Simpleboy353]

i guess the previous bot didn't like the code....

[makarasty]

i guess the previous bot didn't like the code....

I'm interested in your bot, it's great

[Simpleboy353]

dont know what is wrong..... why it isnt working.....

[makarasty]

dont know what is wrong..... why it isnt working.....

I must be cursed, not a single bot I tried to use does not work properly 😞

[Simpleboy353]

try using the code on a different bot ( a different bot on developer portal) .. and enable the intents (all of them) and try using the code with that.. that might work

[makarasty]

try using the code on a different bot ( a different bot on developer portal) .. and enable the intents (all of them) and try using the code with that.. that might work

I tried changing the bot's token to a different one, but it did nothing.

[Simpleboy353]

okay, lets try this: use the intent flags instead of bit value...

const client = new Client({
  allowedMentions: { parse: ["users", "roles"] },
  intents: [
    GatewayIntentBits.Guilds,
    GatewayIntentBits.GuildMessages,
    GatewayIntentBits.GuildBans,
    GatewayIntentBits.GuildsVoiceStates,
    GatewayIntentBits.GuildMembers,
    GatewayIntentBits.GuildPresences,
    GatewayIntentBits.MessageContent,
    GatewayIntentBits.GuildWebhooks,
    GatewayIntentBits.GuildMessageReactions
  ]
});

[makarasty]

okay, lets try this: use the intent flags instead of bit value...

const client = new Client({
  allowedMentions: { parse: ["users", "roles"] },
  intents: 47007
});

It didn't give any results, I think we're looking in the wrong place

[Simpleboy353]

okay, lets try this: use the intent flags instead of bit value...

const client = new Client({
  allowedMentions: { parse: ["users", "roles"] },
  intents: 47007
});

It didn't give any results, I think we're looking in the wrong place

just updated the message

[makarasty]

I changed GatewayIntentBits.GuildsVoiceStates, to GatewayIntentBits.GuildVoiceStates Because it didn't work

but the error is the same

[makarasty]

The bot sees the messages

[Simpleboy353]

bruh.. change the prefix to ! or any else

[makarasty]

maybe the problem is in these lines because they cannot measure the command.enabled

[makarasty]

😲😲😲😲😲😲😲😲😲😲😲😲😲😲😲

[Simpleboy353]

lol... im dumb af... im done

[makarasty]

it seems that the bot just does not know how to work with other prefixes

[Simpleboy353]

i dont think so

[makarasty]

But the other prefixes don't work for me

[Simpleboy353]

please edit the command.js file... refer to this... this should fix the prefix issue

[makarasty]

IT WORKS 😳

[makarasty]

Thanks dude, you're the best.

[Simpleboy353]

Thanks dude, you're the best.

np broo... enjoy your bot :heart:

[Simpleboy353]

also i forgot to mention, activity commands arent working for now as the package hasnt been update to use djs v14. I'll wait a week or two, if gets the update, its fine else i'll update the code...