Function to grab all registered global slash commands

[JDJGInc]

I think it should be possible to grab all the slash commands located in guilds(for your bot), in one api request, so on libraries like discord.py, or discord.js you don't need to readd the command every time the bot starts up, instead you would be able to add it temporarily in your cache, so the commands, get added if they haven't been. Basically it just makes it easier to see what slash commands you registered in guilds, and it doesn't take a ton of api requests, if this can't be added, then why not?

(yes I am aware that slash commands can be grabbed but only the global ones.)

[Longhouse81]

I don't know how DiscordPY works but for DiscordJS you can easily fetch all commands for a guild when you don't specify a command id.
https://discord.js.org/#/docs/main/stable/class/ApplicationCommandManager?scrollTo=fetch
And Discord developers documentation:
https://discord.com/developers/docs/interactions/application-commands#get-guild-application-commands

Also to come to the topic of guild commands you shouldn't read them on startup but store them upon creation, they only change when you alter them, they are still registered when your bot is offline.
The only way the guild commands get deleted is when the bot leaves a guild or you bulk set commands with an empty request...

So practical use:

• create/alter command => store the commands data in your bot
• when your bot leaves a guild (or get kicked) you remove the save in your bot settings
• when rejoining a guild you create the guild commands again based on the previous guild settings => store the commands data in your bot again

[Longhouse81]

Huh... ok...
Creating/Updating Slash commands is done by sending in JSON format...
So if you want to update commands a simple JSON file would do it without requiring your bot to have some downtime...
Easy way:

• Bulk Update with an empty JSON API query, your commands will all be gone.
• Read your updated JSON file and bulk set slash commands with the content of the JSON file...
• Read all application command ID on Create or Update and store them in your bot memory (DB/Save File)
  Advanced way:
• Read your updated JSON file, compare all the commands with the ones in the memory (DB/Save File) of your bot.
• For the ones that differ from the JSON file you check the stored ID in memory (DB/Save File) of your bot, adjust your commands by ID (Delete, Update, Create) and store them again in your memory (DB/Save File) with the updated version.

Depending on the situation and changes the easy way may be preferred over the advanced way, for guild application commands you can only update 200 times a day, making it on large changes bulk is preferred over individual application command updates because of the limits.
Also, note you should try to keep your bot online at all costs, changes like this shouldn't affect your bot uptime in any way, they require simple solutions, you can easily code in your bot to accept commands from you only or some command-line command, website and so on... to update stuff like that...

[ckohen]

There's no need to bulk update with an empty query if you're just going to bulk update again with new ones, that's the whole point of bulk update, its an upsert.

For the "advanced" way, I'm again not sure why you're stuck in the delete-create loop. In fact that method would not work at all as described (delete then update would error on the update)

[JDJGInc]

I don't know how DiscordPY works but for DiscordJS you can easily fetch all commands for a guild when you don't specify a command id. https://discord.js.org/#/docs/main/stable/class/ApplicationCommandManager?scrollTo=fetch And Discord developers documentation: https://discord.com/developers/docs/interactions/application-commands#get-guild-application-commands

Also to come to the topic of guild commands you shouldn't read them on startup but store them upon creation, they only change when you alter them, they are still registered when your bot is offline. The only way the guild commands get deleted is when the bot leaves a guild or you bulk set commands with an empty request...

So practical use:

• create/alter command => store the commands data in your bot
• when your bot leaves a guild (or get kicked) you remove the save in your bot settings
• when rejoining a guild you create the guild commands again based on the previous guild settings => store the commands data in your bot again

My problem with this, it's not one quick grab request, which is my library would want to do, they don't want to fetch every slash commands for every guild that would be very api heavy, and they don't really want to store local commands locally, and how it works makes it impossible to essentially do this:

1. keep Database of every slash command and what guilds it is in so...
2. Database shouldn't be needed anyway.

[Longhouse81]

There's no need to bulk update with an empty query if you're just going to bulk update again with new ones, that's the whole point of bulk update, its an upsert.

For the "advanced" way, I'm again not sure why you're stuck in the delete-create loop. In fact that method would not work at all as described (delete then update would error on the update)

The update with the empty JSON was more intended for explaining how to remove them all...
That's why i wrote it in 2 separate lines, of course, you don't remove them but you just bulk set them instead of removing them first.

[Longhouse81]

My problem with this, it's not one quick grab request, which is my library would want to do, they don't want to fetch every slash commands for every guild that would be very api heavy, and they don't really want to store local commands locally, and how it works makes it impossible to essentially do this:

1. keep Database of every slash command and what guilds it is in so...
2. Database shouldn't be needed anyway.

Now i gave you the link on how to read all commands per guild, your original question... A link to the Discord API guide and DiscordJS documentation on how to do this.
Now you mention API spam, you are spamming the API if you don't save local what you create and on startup demand all guilds their commands, if you don't want to use a database that's not the issue, but your bot is never going to magically fill it's cache what guild commands are registered without a DB, local save file or API requests. You don't want to use a DB, then use a local save file like i also stated...

[CanIGetaPR]

would be very api heavy

Well apparently it's not that API heavy because Discord itself sends a separate Guild_create event for every guild as it becomes "available" while you're booting up your bot, so it's okay to request per guild, you should do it in the guild_create event on your bot startup.
https://discord.com/developers/docs/topics/gateway#guild-create

In addition to creating missing commands I suggest you also implement an equals method for commands to compare if your local copy is identical to the uploaded copy, if not do an update.