Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

Would be difficult to replicate this. But the story goes as follows:

I make a trigger. I save it with a name. I edit said trigger. I change trigger's name. I edit trigger further. I save trigger. I test trigger out. I close the window. I connect to a different session with a package that is linked across sessions. Trigger is now gone. I go back to the session I was connected to before, Trigger is still gone.

Has anyone had this happen before?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Have you tested the trigger pattern to see if the trigger is simply hidden? In the myriad forms that corruption can manifest, one of the most frustrating ones is where a setting works correctly but which does not show up in the expected place in the Package Editor. This "hiddeness" can be a completely invisible thing, or it can be such that the trigger only becomes visible in the All tab rather than in the specific package tab that you created it in.

Another situation wherein a setting could disappear is in the case of two separate instances of CMud involving shared packages between multiple sessions. If I recall, this is the more stable version of multiplay in the 2.37 public version. With each session having the autosaver turned on by default, it is possible for CMudSession1 that has the trigger you created to save its data first and then CMudSession2 that does NOT have the trigger to save its data. The only fix here is to turn off autosaving and recreate the trigger--it is permanently gone, but more importantly it was deleted in a proper, working-as-intended way.

Finally, there's the situation where your OS has write-protection on important application folders. If your datafiles are in these folders, CMud will not be able to save any changes at all to them due to OS interference. You will have to uninstall and reinstall CMud, and then manually move your data over to the proper location.

Posted: Sun Mar 21, 2010 4:25 am

From what I recall, there were also some bugs in v2.37 related to possible setting loss in shared packages that was fixed a while ago in the Beta versions. You could look through the Version History to find out more.

Wizard Joined: 26 Mar 2008 Posts: 1547

Thanks Zugg and Matt. I have a feeling it is covered under one of the two things you guys mentioned, I'm leaning towards setting loss though as that seems to make the most sense. Though it could easily have been me screwing something up. Either way, it would seem that if it was the issue that Zugg mentioned, then it's well on its way to being fixed. I ended up re-doing the trigger, not a huge deal, but I wanted to see if the issue was a known one.