-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Command Handling #28
Comments
I think we just need to expand this function to send a new event (maybe :custom or :unrecognized) or something, that way your handler can accept all unrecognized messages and do whatever you wish with them. Thoughts? |
That'd probably be great! Maybe just pass a :cmd event? |
I wouldn't mind that, something to keep in mind though is that something received by that callback may not actually be a command (it could just be garbage), so we probably want a way to signify that while it's an event that can be handled, you can't necessarily rely on it being a valid message. |
Would it be better to have some list of "CMD" options to handle? ['MODE', 'USERSTATE', 'CAP'] |
I'm working with a IRC that has custom CAP (capabilities), which adds more commands. Is there a good way to handle these messages so they can be handled outside of the ExIrc.Client?
Requesting capabilites:
Example message from the IRC server
https://github.com/justintv/Twitch-API/blob/master/chat/capabilities.md#membership
The text was updated successfully, but these errors were encountered: