mIRC Homepage
Posted By: pouncer ctcp isnt working - 03/04/07 01:10 PM
say for e.g i do..

/ctcp pouncer TIME hi

then on my script

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

it doesn't echo. hmmm
Posted By: genius_at_work Re: ctcp isnt working - 03/04/07 02:18 PM
I don't think the ctcp event use the ^ prefix.

-genius_at_work
Posted By: RoCk Re: ctcp isnt working - 03/04/07 02:23 PM
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.
Posted By: landonsandor Re: ctcp isnt working - 03/04/07 04:40 PM
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
Posted By: RoCk Re: ctcp isnt working - 03/04/07 06:06 PM
I didn't say using the ^ was causing the problem, I said...

Quote:
the ^ is not necessary in the ctcp event for haltdef.
Posted By: landonsandor Re: ctcp isnt working - 03/04/07 07:09 PM
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.
© mIRC Discussion Forums