mIRC Home    About    Download    Register    News    Help

Print Thread
#112620 25/02/05 06:54 PM
Joined: Jan 2005
Posts: 37
S
Scratch Offline OP
Ameglian cow
OP Offline
Ameglian cow
S
Joined: Jan 2005
Posts: 37
I think I've found another bug in mIRC v6.16.


How to reproduce:

In the Options dialog, goto the IRC -> Flood section and disable Ctcp replies under the Enable protection section.


Now, connect to an IRC network, and execute the following command:

//timer 10 1 .ctcp $me VERSION

Now since you have Ctcp protection disabled, mIRC should not queue the CTCP requests, and you should be seeing a total of 10 CTCP VERSION requests appearing at a 1 second interval, but for some reason, mIRC is still queuing them.

It seems that this option is not sticking/working correctly.

#112621 25/02/05 07:15 PM
Joined: Feb 2005
Posts: 681
M
Fjord artisan
Offline
Fjord artisan
M
Joined: Feb 2005
Posts: 681
This is not because of your flood settings .. it's because
mIRC will only reply to 1 version request in 10 seconds.
This is intended behavior .. try another CTCP and it will
do as you're expecting.

#112622 25/02/05 07:39 PM
Joined: Jan 2005
Posts: 37
S
Scratch Offline OP
Ameglian cow
OP Offline
Ameglian cow
S
Joined: Jan 2005
Posts: 37
That doesn't seem very logical since the Ctcp protection is disabled...

#112623 25/02/05 07:55 PM
Joined: Feb 2005
Posts: 681
M
Fjord artisan
Offline
Fjord artisan
M
Joined: Feb 2005
Posts: 681
It only does this with version requests, no other CTCP's I believe.
Try another CTCP, like //timer 10 1 .ctcp $me TIME

~ Edit ~
I'm sorry, I meant to say mIRC will only reply with it's
default version reply once in 10 seconds, if you have
a custom/scripted version reply, it will not be effected
by this.

~ Edit ~
Upon testing with TIME, it seems TIME & FINGER both
behave this way, as well as VERSION. So it seems
that any internal mIRC CTCP replies behave this way.

Last edited by mIRCManiac; 25/02/05 08:04 PM.
#112624 11/03/05 04:03 AM
Joined: Mar 2005
Posts: 7
T
Nutrimatic drinks dispenser
Offline
Nutrimatic drinks dispenser
T
Joined: Mar 2005
Posts: 7
I doubt this is something to do with mIRC, a CTCP is sent via the server, not client->client .. CTCP's are sent with PRIVMSG, when you send heaps, the IRCd will truncate them and slow the sends down and 'lag' you a bit, it does this with normal privmsgs so i dont see how ctcps are any different...

#112625 11/03/05 04:57 AM
Joined: Sep 2003
Posts: 4,230
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
Its in mirc, the server may or maynot send them as fast as there issued, but mirc wont reply with any of its defualt replies at a rate faster than once every 10 seconds (or so), as said, you still recieve the ctcp's at what ever rate there sent from the irc server, but the defualt reply only occurs once.

CTCP ^*:VERSION*:*:echo -st $nick just doing a /CTCP $me $1-

Then do a //TIMER 10 1 ctcp $me version

you get all of them back, just mirc only tells u the version once (maybe twice on the tenth one i didnt get one tho)


Link Copied to Clipboard