Solution that allows increasing the subcommand limit #5218
Unanswered
BowkC
asked this question in
API Feature Requests & Ideas
Replies: 1 comment 1 reply
-
What is the need for a >>> 100 * 25 * 25
62500
This is not a limit from what I understand. What you are saying is "calculate a limit based on how many they use", so a bot can just post more every day to get the maximum limit? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why should the subcommand limit change?
Many developers have more than 100 commands and thus they will be forced to use subcommands to accommodate for those extra commands. But you can only have 25 subcommands per command and this forces developers to resort to stuff like this:
/image1 avatar
/image2 invert etc
How on earth is the user supposed to know what category it falls under or how to run the command they want?? It is incoherent and sloppy no matter what
The solution
Why not make it so developers can choose their own limit say 10, 25, 50 and 100. Then for each limit they pick, the number of subcommands per command increases. So if I picked my slash command limit at 50, each command could have 50 sub commands. So with this method the theoretical number of slash commands a bot can have never increases but the amount of subcommands can still increase to suit users with large categories - which is extremely useful when applied properly.
This could also be implemented other ways, the user could specify their own limit on slash commands from 1-100 and this would determime the number of subcommands they are permitted to use. Or it could just be a simple select box scenario with 100, 50, 25 and 10 for example.
This method means that the maximum number of requests and theoretical slash commands does not change and that - I think - is key. As far as I know, the implementation of this feature would be a win win for both discord and developers and I see it as mutually beneficial.
I have attached below some examples
Beta Was this translation helpful? Give feedback.
All reactions