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
We have found that sometimes, when the bot is cycled, it reconnects to the room before its old nick is released, and therefore reconnects with a different, deduplicated nick. E.g., instead of connecting with my_robot, it uses my_robot1, which is automatically generated by the irc server.
When that happens the robot will not respond to its new nick, e.g., my_robot1, but only the nick it was expecting, e.g., my_robot. This makes it difficult and confusing for users to interact with.
This seems like something that would need to be dealt with via the irc adapter, hence I am opening this issue.
The text was updated successfully, but these errors were encountered:
It looks like we could use bot.nick after connecting to set the robot name. Something like:
@robot.name=options.nickbot=newIrc.Clientoptions.server, options.nick, client_options
bot.addListener'registered', (message) -># The 'registered' event is fired when you are connected to the server@robot.name=bot.nickifoptions.connectCommand?strings=options.connectCommand.split""self.commandstrings.shift(), strings...
We have found that sometimes, when the bot is cycled, it reconnects to the room before its old nick is released, and therefore reconnects with a different, deduplicated nick. E.g., instead of connecting with
my_robot
, it usesmy_robot1
, which is automatically generated by the irc server.When that happens the robot will not respond to its new nick, e.g.,
my_robot1
, but only the nick it was expecting, e.g.,my_robot
. This makes it difficult and confusing for users to interact with.This seems like something that would need to be dealt with via the irc adapter, hence I am opening this issue.
The text was updated successfully, but these errors were encountered: