mIRC Home    About    Download    Register    News    Help

Print Thread
#174171 03/04/07 01:10 PM
Joined: Oct 2005
Posts: 827
P
pouncer Offline OP
Hoopy frood
OP Offline
Hoopy frood
P
Joined: Oct 2005
Posts: 827
say for e.g i do..

/ctcp pouncer TIME hi

then on my script

ctcp ^*:*: echo -a $nick $1-

it doesn't echo. hmmm

Joined: Oct 2005
Posts: 1,741
G
Hoopy frood
Offline
Hoopy frood
G
Joined: Oct 2005
Posts: 1,741
I don't think the ctcp event use the ^ prefix.

-genius_at_work

Joined: Dec 2002
Posts: 2,031
R
Hoopy frood
Offline
Hoopy frood
R
Joined: Dec 2002
Posts: 2,031
It worked here even with the incorrect format. Are you ignoring CTCP's ?
mIRC has a built-in ctcp time response and just like version, it will only
respond once in 10 seconds. Try something different, for example..
/ctcp pouncer test hi

ctcp *:*:*:echo -a $nick $1-

Also, the ^ is not necessary in the ctcp event for haltdef.

~ Edit ~
What genius said.

Last edited by RoCk; 03/04/07 02:25 PM.
Joined: Dec 2002
Posts: 1,541
L
Hoopy frood
Offline
Hoopy frood
L
Joined: Dec 2002
Posts: 1,541
actually, I've been using the ^ and haltdef for years now and it works fine with it. There may be a 2nd ctcp event in the script file which is causing this one not to work (as an alternative solution). What I've been using is (basic formatting):

Code:
ctcp ^*:*: {
  if (stuff) { }
  elseif ($1 == clientinfo) { }
  elseif ($1 == dcc) { }
  elseif ($1 == finger) { }
  elseif ($1 == ping) { }
  elseif ($1 == time) { }
  elseif ($1 == userinfo) { }
  elseif ($1 == version) { }
}


That has all worke3d for me no problem so ^ can be used in a CTCP event


Those who fail history are doomed to repeat it
Joined: Dec 2002
Posts: 2,031
R
Hoopy frood
Offline
Hoopy frood
R
Joined: Dec 2002
Posts: 2,031
I didn't say using the ^ was causing the problem, I said...

Quote:
the ^ is not necessary in the ctcp event for haltdef.

RoCk #174192 03/04/07 07:09 PM
Joined: Dec 2002
Posts: 1,541
L
Hoopy frood
Offline
Hoopy frood
L
Joined: Dec 2002
Posts: 1,541
sorry, I meant to reply to genius's post not yours. No you never said it was a problem but he said he thought ctcp events didnt use the ^:

Quote:
I don't think the ctcp event use the ^ prefix.


Those who fail history are doomed to repeat it

Link Copied to Clipboard