I'm trying to think of a way of detecting when the player fast travels, and how long the journey time is, as part of the weather system for All Natural. Here's the current code:

set travelTime to ((GetCurrentTime + (GameDaysPassed * 24) - currentTime)/TimeScaleif travelTime >= 0.01				set flag to 1				set weatherShouldForce to 1				set fastTraveled to 1			elseif travelTime >= 0.0002				set flag to 3				set weatherShouldForce to 1				set fastTraveled to 1endifset currentTime to GetCurrentTime + (GameDaysPassed * 24)

Basically, it's supposed to force a new weather if you fast travel a distance that results in a large travelTime, and set the old weather on a small travelTime. The check is carried out for every cell change, though currentTime is updated every time the script is run.

However, I'd like it to change the weather if the travel time is greater than the predetermined time for the current weather to last. The time set for the next natural weather change is given by timeForCheck, which is the currentTime at the time of the weather being set plus the weather length.

I have that sort of system set up for the sleep/wait menu:

begin menumode 1012;Sleep/Wait Menuif IsTimePassing == 1	if (GetCurrentTime + (GameDaysPassed * 24)) < timeForCheck		set flag to 3		set weatherShouldForce to 1	elseif (GetCurrentTime + (GameDaysPassed * 24)) >= timeForCheck		set flag to 1		set weatherShouldForce to 1	endifendifend

So I was wondering if there was any way of doing the same thing for Fast Travel, without triggering it for normal cell transitions (as if I put similar checks into the GameMode cell change checks, one of the options would be true for every check, regardless of Fast Travel or not, and would lead to screwy weather.

Any help would be greatly appreciated.

begin menuMode

Right, so I've got to check for when people click yes to the 'do you want to fast travel to this location' messagebox?

The problem with that would be with stuff like Map Marker Overhaul, which does the same thing, but with a modifier key to bring up a different menu, so would I be able to prevent that from giving a false positive?

EDIT: Nevermind that, I think I'll do it as before, but with proper timings instead.

A very simple way to detect fast travel is to set a variable to game hour when the map menu is opened, then back in gamemode check if that variable == gamehour. If not then the player fast traveled. Using istimepassing doesn't seem to work for fast travel.

Yup. The issue you've brought up can be mitigated ( to some extent ) by loading your mod before MMO, thereby getting your script to run before MMO's.

Oh, I didn't know that load order affected script running order. :huh:

I think I've got a solution anyway, b3w4r3's suggestion seems to work fine, hopefully I'll get confirmation of that by tommorrow morning, but thanks for the help anyway.

Only found out recently. I added more info about it to the script processing article http://cs.elderscrolls.com/constwiki/index.php/Script_Processing.

Wait... what? Script processing is dictated / modified by mod load order? Seriously? Geez... the things you learn after 3 years...

I spent a good 30 minutes on testing the process queue and that was the pattern that I saw. But I do recall a particular instance ( or two ) when it didn't follow the predicted order.