As the bot is hosted on a persistent server, and for Twitch streams, certain messages may need to be forwarded to the streamer, it would make sense to allow messages to be sent to an exposed message queue that can be subscribed to one way or another.
This might not be a separate handler, instead, it may be a feature of any particular handler; for example:
The streamer runs a local client while they are streaming that subscribes to a message broker. The client handles various messages in different formats
The bot receives a !bang command
The bot forwards a message to the message broker
The message broker publishes the message, which is made available to all subscribers (i.e. the twitch streamer)
An action subsequently happens on stream; an image changes, a sound or animation plays, VSCode theme changes etc. This depending on the message received and the implementation.
It may be suitable to make the local client scriptable - i.e. allow the streamer to control what actions take place when a command is received. This might take some work, though.
This would be specifically for Twitch.
As the bot is hosted on a persistent server, and for Twitch streams, certain messages may need to be forwarded to the streamer, it would make sense to allow messages to be sent to an exposed message queue that can be subscribed to one way or another.
This might not be a separate handler, instead, it may be a feature of any particular handler; for example:
It may be suitable to make the local client scriptable - i.e. allow the streamer to control what actions take place when a command is received. This might take some work, though.