bug with "clock clicks -milliseconds"

[Caribou]

Hello

Few weeks ago i did a ping reply on my bot using "clock clicks -milliseconds" to be more effective.

It worked nicely for about weeks, but now it is not working anymore, i did not modified the source code, its still the same...

I tried to see why its not working anymore, and i found that [clock clicks -milliseconds] is now giving a Negative number .. thats mean something like -845421547 .. then ping is not working anymore with a negative number.

Does anyone already had this sort of problem ? a [clock clicks command who give negative numbers ? i don't understand why it does this, maybe my shell hosting got bugged out ?

Maybe this bot is just too much online and getting crazy..

Thanks for anyhelp and sorry for my bad english

[Caribou]

I forgot to say, its a !ping command for users

Here is the source code :

Code: Select all

bind pubm - *!ping pub:ping
bind ctcr -|- PING ctcr:pingreply

proc pub:ping { nick uhost handle channel arg } {
 global ping status
 if {$status(listen) == "on" && [llength [split $arg " "]] == "1"} {
  set ping "[expr [clock clicks -milliseconds]]"
  putserv "PRIVMSG $nick :\001PING $ping\001"
 }
}
proc ctcr:pingreply {nick uhost hand dest key arg} {
 global ping
 set temp "[expr [expr [clock clicks -milliseconds]. - $ping.] /1000.]"
 putquick "NOTICE $nick :15,2Ton 8Ping15 avec le bot est de 9$temp15 sec"
}

[Ofloo]

the problem is that it has a - value i gues .. try to make it possitive i have experianced this to before it comes and goes don't know why ..

[stdragon]

Well, I think using abs() will solve the problem.

set temp "[expr abs([clock clicks -milliseconds] - $ping) / 1000.0]"