Zugg Software :: View topic

Magician Joined: 23 Apr 2003 Posts: 358 Location: USA

The world in which DragonRealms takes place has 3 moons upon which Moon Mages depend.

I'm trying to write a script that will predict when they will rise and set. They rise every 5 hours and 50 minutes (give or take a few minutes depending on the moon, and give or take a few minutes depending on some random factor).

It's easy to set an alarm based on when one rises/sets during the current session, but what if I haven't been in game for a few days? Any help?

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

make the alarm store the %time of the moons
I am not going to write a spicific script for you because I can not test it at this time.

along that same route you could then use %time to make a database to keep track of the cycles but as you stated it is not garonteed because of outside influences.

Stick with just the Alarm

Most game have a mud time and a game time use these to pin point the rising and setting of the moons, maybe?

megamog75

Keeper of the only printable help files for Zmud.

Wanderer Joined: 26 Jan 2001 Posts: 74

quote:
I'm trying to write a script that will predict when they will rise and set.

Hmm.. Well, it depends on how hard core you want to be about this too. With Zmud able to capture the gsl tags now, you can use a trigger to grab the game time when a moon rises or sets. With enough captures, it wouldn't be too hard to figure out a pretty tight time period, and to predict when the next event would occur, even if you didn't connect for days at a time.

I can tell you that after to talking to GMs there, the lunar system had a lot of thought behind it, and should be trackable. The big thing that would screw you up would be game crashes and/or resets, which might throw a wrench into any system that you managed to work out.

Ana

Magician Joined: 23 Apr 2003 Posts: 358 Location: USA

The moons are each on their own cycle, which is seperate from the sun. Just like the Earth's moon rises a few minutes earlier or later every day depending on the time of year, as do the moons of Elanthia. I've collected quite a bit of data.

My problem now is using the functions of zMUD to figure out when the next rise (or set) will be, ignoring the random element. Here's an example:

quote:
The black moon Katamba rises at noon IRL. In game, it's the right at the 6th "anlas" (1 anlas = 30 minutes, there are 12 anlaen in one game day, 4 game days in one RL day). It will rise again at 5:50pm, which is 10 minutes before the 6th anlas of the following game day. Next time it will rise will be 20 minutes before the 6th anlas (10 after the 5th). So, the next RL day, Katamba will rise not at noon, but at 11:20am, 10 minutes before the 5th anlas.

Given a variable (call it @Katamba) of the last confirmed rise of Katamba being... 3 RL days ago, how can I get zMUD to calculate when Katamba will rise again?

If #ALARM or %alarm can help, I'd like to know what the syntax should be.

Wanderer Joined: 26 Jan 2001 Posts: 74

quote:
The black moon Katamba rises at noon IRL. In game, it's the right at the 6th "anlas" (1 anlas = 30 minutes, there are 12 anlaen in one game day, 4 game days in one RL day). It will rise again at 5:50pm, which is 10 minutes before the 6th anlas of the following game day. Next time it will rise will be 20 minutes before the 6th anlas (10 after the 5th). So, the next RL day, Katamba will rise not at noon, but at 11:20am, 10 minutes before the 5th anlas.

Well, forget anlas. You'll go nuts trying to track it with that. If you need that, convert it back at the end from minutes.

quote:
Given a variable (call it @Katamba) of the last confirmed rise of Katamba being... 3 RL days ago, how can I get zMUD to calculate when Katamba will rise again?

Use the gsl(q) variable to capture the last setting, then figure out how to add the period til moonrise to get what the next q variable should be. Rise and set should be reasonably predictable days in advance just by adding total period to the last captured (q).

Ana

Magician Joined: 23 Apr 2003 Posts: 358 Location: USA

I didn't realize that %gsl(q) was a timekeeper. That's incredibly helpful, here and in other applications.

Wanderer Joined: 26 Jan 2001 Posts: 74

quote:
I didn't realize that %gsl(q) was a timekeeper.

I don't know how good a timekeeper it is, but it has that function, and is forecastable. You can see that it is via some of the RT timers floating around.

Ana

Apprentice Joined: 09 Jun 2002 Posts: 186 Location: USA

You have to love moon mages. Boy are you guys pain in the butts. Can't be easy to get along with like the empaths.....GEESH! NO! You have to go and figure out the cycle of the moons......
....
....
In any case if you figure this out let me know. I have a moon mage as well!