Zugg Software :: View topic - [2.11] Expression trig behaviour, possible link to default var bug

Posted: Mon Nov 12, 2007 8:56 am

I have posted to Vijilantes thread on default value variables not being initialised .. well, ever. Just briefly though, my test consisted of choosing one of the muds from the character selection screen that I do not play, to be sure to get a blank session file.

I created a new package from there, called 'bugtest'. In that package I created a class called "test" and in that class I created two variables (@eqbal and @armb) with the default values of eb and lr respectively. I made sure to check 'use default value".

Then, upon closing CMUD and starting up (or just closing session and connecting again), I found both variables to have been given null values, rather than the default values I set.

Right. So upon reporting that bug to the relevant thread (Vigilantes) I then set about testing an expression trigger. I created an expression trig:
#TR (@eqbal=eb && @armb=lr) {#SH balanced}
Then, from the command line, set the variables to different values, and then back to the values that will make this trigger fire. This worked correctly. I then saved (both with file>save from the package editor menu, and with #save at the command line), closed the session and reconnected, and discovered that the expression trigger I had created did not exist. I repeated this 4 times to make sure it was not an anomaly, and it failed to save all four times.

I tried closing CMUD completely instead of closing the session, and this time the setting saved. A separate bug (or somehow linked? I will investigate more, meh. For now.. back to the expression trig bug at hand.

Upon finally managing to connect and have my expression trigger actually in existence, I set the null values of those two variables to their correct default values, then changed them to something else random... and back to their correct default values (all from the command line, I should specify).

Upon doing this.. the expression trigger did not fire. I felt close to having replicated the bug, so I opened up the debugger, opened up the package editor, changed the vars away and back again, waited for about 20 seconds, then clicked on that XML tab - and nothing happened.

I cannot get this expression trigger to work at all now.

Posted: Mon Nov 12, 2007 9:11 am

Sorry for yet another post.. but I installed 2.11 again (to a different HD partition, actually) and before copying any package files over to the new installation, I connected to materia magica, created a new package, a new class, a new variable with a default value. Saved, restarted CMUD, connected to Materia Magica again, and found the variable to have a null value.

I then opened the debugger, and closed the session with it still open, then connected again. Just in case that is somehow useful.
Sorry if this is an overload of test info, it just seems that everything I do that is somehow linked to these variables doesn't work right, and it only seems worse in 2.11 so I want to make sure I do enough testing :S