Zugg Software :: View topic

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

anyone know a way to calculate this?

(Sun Jun 5 15:31:43 2005) - (Wed Jun 1 14:36:01 2005) = ??? minutes
or
(Fr Dec 30 10:00:31 2005) - (Mon Jan 2 9:11:05 2006) = ??? minutes

minutes_uptime = ???

I shoulda payed more attention in math class :P

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Why not just use %ctime which is for connected time in milliseconds.

Adept Joined: 14 Jun 2003 Posts: 222 Location: Chile

I found an interesting website that does that for you, I'm sure we could come up with an interesting function as well :D
http://www.calendarhome.com/date.shtml

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Umm, let's see...

The formula we need to end up with is (Days * 86400) + (Hours * 3600) + (Minutes * 60) + Seconds

However, since the number of days varies every 4 years (every 400 years for years that end in 00) and since there are a varied number of days in each month, we first need to first convert our dates to a Days format. For this, we need to use a 365-day year lookup table:

#case %ismember(%1, "Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec") {Days = 0} {Days = 31} {Days = 59} {Days = 90} {Days = 120} {Days = 151} {Days = 181} {Days = 212} {Days = 243} {Days = 273} {Days = 304} {Days = 334}

Now we test for leapyear and whether we have passed it or not:

#if (%ends(%3,"00")) {LeapYear = %mod(%3,400)} {LeapYear = %mod(%3,4)}
#if ((@Days + %2) > 59) {#noop we are on or past feb 29;#if (@leapyear) {#add Days (%2 + 1)} {#add Days %2}}

At this point, we now have our Date reduced to Days and can resolve our formula:

DateInSeconds = %eval((@Days * 86400) + (%4 * 3600) + (%5 * 60) + %6)

This will convert a date into seconds, allowing you to do something like this to figure out uptime (once you get the #FUNCTION correctly written up):

UptimeInSeconds = DateInSeconds(Month, Day, Year, Hour, Minute, Second) - DateInSeconds(Month, Day, Year, Hour, Minute, Second)

Adept Joined: 14 Jun 2003 Posts: 222 Location: Chile

The rule for years that have 1 more day is that they are divisible by 4
so you could skip the 400 part and just look if the year is divisible by 4, if not, then its a 365 days year.
Very nice efficient script though.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

nexela: trying to compute between mud uptime and current time... not connection time.
DeReP: it also needs to do the actual time down to minutes, dont care about the accuracy of seconds.

MattLofton, im so glad you posted that days list... i came up with:

#VAR day_of_year {0|31|59|90|120|151|181|212|243|273|304|334}

but wasnt sure if i was correct on it.

I didnt figure seconds... didnt care to be THAT exact.. so i did days*1440

I have the script written now... still doing testing on it, so far it takes:

Since Reboot Since Added
Mob Deaths : 706,560 272,112,958

and 2 time lines:

Aardwolf entered a new age at Wed Jun 1 14:36:01 2005
The system time is Mon Jun 6 14:57:48 2005

i then use a condition 'within' trigger to fire off of system time and see in #SHOWS:

+---------------------------------------------------
| Mobs Killed: 112958
| Mobs Need Killing: 887042
| Aardwolf rebooted: 0y 0m 5d 0h 21m ago.
| Minutes Since Reboot: 7221
| Mobs killed per minute: 97
| Prediction: 6d 8h 24m till next hour of double.
+---------------------------------------------------

like i said the 47 seconds i aint critically worried about as im going by avg kills per minute.

didnt realize how many variables i used...
1 alias (fires the 2 info commands)
3 triggers (captures mob,boot,time info)

and.... FORTY variables :P

i also didnt allow for leap year... so my script will 'break' in 2008 :P

I'm also pretty sure from my math that its gonna break between DEC and JAN... didnt do a IF num_months < 0 calculation.

But anyhoo... i ramble, thanks a bunch your info helped a ton. :)

Wanderer Joined: 07 Dec 2004 Posts: 65

I would use VBScript for this problem, much simpler.

#alias timediff {#noop VBScript
#mss {MinDiff = DateDiff(~"n~", ~"%1~", ~"%2~")}
#show {Time Difference ~[ %1 ~] ~[ %2 ~] = %mss(MinDiff) minutes}}

Input:

timediff "1/1/2005 12:00:00" "1/1/2005 13:00:00"
timediff "1/1/2005 12:00:00" "1/2/2005 12:00:00"
timediff "6/1/2005 14:36:01" "6/5/2005 15:31:43"
timediff "12/30/2005 10:00:31" "1/2/2006 9:11:05"

Output:

Time Difference [ 1/1/2005 12:00:00 ] [ 1/1/2005 13:00:00 ] = 60 minutes
Time Difference [ 1/1/2005 12:00:00 ] [ 1/2/2005 12:00:00 ] = 1440 minutes
Time Difference [ 6/1/2005 14:36:01 ] [ 6/5/2005 15:31:43 ] = 5815 minutes
Time Difference [ 12/30/2005 10:00:31 ] [ 1/2/2006 9:11:05 ] = 4271 minutes

If VBScript is not an available scripting language on your computer, then you can download Microsoft Windows Script 5.6 here:

http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp

You have to check "Allow VBScript" in preferences/script parser within zMUD.

Wanderer Joined: 07 Dec 2004 Posts: 65

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

mud output:

Wanderer Joined: 07 Dec 2004 Posts: 65

The replace function in the time alias is removing all the zeros.

I don't know why...

So "10:00:01" would be replace by "1::1".

You can get the script to work correctly if you quote the %key and %val variables in the #loopdb line within the time alias.

#loopdb @db {#variable %1 %replace(@{%1},"%key","%val")}

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

If its still needed here is a working Aardwolf example 1 var, 1 trigger:p

#VAR Months {Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec}
#TRIGGER "t_uptime" {^Aardwolf entered a new age at %w (%w) (%d) (%x) (%d).} {}
#COND {^The system time is %w (%w) (%d) (%x) (%d)(.)} {
#MSS {uptime = datediff(~"n~", ~"%ismember( %t1, @months)/%t2/%t4 %t3~", ~"%ismember( %1, @months)/%2/%4 %3~")}
#SHOW Uptime is %mss( uptime) minutes

SEEEEE I can be usefull

Wanderer Joined: 07 Dec 2004 Posts: 65

Nice job Nexela Smile

Here is my script for Medievia based on Nexela's post: