Discord bot slash commands not showing/recognized about windowsgsm HOT 10 OPEN

I have the same issue with the build in discord bot. No error, nothing. Please advise!

Try: If the bot is not responding to commands, acitvate: ► Privileged Gateway Intents -> All 3 options. (Discord Developer Portal). Also make sure you have add your user ID (Right click on your discord name and copy the ID) to the WindowsGSM and not your username#0000.

After that the bot should response. But Slash commands are not working.

Hopefully it helps.

from windowsgsm.

I have the same problem. Can't get this feature to work
@EpsilonCommunity We are talking about the discord bot inside WGSM

from windowsgsm.

Privileged Gateway Intents And select all 3 options,

Thanks for getting me in the right direction. The only thing needed to be changed from default was:

from windowsgsm.

The wgsm commands are not for this WINDOWSGSM. They're webhooks.

You're looking for: https://github.com/DiscordGSM/GameServerMonitor

from windowsgsm.

I have the same issue with the build in discord bot. No error, nothing. Please advise!

from windowsgsm.

Same problem her, Bot created in the discord developer portal, with all intents and as administrator. Copied token to WindowsGSM ad the admin-id with user xxxx#xxxx. Enable and Autostart in WindowsGSM. Created a Test Server in Discord, and invited the bot with the wizard from the developer portal. But it is not working with wgsm. Is there an ACTUAL Manual out there or is this a bug?

from windowsgsm.

I got this working, Here is how: On your "invite link" it will show this
https://discord.com/oauth2/authorize?client_id=9999&permissions=67497024&scope=bot

Change Permissions=8 This will give the bot Admin permissions upon entry of the server.
On Bot Application "discord" Go to > Privileged Gateway Intents And select all 3 options,

Restart bot and try the commands

from windowsgsm.

Privileged Gateway Intents And select all 3 options,

Thanks for getting me in the right direction. The only thing needed to be changed from default was:

This is the way!

To add the bot as admin is a bit of a security risk, or any other bot for that matter. From what I understand, you should only add bots as admin that need to administrate your server. No more, no less.

There are a few people in the WindowsGSM discord having issues as well. I wonder if there's an API outage in some areas, possibly?

Anyway, kudos to @FriedCheese2006 for fixing it himself.

LONG IMAGE WARNING (Role configuration for Discord bot)!!!

I'd recommend using that method and/or giving the bot a role on your server with the following permissions:

All the best,
//TheModdersDen

from windowsgsm.

The bots permissions are set by the invite link and reconfirmed when you invite it to the server. The real missing piece was the API change they made a while back (been a while since I set a bot up) that prevented bots from being able to read regular messages by default (if I recall, they were trying to phase this out in favor of slash commands unless needed to bot functionality). What's weird is I remember them saying it would only be enforced for bots that are in a large number of servers. It looks like this is now required period and just gets the additional review by Discord if in a large number of servers.

So, you just need to create bot (Discord Dev), make sure you add the "Message Content Intent", generate and copy the token into WindowsGSM, click the invite button to invite the bot to the server, and give it the requested permissions. Add your admin IDs and server info in WindowsGSM and you should be good to go.

from windowsgsm.

The bots permissions are set by the invite link and reconfirmed when you invite it to the server. The real missing piece was the API change they made a while back (been a while since I set a bot up) that prevented bots from being able to read regular messages by default (if I recall, they were trying to phase this out in favor of slash commands unless needed to bot functionality). What's weird is I remember them saying it would only be enforced for bots that are in a large number of servers. It looks like this is now required period and just gets the additional review by Discord if in a large number of servers.

So, you just need to create bot (Discord Dev), make sure you add the "Message Content Intent", generate and copy the token into WindowsGSM, click the invite button to invite the bot to the server, and give it the requested permissions. Add your admin IDs and server info in WindowsGSM and you should be good to go.

Fair enough. I was just sharing what I know worked for me. 😉

from windowsgsm.