Max number of daily application creates ratelimit of 200 should be raised

[Rwarcards762]

NOTE: Most of this issue is likely due to utilizing register_commands vs sync_commands with Pycord in the on_connect override. The rest of the questions are still valid, however.

Issue

Testing a bot as it gets further to complete development, i.e. 30-40 commands maybe, means that you can only restart your bot approximately 6 or so times before you would hit the "200 daily" ratelimit for application command registration.

This occurs even when the commands are just being registered to a single guild. This ratelimit impedes the ability to be able to test, bugfix, and create code for the next 24 hours after hitting it.

Issue Beyond the Ratelimit

The ratelimit itself is a work stoppage. However, after hitting this ratelimit on a restart, all commands from the bot are wiped but then fail to re-register, leaving the bot inoperable for the next 24 hours.

This ratelimit seems to be for a developer themselves, and not for the application itself, as I was unable to register commands on both of my applications after hitting this ratelimit.

Solution

Raise ratelimit for application creates per day, at least for guild-only creates (since that's where testing should be done and the ratelimit should be higher.)

Current Workaround

Unload everything except what is being worked on at the time to avoid the ratelimit -- although if you dedicate a day to working on a bot, you very well could still hit it and be left stuck, unable to work any more for 24 hours.

More Information

• Using pycord API wrapper.
• Specific error is discord.errors.HTTPException: 400 Bad Request (error code: 30034): Max number of daily application command creates has been reached (200)

---

Discussion

I'm making this discussion because it has now been at least 20 hours since I hit the ratelimit and still cannot register any commands on any bots. I was planning to work on my bot today and was unable to test anything.

• I'm curious to see if other developers have been put at a work stoppage due to this.
• I also would love to know more about this ratelimit and why it exists in the first place for guild-only commands (or why the limit is SO low!)
• Why does this ratelimit apply to all applications owned by a developer?
• Could this ratelimit be adjusted to be a global-registration ratelimit instead of for all registrations?

[devsnek]

this only applies to new commands. PUTing existing commands does not count towards this limit.

[Rwarcards762]

This may be an issue with the way Pycord registers commands then -- I just restart my bot once I make a change, test it, make adjustments, and restart.

Update: Was utilizing register_commands instead of sync_commands which was likely re-registering commands on boot. Still odd that it would unregister and re-register a command that already exists, though.

[advaith1]

the rate limit only applies to creating new commands; this should not be an issue unless you are doing something you shouldn't, such as constantly deleting and re-creating many commands.

[Rwarcards762]

I agree -- which is why this is odd. I'm not doing anything that should be deleting and re-generating commands. My bot has maybe 30 commands total. Only things that I do are make adjustments to the existing functions and reboot the bot.

Update: Was utilizing register_commands instead of sync_commands which was likely re-registering commands on boot. Still odd that it would unregister and re-register a command that already exists, though.

[Rwarcards762]

I believe this may have been due to a register_commands vs sync_commands -- I'll have to confirm that later (still cannot register anything), but this may be a non-issue.

I'm still curious about the rest of the issue though -- is this ratelimit a 24 hour ban on registering commands? Is it per developer? etc

I'm also still curious -- why is the ratelimit 200, even for guild commands? Is it that taxing to register a command with Discord's API?

[nmsturcke]

I'd say reaching 200 registered commands per guild in a day is quite unlikely to happen.

In your case, the library you were using was re-registering every time the bot came online, but that is not the intended way of using application commands.

[Rwarcards762]

I see -- so this is a per guild ratelimit.

And yes -- I did determine something that was incorrect in registering vs syncing commands and have now solved that issue.

[onerandomusername]

Is the ratelimit a 24 hour ban from making ANY registrations on ANY bot you own? Is there a reason this ratelimit applies to the developer and not the application itself?

No. This applies to just the application itself, and not all of your apps. I just tested with a bot account, of which I made and deleted 200 guild commands, which exhausted all creates for that guild for the day, for that application.

Testing the same code on a different bot token successfully made a guild command in the same guild as above.

[Rwarcards762]

Testing the same code on a different bot token successfully made a guild command in the same guild as above.

That's odd. I tried this exactly -- I tried running the bot with an alternate bot token / application (all of my commands specify a guild ID to register to for now) -- and it would not register any commands still.

I thought it was application-specific, but the behavior I experienced showed otherwise. May have been some other factor involved, I guess.

[Rwarcards762]

Update -- found why the other bot was unable to register any. Now I'm having a separate issue, but it's unrelated to this thread -- thanks for the answers, everyone.