Zugg Software :: View topic - [3.03a / 2.37] I loose triggers, aliases, variables, etc...

Posted: Wed Mar 04, 2009 12:13 am

That is one thing I was about to mention, the possibility of the record NOT being deleted, but corrupted or given a incorrect pointer so it doesn't reflect in CMUD properly, or something along those lines.

I'll be glad to send you the .pkg file as soon as I get home tonight, which will be at about 7:30 pm your time.

Charneus

Posted: Wed Mar 04, 2009 3:46 am

Email package finally. Bah to customers who spend an hour over quitting time to open up accounts. :\

Charneus

Posted: Wed Mar 04, 2009 5:12 pm

I got the file. But no, the missing setting wasn't in the file. I found these two:

Posted: Wed Mar 04, 2009 10:19 pm

I do have a second package opened, aside from the English packages and clickable urls. I have checked the second package to see if it's there, but it isn't. I'd imagine, unless the trigger was hidden with an invalid pointer, it'd still fire, but it doesn't. So that concerns me (as I'm sure it does you) that a trigger created and in effect for 6 hours can just disappear like that, even after #SAVE. When I get home tonight, I'm going to play around with CMUD. I've got my settings backed up, and now since you have my package, I will see if I can create a situation where I can reliably recreate the problem for you. Then I'll post the procedure and see if you can reproduce it using my package, and hopefully you'll see what's happening behind the scenes.

Other than that, maybe this problem will disappear with the bug fix for the duplicate settings and reappearing deleted settings. That's sad, though. Seems like CMUD is latching onto settings we delete, but rejecting new ones. :p

Charneus

Posted: Thu Mar 05, 2009 3:59 pm

Ok. Was able to continuously replicate the bug on my end, so I hope that with my package, you'll be able to do the same, though really, it shouldn't matter with packages, anyway.

1. In Package Editor, select "New->Class" and create a new class.
2. Select the new class, then go "New->Alias" and make up some random alias.
3. Repeat step 2 for variable and trigger.
4. Go to the command line (don't close out package editor. Not sure if this has any affect, but it could) and type #SAVE.
5. Close out CMUD by pressing the nice red X in the window.
6. Reopen - the settings should be gone, or possibly moved to root folder instead. If you don't see this yet, try repeating steps 1-3, then clicking refresh.

Hopefully, this works for you and we're able to get to the bottom of this. Maybe it's with the autosave/#SAVE command, since you added the saving on a regular basis. Only reason I suggest that is because I still think there should have been no way for me to lose that trigger after 6 hours with #SAVE.

Charneus

Posted: Thu Mar 05, 2009 6:18 pm

Nope, I wasn't able to reproduce it with that procedure. Maybe I don't have all of the files that I need. I had to create a fresh layout file for it.

Basically, I saved the PKG file that you sent me as Charneus.pkg. I ran CMUD and created a new Session called Charneus, then exited CMUD and moved the Charneus.pkg file that you sent me into the CMUD/Charneus sub-directory. Then I ran CMUD, held down the SHIFT Key and clicked the Open Offline option.

This gave me 3 windows: maps, Chat, and Aardwolf.

I then went into the settings editor and tried your procedure. I created a class called "aaa", then an alias called "a1", then a variable called "a2", and then a trigger called "a3". Did #SAVE and clicked the red X to close CMUD. Then restarted and everything was there.

You might try this exact procedure yourself so we can determine what is different with it. Maybe your specific layout file is needed, or maybe it's something related to your mapper database, or with some other package files. But keep working on this.

I did the testing with v3.03 to try and reproduce the problem first, so it's not related to anything I have already fixed in 3.04.

If I can get a way to reproduce this before Friday, then I might be able to find a way to fix it. But I'm not going to delay the Friday release any longer. I'll try to check this thread later tonight and see if you have come up with anything else. Thanks for the help.

Posted: Fri Mar 06, 2009 3:19 am

I'll wait until the new version comes out. If it still does the same for the new version, then I'll send you everything I have, my layout, maps, and any packages open, and see if you can reproduce it that way.

The only other thing I can imagine is if you're doing this not connected to a MUD (mine, as you probably know, is Aardwolf), then that might be why you can't reproduce it. I've never tried it without being connected, but I don't think it should ever have a bearing on packages and whatnot.

By the way, try to connect to Aardwolf - I'm getting several strange symbols with autoconnect, and it forces me to reconnect several times before it starts. Want to see if you get the same error. Don't have to, not imperative, but would be nice to know it's not just me.

Charneus

Wanderer Joined: 02 Sep 2005 Posts: 85

It was me too other day, I forget how I triggered it.. I think I still can reproduce on the other comp, as that one is still bugged (freezes when it opens up) I dont use that comp a lot to begin with, so I'll see if I can use it later. :)

Posted: Fri Mar 06, 2009 5:55 pm

I think we talked about this in another thread. I think it depends on if you are doing anything in your OnLoad or OnConnect events that might be sending text to the MUD before the MUD Compression protocol is properly negotiated. I haven't seen anything like that in my Aardwolf playing here in the past several days, so I can't reproduce it. If the problem goes away when you turn off the MCCP emulation option in the Preferences, then look to see what your OnLoad or OnConnect events are doing in the script debugger.