Updating Slash Command Workflow

[full hearth]

Hey! I wanted some clarification and advice for dealing with the rates for slash commands when updating them. I wanted to update the options on a particular slash command quite frequently without exceeding the limits. If I were to push them via the method below, would the slash command data already exists (may have updated option count as a new ) add onto any limits.

await rest.put(Routes.applicationGuildCommands("N/A","N/A"),{ body: SLASH_COMMANDS },)

If this is the case then is there any methods to experiment with slash commands more effectively and frequently like a mock slash command framework. Thank you

[raven abyss]

• What's your exact discord.js npm list discord.js and node node -v version?
• Post the full error stack trace, not just the top part!
• Show your code!
• Explain what exactly your issue is.
• Not a discord.js issue? Check out #useful-servers.

[full hearth]

If anyone also has any definitive answers to what procedures occur from discord's side to determine what need to adjusted or created (comparing the JSON, accessing any caches) that'd be great in better understanding the process cause working with slash commands from my POV so far is very inconvenient as a game developer especially when these commands are linked to a game engine which needs constant adjustments in it's options.

[atomic remnant]

Can you help me understand why you need to change the slash command so often?

Or what parts of it are changing?

[full hearth]

These commands are for a game studio I own with my marketing/influencing department giving constant ideas and amendments to certain commands on-top of adjustments when taking into account of thing from the engine side. the options of the commands would be changing not so much the amount of commands.

[atomic remnant]

So is this all happening in dev before it's pushed to production?

[full hearth]

Yes I'm pushing it to the guild commands first before pushing it to global commands. Is there a better method or workflow i could be using?

[atomic remnant]

Nah thats correct, and what I wanted to make sure of

Im not sure I have any specific answers for you though

[stone marlin]

Probably a better design to have a longer period between design/deploy, or have more static commands that can pull data from an external API or such that can return other info that's more readily edited

[full hearth]

Yeah guess I'll have to stick to the longer period between design/deploy for now The fact discord, a company serving billions of messages a month is giving rates, tight rates for in essence manipulating a JSON table on their servers is interesting. Is it possible to update the options of a particular commands and what implications would that have on my limits/quotas.

[stone marlin]

Discord is pretty limiting on stuff like this, it's one reason I stopped working on my bot for the platform

You might wanna check in ddevs or such for more stuff about the API directly, as we're just a wrapper

[full hearth]

Will do, thank you both for the responses

[atomic remnant]

An unfortunate reality of Discord is that despite the size of their company a huge majority of both their users and developers are basically kids, or extremely new amateurs