Describe the feature request in as much detail as possible
Hey aaa,
Hope you're doing well!
I Have some suggestions for your cogs as overall, more specifically about the default error message.
Could you please give us (bot-owners) an option to disable or opt-out the huge error message that your cogs throw when the invoker is bot-owner itself!
A toggle switch to disable this would be perfect (I get it if you don't want to disable it completely) as individuals can disable it if they want to.
I'm specifically saying bot-owners as this big error message only shows up when the command invoker is bot-owner.
The truth is - As a bot-owner you already know when a command is errored. Whether via errorlogs which everyone already has setup, or via logs. So bot-owners are already aware of the fact that - what to do when a command is errored. So, for them, there's no point in seeing another big and long text in a convo along with the errorlogs that they have!
Honestly, having these long texts in a chat while in a convo (with one of the users being bot-owner who ran the cmd), doesn't look good atall.
I get the technical appeal here & the info that the error msg is trying to tell but what I'm saying is - I already am aware of the fact that the command got errored and I will be taking the necessary steps to get it fixed.
2nd Part
Not only that,
Even when there is already a customerror setup by the bot-owner (with another cog or the core's set errormsg <msg>) in the machine, your cogs still send the additional error message alongside it. 😶
This is really really odd and pretty much falls into the "annoying" category if you ask me. (As I'm already seeing the exact error message that I need to know via the customerror msg, when I'm in a convo with other users - they don't need to know the additional details of it!!)
3rd Part
Ironically when a normal user invokes an errored command in any of your cogs, It still sends sends an additional error message along with the customerror message that the bot already has.
This extra message is not needed at all.
Possible Soulution
A toggle key to disable the cogs from throwing that error message (Error in [hybrid|text] command...) via your utils (since it already comes installed alongside any of your cogs).
I get you might not want to implement it as it might be useful for you, and I respect that, but at the same time it's horribly aggravating to other bot-owners to use your really useful cogs knowing it will throw that error message along with what they might already have! - So having a toggle switch would help immensely to the community as a whole, I believe.
Or, there can be the option - If there's already a custom errormsg set, whether via set errormsgor via other customerror cogs then your cogs will not show the additional error msg and instead it will log that in the logs so that the bot owner can report it back via sentry if they want to. if not then it will default to what it's been doing atm.
Thanks
I hope you understand the underlying issue that I'm trying to address here and at least give us an option to adjust the settings by ourselves.
What cog is this feature request for?
Applies to all of the cogs and sub-commands.
Describe the feature request in as much detail as possible
Hey aaa, Hope you're doing well!
I Have some suggestions for your cogs as overall, more specifically about the default error message. Could you please give us (bot-owners) an option to disable or opt-out the huge error message that your cogs throw when the invoker is bot-owner itself!
I'm specifically saying bot-owners as this big error message only shows up when the command invoker is bot-owner.
errorlogswhich everyone already has setup, or vialogs. So bot-owners are already aware of the fact that - what to do when a command is errored. So, for them, there's no point in seeing another big and long text in a convo along with theerrorlogsthat they have!2nd Part
Not only that, Even when there is already a customerror setup by the bot-owner (with another cog or the core's
This is really really odd and pretty much falls into the "annoying" category if you ask me. (As I'm already seeing the exact error message that I need to know via the customerror msg, when I'm in a convo with other users - they don't need to know the additional details of it!!)
set errormsg <msg>) in the machine, your cogs still send the additional error message alongside it. 😶3rd Part
Ironically when a normal user invokes an errored command in any of your cogs, It still sends sends an additional error message along with the customerror message that the bot already has.
This extra message is not needed at all.
Possible Soulution
togglekey todisablethe cogs from throwing that error message (Error in [hybrid|text] command...) via your utils (since it already comes installed alongside any of your cogs).set errormsgor via other customerror cogs then your cogs will not show the additional error msg and instead it will log that in the logs so that the bot owner can report it back via sentry if they want to. if not then it will default to what it's been doing atm.Thanks I hope you understand the underlying issue that I'm trying to address here and at least give us an option to adjust the settings by ourselves.