Once the script is compiled, variables aren't accessed by their name but by an internal index-number, thus the compiled scripts in a Tribunal mod and those in a non-Tribunal mod use different variables.

Dayspassed works fine with v1.0 - v1.2 (Vanilla Morrowind) You don't even need to declare it if you just want to read it. If you actually want to change the current day, you have to declare it, though. (Remember? I was the one who found this "hidden global" while working on Haldenshore two months before Tribunal came out...)

Dayspassed also works fine with v1.3 and v1.4 (Tribunal only) when your mod IS dependent on Tribunal.esm. No need to declare it.

The variable also works with v1.5 and v1.6 (Bloodmoon only, Tribunal NOT installed) as long as you declare it. It will no longer work when you don't declare the variable.

And finally it also works fine with v 1.5 and v1.6 (Tribunal AND Bloodmoon installed) as long as your mod IS dependent on Tribunal.esm. (No need to declare the variable)


So... when is Dayspassed NOT working or at least not reliable? Well, this happens with v1.3 - v1.6 when you HAVE Tribunal installed, but your mod IS NOT dependent on Tribunal.esm:

* If you don't declare the variable MW crashes or returns an left-eval error when you try to use it in the script (the Construction set accepts the script without problems)

* If you declare the variable in an ESP that is not dependent on Tribunal.esm, the script works but the Dayspassed-Variable that is used by your scripts will never be count up

* If you declare the variable in an ESM that is not dependent on Tribunal.esm, the Dayspassed-Variable from your mod is count up but the one used by Tribunal and Tribunal-dependent ESP's isn't.

* If another non-tribunal ESM declares the variable, and this other mod has a later file-date than your own, then your mod will share Tribunal's fate, and the Dayspassed variable used by your scripts will also cease to work.



This post has been edited by JOG: Jun 14 2005, 05:00 PM