You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if you return an error from a command, the bot prints the following message:
An error has occurred.
At `2016-05-12T20:36:16Z`, @vanstee initiated the following pipeline, assigned the unique ID `ec536613be7840189c133a932f10eaeb`:
` help wut`
The pipeline failed planning the invocation:
`operable:help wut`
The specific error was:
Whoops! An error occurred. Command "wut" does not exist
That's great for when a command unexpectedly crashes, but if you mistyped something it would be nice for the bot to just say:
help: ERROR: Command "wut" does not exist
The text was updated successfully, but these errors were encountered:
Add a new response status called "abort". Add support to Relay, pycog3, and cog-rb to allow commands to signal when they wish to abort by writing COGCMD_ACTION: abort\n to stdout. When Cog receives this status it will render the body (with template if the command has specified one) and then terminate the pipeline. A "pipeline aborted" audit message will be written as well.
Right now if you return an error from a command, the bot prints the following message:
That's great for when a command unexpectedly crashes, but if you mistyped something it would be nice for the bot to just say:
The text was updated successfully, but these errors were encountered: