Zugg Software :: View topic - CMUD: No longer able to edit session packages, yet the existing still work...

Novice Joined: 15 Jul 2010 Posts: 39 Location: USA

I am running CMUD version 2.37

I had lots of random CMUD crashes, that I found to be isues with some of the package settings in CMUD. I delted all my custom packages, are created new ones from scratch which stopped the CMUD crashes.

However, after working happily for about 2 weeks, CMUD will no longer let me edit any settings. I can connect to a session, see all my buttons and status guage just fine, and after numerous tests, I can say with fair certainty that every trigger I wrote still exists and is functioning normally.

The problem is that when I open say the 'Triggers' button, I get the usual window, I can't do anything. At the top I see my 'UNIVERSAL' package that I wrote to contain items for every session, as well as an individual character package. I click the magnifying glass on the left to show 'all' settings, and all I get is an empty grey window. No folder tree, no settings to edit. The rest of the window seems fine. I can remove tabs (packages) and add them to the session, and they appear properly on the main CMUD window, but the editor remains a blank grey box where the settings should be.

I don't understand how all the settings are fully functional within CMUD, but the editor comes up blank. I reinstalled CMUD over itself to see if the editor files had somehow corrupted, but that does not appear to be the case.

ok... well i resolved the issue while I was posting, but perhaps this might help someone in the same boat later on, I opened the 'view' menu in the editor and selected 'restore default layout' and everything went back to normal.

Not sure why this occured as I didn't change the layout...

Beginner Joined: 15 Jul 2010 Posts: 12

I have this problem too!! I am on 3.22 beta.

It is sporadic - the Package Editor will - without pattern or predictablity - open up but not display the menu tree, or any of the settings, classes, triggers etc. I've tried closing and opening the window. There are only 2 solutions I have found. One is to shut down the entire application and restart - not practical if you have a session running. The second is to leave the Editor closed for anything from 10 seconds to 10 minutes and re-open. Then you have access to all the settings again.

Restore default layout fix didn't work for me.

Please please help! It is a paralyzing bug!

Wizard Joined: 22 Mar 2007 Posts: 2320

Vortis, what probably happened is that your layout got corrupted somehow.

Markb, don't know what the problem is. You probably should post to the Beta forum, since this appears to be a different problem than Vortis had.

Novice Joined: 15 Jul 2010 Posts: 39 Location: USA

I think most my original problems came from using the #WAIT command, which I recently learned causes lots of havoc in zMUD/CMUD

for instance, Her is the code in a button I was using during times of my character being afk:

Ping=1
#WHILE @Ping=1 {
prayer
emote looks to be afk.
#WA 60000
}

I've recently learned about the #alarm command and have been trying to understand how it works so I can stop using the #WAIT command and replace it, but I am pretty sure i'm not doing it right just by looking at the pattern's behavior.

I re-wrote the button as such, can you tell me if I am close to getting it to perform with the same behavior as the original script?

Ping=1
#WHILE @Ping=1 {
prayer
emote looks to be afk.
#ALARM {+600} {
prayer
emote looks to be afk
}
}

Posted: Thu Jul 15, 2010 4:34 pm

In the Package Editor, select the View/Restore Default Layout menu command to see if that helps.

If that doesn't help, then your package might be corrupted. Try doing a File/Export XML to write your scripts to a *.xml file. Then close your session, use the Edit Session action to edit your session and click on the Package Files tab. In the field for your primary package file name, enter a new name of a file that doesn't exist yet. Now connect to the session Offline to allow CMUD to create your new blank package. Now go back to the Package Editor and use File/Import XML to read in the *.xml file that you saved in the first step. That will recreate your settings in a fresh package file which should fix any corruption.

Regarding #WAIT, I don't see anything wrong with your use of #WAIT assuming that "prayer" and "emote" are both just MUD commands and not CMUD aliases. The only problem with #WAIT is if you write to global variables, which you don't. So your command looks fine and if it causes trouble in the latest Beta version, then you should post a detailed bug report over in the Beta Forum describing what problems your #WAIT script is causing.