Zugg Software :: View topic

Adept Joined: 24 Aug 2004 Posts: 277

CMud Pro Beta 3.22a
Windows 7 64bit

Can I get someones assistance on this please. I kind of got it working, but it's not exactly pretty, and it's got way too much going on.

What I have is the following line:

Likelihood of Flux: 5.94%

The trigger I have set up is this:

Likelihood of Flux: (%d)*

and my code is as follows:

Posted: Wed Aug 18, 2010 3:31 pm

Ok we can simply things greatly here. First thing to note is that it resets every hour which we all know is 3600 seconds. Second for speed we are going to use local variables and get rid of a lot of the intermediary variables we don't need. Finally we will tweak your trigger just a bit to be more precise.

Here's what you end up with.

First I know it's 3600 secs (1 hour) by working backwards. It came so close I assumed that's that it was then confirmed. That would mean it goes up 1% every 36 seconds. 1 divided by 18 is 0.0555..(repeating) hence it goes up by 0.06% every two seconds by rounding up.

Adept Joined: 24 Aug 2004 Posts: 277

Thank you for the reply.

Something didn't quite work properly. When I use your trigger, it's supposed to return approx 11 minutes, but it shows this instead.

68.31
31.69
0.00880277777777778
0.528166666666667
0 min and 31 sec.

Wizard Joined: 22 Mar 2007 Posts: 2320

There's nothing wrong at all. Tech told you that he added some extra #ECHO lines to show you various forms of the calculations. The 0.008802777777778 is the value in hours, the 0.527166666667 is the value in minutes, and the last line is minutes and seconds. He only put those lines in to help you see what was going on. You can remove those lines, or change the output however you want.

Adept Joined: 24 Aug 2004 Posts: 277

That's what I mean tho, it returns 0 minutes when it should be 11.

Posted: Wed Aug 18, 2010 5:13 pm

What should be 11 exactly? You said [quote" Loftaris"]The % increases .06% every 2 seconds[/quote], although in your code you used "0.6" vs "0.06".

That what i used as the basis for my calculations. The #ECHOs were to reinforce how I arrived at my calculations so that you can easily make corrections if they were incorrect.

What was your percentage value when you expected the remaining time to be 11 minutes? Does is it increase "0.06%" every 2 seconds, or "0.6%" every 2 seconds? In either case the trigger is easily correctible.

Can you include the text you received and the full output text of the trigger I posted.

Adept Joined: 24 Aug 2004 Posts: 277

Maybe my math was wrong, like I said I was having troubles with it, and it's quite possible I borked it up.

With my trigger, it turns

Timescan <Dark room>:[yellow] [Likelihood of Flux: 75.70%]

into

Timescan <Dark room>:[yellow] [Flux: (8.33 minutes])

each heartbeat (every 2 seconds) it will increase from 75.70, to 75.76.

if I change it to .06 in my math, it goes from 8 minutes, to 83 minutes. I'm not entirely certain (as I just got the power and haven't had much time to test it), but I thought I figured out 100% is approx 30 minutes.

if 1% is 33.33 seconds, 100% would be 33.33 minutes. (1 percent / .06 * 2(each tick is 2 seconds instead of 1) = 33.33)

Tell me my math is faulty?

Posted: Wed Aug 18, 2010 7:26 pm

It is. As I explained in my math even though it increases 0.06% every two seconds, this is really an artifact of rounding it is 0.55555555 (the five repeats ad infinitum).

Even assuming it is 0.06 exactly you have

Adept Joined: 24 Aug 2004 Posts: 277

Excellent, thanks so much for your time/help! I appreciate it!

Adept Joined: 24 Aug 2004 Posts: 277

I know this is an old post, but it's relevant to this exact trigger.

Posted: Wed Dec 14, 2011 8:42 pm

Adept Joined: 24 Aug 2004 Posts: 277

I jumped the gun. Something's wrong in the calculation.. It's not displaying the proper time.

However it's working, somewhat.

Adept Joined: 24 Aug 2004 Posts: 277

This is the output I get using your code.

14:51:32 Timescan <The Center of Town>:[purple] [22 min and 34 sec. (59.37%) 15:38]

Each time I scan it, the ETA increases, it never decreases..? hrm.

Posted: Wed Dec 14, 2011 10:12 pm

Yeah, that was my fault. The $Min should only be:

Adept Joined: 24 Aug 2004 Posts: 277

That fixed the counting problem.

My last question. It's currently showing 6:6 instead 6:06 .. Is that easy to fix?

Thanks so much! I love this. I've been counting it in my head for a long time heh.

Posted: Wed Dec 14, 2011 11:55 pm

Quite easy.

Where you display the $Min, do this instead:

Adept Joined: 24 Aug 2004 Posts: 277

that sends it to the mud, I put it under the $min and in the #sub, but it still sends it to the mud instead.

Adept Joined: 24 Aug 2004 Posts: 277

I also just realize there's a little glitch.

18:02:58 Timescan <The Center of Town>:[red] [3 min and 16 sec. (94.10%) 18:5:11]
18:03:03 Timescan <The Center of Town>:[red] [3 min and 8 sec. (94.34%) 18:6:11]

It doesn't count the seconds properly, when it should say 18:06:11, it's showing 18:05:11

I also added seconds to the calculation using your examples, probably obvious tho. heh

Adept Joined: 24 Aug 2004 Posts: 277

I've been unable to fix this by tinkering with the script.

Any suggestions on how to correct the calculation trouble?

Posted: Fri Dec 16, 2011 9:33 pm

I'm not sure why it would send it to the MUD. I said where you display the $Min. It seems like you're putting it on its own line.

You'd need it to be:

Adept Joined: 24 Aug 2004 Posts: 277

Thanks. I won't be able to test this for a day or two.. When I do, I'll let you know.

Thank you!

Adept Joined: 24 Aug 2004 Posts: 277

Uh.. I'm quite possibly mentally retarded, but I have no idea what's going on.

I imported your example, but it's not anywhere to be found.. if I try to import it again, it says there's already one there.

I've "searched" and manually browsed every trigger I have and it's nowhere to be found, nor does it work...

You managed to create an invisible trigger...

Sorcerer Joined: 15 Apr 2011 Posts: 809

It's not a trigger, it's a function.

Posted: Sat Dec 17, 2011 8:51 pm

It's a function, as Daern said. That's why I said in the trigger YOU have created (from the above posts), all you need to do is, in the #SUB {blah blah blah} line, change the part that displays the time to @fluxtime(%1).

I don't know exactly what your trigger looks like, so I can't quite copy/paste it for you. The only change you need to make is putting the @fluxtime(%1) in there where you display 11:34.

Edit:

Actually, give me a few, and I'll remake the trigger for you so that it can be just imported over and we should be done.

Posted: Sat Dec 17, 2011 9:21 pm

Here: This is the trigger you should use. It utilizes #SAYADD (which adds information to the line instead of needing to completely sub it out). This works as-is (tested it on my end), but if you have any questions whatsoever, let me know.