mIRC Home    About    Download    Register    News    Help

Print Thread
#77706 03/04/04 06:54 PM
Joined: Jul 2003
Posts: 742
MTec89 Offline OP
Hoopy frood
OP Offline
Hoopy frood
Joined: Jul 2003
Posts: 742
Following a mode flood (see below) like when i Op chanserv to stop the flood, chanserv in the nicklist is not opeed, when "he" actually is.

Code:
01:49.11> * Now talking in #blah
01:49.12> * ChanServ changes topic to 'blah'
01:49.13> * ChanServ sets mode: +ntr
01:49.13> * XXLBoT (XXLBoT@Mythical.Net) has joined #blah
01:49.13> * XXLBoT sets mode: +oa XXLBoT XXLBoT
01:49.13> * ChanServ (services@mtec89.com) has joined #blah
01:49.14> * ChanServ sets mode: +oa ChanServ ChanServ
01:49.14> * ChanServ sets mode: -o MTec89
01:49.15> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.15> * other.server.im.not.on sets mode: -ntr
01:49.15> * other.server.im.not.on sets mode: -oh XXLBoT XXLBoT
01:49.16> * other.server.im.not.on sets mode: -oa XXLBoT XXLBoT
01:49.16> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.16> * other.server.im.not.on sets mode: -oa ChanServ ChanServ
01:49.16> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.17> * other.server.im.not.on sets mode: +o MTec89
01:49.17> * ChanServ sets mode: +ntr
01:49.17> * ChanServ sets mode: +A
01:49.18> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.18> * other.server.im.not.on sets mode: -ntr
01:49.18> * ChanServ sets mode: +ntr
01:49.18> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.19> * other.server.im.not.on sets mode: -A
01:49.19> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.19> * other.server.im.not.on sets mode: -ntr
01:49.19> * ChanServ sets mode: +ntr
01:49.20> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.20> * other.server.im.not.on sets mode: -ntr
01:49.20> * ChanServ sets mode: +ntr
01:49.21> * irc.mtec89.com sets mode: +qa MTec89 MTec89
01:49.21> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.21> * other.server.im.not.on sets mode: -ntr
01:49.21> * ChanServ sets mode: +ntr
01:49.22> * MTec89 sets mode: +o XXLBoT
01:49.22> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.22> * other.server.im.not.on sets mode: -ntr
01:49.23> * ChanServ sets mode: +ntr
01:49.23> * MTec89 sets mode: +o ChanServ
01:49.23> * other.server.im.not.on sets mode: -oh ChanServ ChanServ
01:49.23> * other.server.im.not.on sets mode: -ntr
01:49.24> * ChanServ sets mode: +ntr
01:49.36> * MTec89 sets mode: +o ChanServ


http://MTec89Net.com
irc.freenode.net #MTec89Net
#77707 03/04/04 11:24 PM
Joined: Dec 2002
Posts: 349
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Dec 2002
Posts: 349
The mode flood is a desync or missing Uline issue which is bouncing services' modes. I am not sure what you mean, but chanserv *would* appear deopped to all people on 'other.server.im.not.on' (and servers connected under it) during the mode flood, until you (a 'legal' op on all servers) properly opped it.

Unless the servers have reported a different purpose for +o (in numeric 005) I can see no reason chanserv would not be opped after you opped it. Does /names #blah show chanserv as opped?


Link Copied to Clipboard