Skip to content

jsircbot failed to manage nick collisions #2

Description

@GoogleCodeExporter
default.jsmod has a listener for nick collisions. I ran into a problem with
this.
Another user on a channel where jsircbot was listening logged on twice and
thus caused nick collisions.
This triggered the jsircbot code, and as a result "_mod.data.nick" was
changed internally.
I have my own jsircbot module which at some point calls the following method:

_mod.Send( 'NICK ' + getData(_mod.data.nick)

It does this in order to get back the original nick that it was configured
to run under as specified in configuration.js.
However, due to the listener in default.jsmod this now has the value of
whatever other user last ran into a nick collision.

Original issue reported on code.google.com by sou...@gmail.com on 19 Oct 2007 at 6:16

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions