Description
Currently we have the messages feature which just includes a message for unknownCommand. JellyCommands sends this message when the command it receives isn't known. This is a reasonable assumption, since JellyCommands requires to be the sole command registrar. However, it's still weird because if that assumption is right then it shouldn't ever happen right? The times I've come into it is partially due to development quirks and partly due to #216 (us matching by id, rather than name).
Currently my ideas around this are:
- Remove messages and happily ignore any command interactions we don't handle. We should also warn in console if this happens.
- Provide a "catchall" hook that you can modify to customise the behaviour when this happens. The default hook would replicate the current behaviour, minus an option to configure the "messages"
Similarly we need to decide what happens to other interactions that suffer this problem, and whether it exists. I can imagine there being situations where you have a button/modal/etc request that comes in we can't handle. Now whether that's because of a typo, or you receive interactions from other bots (I don't believe so), not sure. Needs investigating