Forums Feature Suggestions /ping accurate to milliseconds

The current implementation of CTCP PING uses the $ctime variable which results in a ping reply accurate to the second. However given that a high number of users are on fast digital connections, having a ping of 0sec when < 1000ms is not very useful.

I propose that CTCP PINGs be more accurate, perhaps to the millisecond by using a modified timestamp. I have implemented with mIRC script a new /ping command with the $ticks variable. This gives a less 'blunt' ping reply.

Aliases: (aliases.ini)
/ping raw -q PRIVMSG $$1 $+(:,$chr(1),PING $ticks,$chr(1))

Remote: (scripts.ini)
on 1:CTCPREPLY:PING*:{
echo 4 -a $+([,$nick PING reply]: $calc($ticks - $2),ms)
halt
}

This could of course be refined to use $asctime to format ping replies > 1000ms like mIRC's native implementation.

Hopefully this feature will be useful to people, and possibly included in future versions of mIRC.

Indeed, many of us write our own PING methods using "$ctime $ticks" like yours. Though, I'm happy with it the way it is, personally. Gives people something to do. And besides, $ticks is only accurate to about 100ms.

Btw, you may want to check if $2 exists, if not, then use $1. Some clients will only reply with your first parameter.

$2 IS the 1st paramter $1 is "PING"

Just a little shorter code:

Ah, DOH!

And for some reason I read $ctime $ticks in his example, when $ctime isn't even there.

* Raccoon goes to have his eyes checked.

There are optometrists for raccoons?

A simple new option could allow for us to designate this; giving the default in black text near the checkbox for customizing etc and an editbox to enter in the mirc $identifyer to use for it (only allowing time identifyers and nothing else so it couldnt be used to attack)