Stripping the codes is a good idea.
I've only seen ChanServ put it in bold in the first line
'-ChanServ- SOp list for #awyeah'.
After that, I know all nicks, and ip addresses listed of
the access list are in plain text format without any control codes.
However there might be one, at the end as well '-ChanServ- End of list'.
Alchera use, any:
Code: Select all
putquick "PRIVMSG chanserv@services.dal.net :AOP $chan list" -next
putquick "PRIVMSG chanserv@services.dal.net :AOP $chan list"
putserv "PRIVMSG chanserv@services.dal.net :AOP $chan list"
But specify, '
chanserv@services.dal.net' not simply '
chanserv'
DALnet has enfocred this because:
Services impersonators use similar nicks to ChanServ, like:
ChanSev, ChannelServ, ChanService, ChanServices, ChanServer etc.
to fool people into getting their passwords. So just by simply: /msg chanserv <bla bla> (wont make chanserv get your command)
On DALnet you will need to specify: /
chanserv@services.dal.net.
As the part after the @ is like the uhost. So even if an impersonator uses a nick, and a user mistakenly sends a notice to:
E.g: /msg
ChanService@services.dal.net (the msg will not go as a nick with that uhost would cease to exist, if the nick ChanService is online)
That is why they came up with this thing.
So for everyone I suggest you use:
/msg chanserv@services.dal.net bla bla
Another alteration can be:
/chanserv bla bla
For that, on mIRC like I use: /chanserv aop #chan list
In, tcl if it works it can be something like: (Only for DALnet!)
Code: Select all
putserv "chanserv aop $chan list"
or
putserv "chanserv :aop $chan list"
#I am not sure but one of these will work. I think the one without the ":".
#You can use the same with putquick, puthelp etc.
Everyone, who reads this post... please be aware this is only for DALnet's ChanServ as I am not aware with ChanServ services of other IRC networks.