Zugg Software :: View topic - CMUD Closing -- not even an error message

Newbie Joined: 24 Apr 2007 Posts: 7

Using the package window I created a class X inside class Y which was inside my Avalon package.
Next, I clicked on that new subclass - X - to make sure it was selected.
Then using the command line I typed #CLASS Y|X to make sure I would be creating triggers in the correct class.
Using the command line, I created a trigger with the following command:
#TRIG {at Start of mountain road.} {#CW @color5}

The results were as follows:
A new class was created at the same level as my Avalon package. That class has the name "at Start of mountain road". It apparently contains a trigger, since when I filter for triggers I see a + sign next to this class. Anytime I click on the class, cMud closes.

Of course, I had done about an hour's work previous to this and would like to not lose it if possible. I can avoid the problem by not clicking on the class, but that is obviously not acceptable for the long-term.

I've tried various ways of referencing it and deleting it from the command line. But, they all result in cMud closing.

Any help would be GREATLY appreciated.

Posted: Wed Apr 25, 2007 12:18 am

Which version of CMUD are you using?

Sounds like you've managed to quite severely corrupt your package. I can't reproduce the error following those steps you've given - make sure you post every single click you did and word you typed.

Newbie Joined: 24 Apr 2007 Posts: 7

Using version 1.29
And to the best of my knowledge that's exactly what I did. Of course, it could have been something prior to this that began the corruption process.

I guess I'm just wondering if there's going to be a way to fix this....or if I should just take the loss and move on?

Posted: Wed Apr 25, 2007 12:45 am

Well, you didn't explain every step - did you click "save" between creating the class and moving to the CMUD window? Did you close the editor or just click the CMUD window? Did you create the class long before you created the bugging trigger?

Zugg normally has people email corrupted packages with bugs that can't be easily reproduced to support@zuggsoft.com. It's possible that he'll find a fix, but for now there's little else you can do.

Newbie Joined: 24 Apr 2007 Posts: 7

I didn't save, I didn't close the editor. I only did what I said in the original post. And it was all done sequentially as stated.

I'd love to send in the package. I'm also willing to just scrap any recent changes.....I realize when using the beta, some strange things are probably going to happen.

Weird things happen quite often in this package, so I probably have more issues than just this...coming from zmud and all the way through the betas.