Freenode no longer works with nickchange after ghosting?
Closed this issue · 3 comments
[17:30:44] NickServ [NickServ@services.]: OmegaPhil has been ghosted.
[17:32:02] NickServ [NickServ@services.]: Invalid command. Use /msg NickServ help for a command listing.
[17:32:08] NickServ [NickServ@services.]: You are not logged in.
Seems that Freenode is using a different IRC event to signal 'Cannot change nickname while banned or moderated on channel' as well...
Along with dealing with the invalid numeric renumber, it seems for Freenode that the script cannot cope with an 'banned from channel preventing nick change' event - it just tries to release the nick. I have commented out this Freenode logic and let the script behave as normal, and now it can ghost, change nick and rejoin all channels properly.
Will wait a week but will probably end up disabling the enforce/release code until this Freenode-specific stuff actually happens again.
Along with dealing with the invalid numeric renumber, it seems for Freenode that the script cannot cope with an 'banned from channel preventing nick change' event - it just tries to release the nick. I have commented out this Freenode logic and let the script behave as normal, and now it can ghost, change nick and rejoin all channels properly.
Will wait a week but will probably end up disabling the enforce/release code until this Freenode-specific stuff actually happens again.