Bot A is set to +bitch. A user gets opped by another known bot B but is not in bot A's userlist. No problem for bot A as bot B is allowed to op users. Now, when this user changes his nick, he gets deopped. I've seen this on twe different eggies.
Is this a known issue and has anyone seen it as well?
On 2002-03-13 16:11, Bever wrote:
I've seen this behavior on 1.6.x.
Bot A is set to +bitch. A user gets opped by another known bot B but is not in bot A's userlist. No problem for bot A as bot B is allowed to op users. Now, when this user changes his nick, he gets deopped. I've seen this on twe different eggies.
Is this a known issue and has anyone seen it as well?
"Bot A is set to +bitch (...) bot B but is not in bot A's userlist."
He IS in Bot A's userlist. That's why I said: no problem for bot A, as bot B is allowed to op users. They are even linked to eachother, but do not share userfiles.
Actually it doesn't even have to be a bot that is doing the opping. If a master ops, and the opped user changes nick, the same thing happens.
I had this behavior with two 1.6.8 bots compiled and running on two different shells. I upgraded one of them to 1.6.9 and tried it again.
I've simulated the problem with a 1.6.8 (Freggel) and a 1.6.9 (Calimero) linked and sharing user files. I've let one bot op a test user (Freggel, -bitch). No problem for the other bot. I changed the test user nick: the other bot (calimero, +bitch) deops:
ùíù mode/#channel [+o deoptest3] by Freggel
ùíù deoptest3 is now known as deoptest4
ùíù mode/#channel [-o deoptest4] by Calimero
this is by design. eggdrop will not reverse most mode changes made by masters and bots. however, it does not store anywhere that clientA was opped by a master/owner etc. when clientA changes his nick to clientB, this changes his info in the bot's internal chanlist. it then suddenly realises that clientB is opped on a +bitch chan with no flags, and deops him. The same thing would happen if you did a .reset on the chan, or kicked the bot and reopped it.