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
I have two bots using the same bot account on Twitch, with different OAuth tokens.
When pinhook sends messages, it does not trigger its own listener, which is good. If the other bot sends a message using the same nick, it causes pinhook to trigger listeners and commands even when pinhook's bot name is added to banned_users:
I can work around this by adding the following code, but it is tedious to do it for every plugin:
ifmsg.nick!="pyllybot":
# plugin code here
Ideally, the bot should always be ignoring its own nick.
Note: pinhook has the command !ping and the other bot has !ding
I've pushed a fix to the twitch_fix branch (which i'm now using as a release branch because I'm lazy). Basically the bot will not process any event if the nick is the same as the self.bot_nick. This might be overkill but that makes some implicit behavior explicit in the code.
I have two bots using the same bot account on Twitch, with different OAuth tokens.
When pinhook sends messages, it does not trigger its own listener, which is good. If the other bot sends a message using the same nick, it causes pinhook to trigger listeners and commands even when pinhook's bot name is added to
banned_users
:I can work around this by adding the following code, but it is tedious to do it for every plugin:
Ideally, the bot should always be ignoring its own nick.
Note: pinhook has the command
!ping
and the other bot has!ding
Here is a log generate for this issue:
The text was updated successfully, but these errors were encountered: