Page 2 of 2
Posted: Sat Jul 17, 2004 10:40 am
by Solutech
I had some trouble from a couple of users using clonesx and flooding out the server . Best thing I found was to locate the original connection and gzline it . That stopped the flood . Bopm helped as he was using proxies and that caught a lot of em.
Posted: Sat Jul 17, 2004 1:12 pm
by katsklaw
aquanight wrote:Huh? All CTCPs use PRIVMSG and NOTICE...
PRIVMSG :\1PING 123\1 - CTCP request
NOTICE :\1PING 123\1 - CTCP reply
In a RAW debug window I get this for VERSION and other CTCP events.
There is no CTCP argument listed, regardless .. mirc allows for total CTCP ignores without hindering DCC, actions, notices or privmsg.
Posted: Sun Jul 18, 2004 11:43 am
by w00t
A /me is sent like this:
:w00t PRIVMSG #test :\1ACTION makes toast\1
A version request is:
:w00t PRIVMSG blahbot :\1VERSION\1
(from memory). So all CTCP does is piggyback on top of privmsg, right? Feel free to correct me.
Posted: Sun Jul 18, 2004 4:47 pm
by codemastr
w00t, no, a CTCP request uses PRIVMSG. A CTCP reply uses NOTICE.
Posted: Sun Jul 18, 2004 11:36 pm
by w00t
Oh! Thanks, I've only ever looked at the request side of things (never needed to see replies) but I'll file that away for when I do
Posted: Sat Jul 24, 2004 3:40 am
by katsklaw
codemastr wrote:w00t, no, a CTCP request uses PRIVMSG. A CTCP reply uses NOTICE.
Which was shown in my code from my last post
Posted: Sat Jul 24, 2004 1:53 pm
by Syzop
This thread is getting rather off-topic, I think it can be closed.