Zugg Software :: View topic

Posted: Thu Sep 24, 2009 11:50 pm

Today I loaded my MUD session as usual and when I went into the settings editor to modify a setting I found that there is no functioning editor. I get a screen that does not contain any settings. No settings tree no panel where the settings content would go, nothing. I do get all the buttons on top, and on the left side. I get the tabs with the package names, and that is it. I thought that if I tried to add a new settings the Editor would respond with some attempt to restore itself. What I got was nothing. Thinking that CMUD terminated last time in an indeterminate state, I uninstalled it and then re-installed it. That made no difference. What's even worse is that now I can't even connecdt to my mud because when it loads it, it loads some garbage package. In view of this, I went and looked at the package using an SQL display tool. The package looks fine AFAIK, though I if there is some information on it that is causing this problem, I am not able to tell. Bottom line is this, when I re-started CMUD and loaded my mud settings, I got a mix of different settiings so that the session is useless. The only way now I can log on to the mud is by renaming the main package and opening the session with a blank one. This means that all my work is gone, 2 years' worth. Oh, before it is suggested, using a backup package doesn' work, because the problem is not the package, the problem is how CMUD is loading them. If I had a Settings Edtior maybe I could fix it, but since I no longer have a Settings Editor, that's not an option.

EDIT: One major flaw in CMUD is the assumption that a package must be loaded and activated if one wants to modify it. A package should be loaded by the Settings Editor for the purpose of editing it and nothing else. This would allow fixing of packages in situations where corruption is suspected. I already encountered this problem when I tried to create a fresh package for my session. The only way to do that is to rename the old package and open the session forcing a new package for the session. While there might be reasons to do it this way, removing this dependency will pay off in the long run. At this time, I cannot salvage my package because I cannot open it safely to copy over into a new packatge the uncorrupted portions. If I open the package, its garbage becomes part of the session. now this is not the main reason for the post, but this problem was caused by the problem that I posted.

EDIT: I just re-installed 3.09B. The Settings Editor works fine in this version.

Posted: Fri Sep 25, 2009 12:57 pm

In the View menu of the Settings editor there is an option to reset the editor layout back to the default. That will fix it.