I'm having this issue with my bot never able to retrieve their nick back. The nick/altnick are set and it will always retain the altnick instead of switching back the the original nick. The keep-nick setting is set and this is occurring on efnet.
The logs are filled with the following message
Switching back to nick bot1
NICK IS INVALID: 'bot1' (keeping 'bot2').
The only way to regain the original bot nick of bot1 is to force the bot to reconnect to the server.
Here's a couple things to play with. Just trying to gather more info about what is really happening.
In partyline, do: .console +r
This will switch on raw logging for you (owner) in the partyline. This must first be enabled in eggdrop.conf though (for owner).
Now, you can see everything that is going on. It's a mess, but handy for times like this.
Try: .dump nick SomeNickHere
and bot should change its nick accordingly.
( You can play with: .set nick and .set botnick , too . Just to see what is config'd in bot )
You'll have to catch the timing just right, when it is trying to switch on its own from bot2 to bot1, and now you can fully see what is coming back from the server. My hope is that there is more to it, than just "NICK IS INVALID" . Maybe there will be more of a clue for us.
And when you no longer want/need to see everything, don't forget to switch raw logging back off, with: .console -r
For a fun (and popular) Trivia game, visit us at: irc.librairc.net #science-fiction . Over 300K Q & A to play in BogusTrivia !
I did try messing around with the .dump nick and the suggested .set nick and .set botnick before I manually made the bot switch servers to actually regain the proper nick. I was still stuck with my altnick while the configured nick would not change even though the configured nick was not in use on the network.
I wasn't aware of the console +r setting to figure out what is happening in more detail. I set raw-log 1 in eggdrop.conf and enabled raw logging in the partyline with .console +r.
The timing is the most annoying part as I usually catch it past the moment it is happening. Now it's time to wait until it happens.
I managed to capture something that is filling the logs...
[@] :irc.mzima.net 432 nick814 nick900 :Erroneous Nickname
[2024-11-08 00:00:45] NICK IS INVALID: 'nick900' (keeping 'nick814').
The nick it is trying to change to is available but it refuses to switch to it. Once I jump servers there is no issue taking the nick.
A '.dump nick' also refuses to change the nick.
A 432 error appears to be this
432
ERR_ERRONEUSNICKNAME
RFC1459 <nick> :<reason>
Returned after receiving a NICK message which contains a nickname which is considered invalid, such as it's reserved ('anonymous') or contains characters considered invalid for nicknames. This numeric is misspelt, but remains with this name for historical reasons