Zugg Software :: View topic - Can someone help? Need to fix a bug involving timing events.

Posted: Sat Jan 29, 2005 3:31 am

Ok, I have written a script for the MUD Aardwolf, which tracks (amongst other things) how long it takes me to "quest". It then averages my quest time overall, for output from an alias. However, whenever I begin a quest BEFORE an even hour (7:00:00pm for example), and end AFTER the hour (so, say, start at 06:59:45pm and end at 07:00:46pm), it counts the time as minus (in the above example, would be like -58 minutes -59 seconds).

However, if I were to simply put in an if statement (if time is not greater than 0, don't add) it would obviously then not track all quests, which would throw off averages and such, unless I had it remove all statistics from the quest (not the desired result). Anyone have a suggestion on how to fix it? Some of the code below:

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

Instead of using %time() you could use the %secs variable
first we make a permanent variable fullday which basically is just how many milliseconds is in a full day

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

#var timeqc %eval( %eval( 60 * %eval( %time( nn)-@QSMinute)) + %eval( %time( ss)-@QSSecond))

First, you need to replace the #VARIABLE command with the #FUNCTION command in the above statement. Otherwise, the command gets evaluated immediately and only the result is put into the variable.

Second, the statement evaluates the difference in minutes {%eval( 60 * %eval( %time( nn)-@QSMinute))} and the difference in seconds {%eval( %time( ss)-@QSSecond)} but has nothing to account for a difference in hours. To fix it, simply add a statement to evaluate the difference in hours {%eval (3600 * %eval( %time( hh) - @QSHour))}. Of course, you'll also need to create @QSHour.

Adept Joined: 20 Jul 2004 Posts: 268

Been using this one for a while now, and never ran into a problem with it: