I am an amateur who runs an mIRC chat bot for a small stream and am trying to update it to use IRCv3 tags in preparation for the deprecation of the TWITCHCLIENT command. I’m having trouble capturing messages sent to the console. When I attempt to capture the raw event (http://en.wikichip.org/wiki/mirc/raw_events), I don’t receive any of the IRCv3 meta tags.
Yes, I have sent CAP REQ :twitch.tv/tags which is why I even see the meta tags at all in my console/status window. I am just having trouble capturing and parsing them.
Please note, that using IRCv3 with mIRC in the above manner bypasses alot of internal functionality of mIRC (such as on text events not firing). There is a feature suggestion to fix this within mIRC that can be found HERE if you’d like to show your support
Yes, parsecommand is an alias in my script specific to my bot. The general idea is that’s the point in the code that will direct to the sub that will decipher all the commands the bot receives. Posting my code here would be a little overwhelming as there are lots of pieces that depend on others and 5 different pathways for commands to get parsed. I’m also changing things constantly…today for instance, I added whisper capability to my bot.
In the newest mirc which is still in beta, there is a $msgtags identifier which returns color=#1E90FF;display-name=Lilqx;emotes=46354:7-17;subscriber=0;turbo=0;user-type=
To check if someone is a subscriber you can do:
if subscriber=1 isin $msgtags {
…insert code here…
}
to check if the user was a mod you can do
if user-type=mod isin $msgtags {
…insert code here etc…
}
The messages display in channel properly, and all the capability requests work fine.
Please note that it is a closed beta, and not available for download as of yet. There are still features to be added and bugs to be fixed before the beta will be made public