hey folks, I was wondering if there is a way to halt the default action on CTCP

eg
On 1:CTCP:FINGER:{
haltdef
ctcpreply FINGER If you want to who I am, just ask me
}

I cant seem to find anything, but I'm reasonably sure that I've gotten this to work before
Cheers all
Stefan Leroux

You aren't allowed to change the default CTCP VERSION reply.

You could ignore all ctcp's by adding address *!*@* to the ignore list of the addressbook and checking the ctcp ignore option. But in that case you cannot send a reply.

Sorry, my example was only meant to be that. I was more looking to change the Finger reply, since atm it gives out my name, but I wanted to make it act with a script to instead do something such as my current song kinda thing.
No matter if its not possible, thanks guys

its possible.


for other you can use this:

Helping someone remove the default VERSION reply, when it's not meant to be removed or changed. Tut tut.

its still his choise at the end

It was your choice, you were the one who said it. Why do you think it can't be halted, Khaled doesn't want it changed. Even when I said in an earlier post it isn't to be changed. Please read this carefully.

happy ?

I was never unhappy, but someone else may have been. I was just displeased.

Thank you WideOpenSpace, that works perfectly.

SladeKraven: I can see you point of view. Obviously my example was a bad one, but if it helps (and you choose to believe me) I can guarantee that I dont intend to stop, or alter the Version CTCP, it is only for the CTCP Finger I was looking.
- Have now read through your link about stopping the version being a violation of mIRC agreement. Is this also the case with finger?

I believe you when you say you wanted to change the FINGER reply. I have no idea where i got VERSION from. I must have misread your initial post.

Edit: If you are able to use haltdef then I assume it's not a violation. But I'm not entirely sure on that.

Ok, I like that assumption, and I've edited the original post. I can understand the confusion, maybe should have just made an example of what I wanted in the very first place.

Thanks to all

if finger would be illegal then it would be locked or just forced like version is.

since its not, i doubt its illegal.

This isn't a reply to anyone, but what i know it's not a bad thing to remove the version reply that are scripted, how ever for a fev years ago many people hexed mirc to remove the version reply, i belive that wasnt that good, but since you can halt the default output relative easy i don't think it's any problem, if Khaled didn't want you to, then i think he would have forced mirc to send a version reply even due you halt the default one, and i have seen many exmaple on this, one is that the coder ignored all ctcp's, then created a new signal that returned the ctcp reply he want it to send, and i think it's still avalibe for download on a respectable scripting site.

I think halting a default reply (version, etc) is not a violation, 'coz simply, Khaled coded mIRC with the "ability" to hide default replies

If he wanted, he could have easily programmed mIRC to "ignore" the /halt command if inserted within a VERSION ctcp

Allowed or not, I think mIRC's a great program and I'm happy to advertise that I'm using it if people check my version. I don't see any reason to hide it. Just my opinion, of course.

It's not that easy to halt the version reply.
You can't just use the ctcp event and halt it, you need to use debug to catch a few things, it's not that simple to the newbie scripter at all. And why you say "if Khaled didn't want you to, then i think he would have forced mirc to send a version reply even due you halt the default one"

Then why did he start adding cyclic redundancy checks to render mIRC useless when someone tampered with the version reply, or any other internal code?

I havent seen anything that say you arent allowed to in any files or pages on the net, what i know the only thing he don't like is when you edit the mirc.exe it self, as i wrote befor it was a populare thing to hex out the version reply, even change the default icons inside mirc.exe, and that's not allowed.

you've completely contradicted yourself in that whole post.

It used to say "Editing the mIRC version reply, huh? :)"

That got removed, and cyclic redundancy checks got added to stop morons from removing the version reply and such like, because some people were using mIRC for illegal activities other than chatting.
I personally think khaled wanted to stop masses of bots from doing their illegal things on IRC
That's why you find some servers now won't let you connect if you don't have a version reply of most of the commonly used clients, including this one.

why are "they" morrons ?
coz they dont want "made by bla bla bla bla" in their reply ?

What difference does it make if the version reply is stopped by ignoring ctcp's altogether or by some other means? I stop version replies with a dll because I don't want to reply to a version request simply because I just don't want to.

~ Edit ~

Nowhere in the help file and license agreement does it say we're not allowed to halt or change the version reply. The only statement about it is in the CTCP events section that says "Note: You can't prevent the standard version reply from being sent." We just can't do it by hacking the exe.