Zugg Software :: View topic

Apprentice Joined: 08 Apr 2004 Posts: 103 Location: USA

I upgraded my CMUD from 2.27 to 3.32. When I got to using it.. I found it had made all my variables from default being chosen to temporary..
After spending an hour fixing all that.. I closed out cmud and came back to it later. Now everything but my class folders is deleted. Is there anyway
to fix another one of cmuds crappy screw ups?

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

Are you sure they are deleted? 2.37 was full of tons of bugs, a disturbingly large amount of them related to package corruption and/or the results thereof (ie, seemingly-deleted settings). It might be the case that your stuff is still all there and just the database connections that kept track of it all were affected, in which case you will find out one way or another by using the XML export process:

1)open up your session in Offline mode, turn Parsing and Triggers off (you do NOT want anything helpfully calling scripts you're about to temporarily get rid of as this will cause CMud to crash or at least will create new settings that will just get in the way), open up the Package Editor
2)click the tab of the package you're wanting to Export
3)click on the File|Export all to XML menu
4)close all windows found in this package
5)back in the Package Editor, right-click on the package tab and choose the Remove Tab option (the goal here is to completely obliterate all traces of the package file from your session so that the next few steps can be accomplished)

NOTE: here is where optional and inconvenient technical stuff might need to be done
a)open up the XML file
b)review the XML looking for wrongly-created stuff (ie, duplicate locations, missing or previously-deleted triggers/aliases/etc, that sort of thing)
c)if it's obvious that your settings are no longer there, perhaps try opening the package file with a real DB manager or possibly in notepad. At this point, you might want to just not bother and simply recreate your scripts from scratch because the ONLY thing you can do here is manually copy and paste probably-incomplete bits and pieces of your scripts. Even if you can save most of the data, you will have to manually recreate every class, trigger, alias, etc so you have something to paste into.

6)find and delete the package file on your computer (the XML file has all the stuff that's in this probably-broken file)
7)back in the Package Editor, create a new package (now that the old one's gone, you can just use the same name without having to modify your scripts)
8)with this new package tab selected, choose the File|Import XML menu option or otherwise continue on with manual recreation of scripts.
9)review your scripts to make sure everything imported properly (there are a few instances where things will not import correctly)
10)save

Wizard Joined: 22 Mar 2007 Posts: 2320

Actually, the most likely reason for everything to appear to disappear is if you accidentally changed what types of objects are shown. I forget exactly which menu it is in, but one of the menus has a Show option, with which you can specify what types of objects are shown. Make sure that is set to All.

Apprentice Joined: 08 Apr 2004 Posts: 103 Location: USA

Did what you said Mat, no luck.
All that's left is Class filders, buttons, and statbar even though the package is still 1.6 megabytes big.

Rahab, I'd already checked that. Thanks though.

Apprentice Joined: 08 Apr 2004 Posts: 103 Location: USA

This is twice now CMUD has ate my system. Is the 2.0 to 3.0 not compatible or something? I really think you should look into this. I play on a mud called "Aetolia" and I know I'm not the only one having this problem.

Posted: Thu Dec 02, 2010 6:40 pm

Actually, nobody else has reported this problem. If you did what Matt said, then post your XML file here so we can look and see what might be messed up in it.

Posted: Fri Dec 03, 2010 8:44 pm

Are you seeing any other anomalous behavior with your computer? Have you tried using some of the back ups to see if there are still good? Version 2.0 had some package storage issues, so if you converted some of those may still linger. If you exported/reimported or rebuilt from scratch, your package should be fine.

Also check to make sure you didn't inadvertently access a search filter. In the worst case PM and so I can get a copy of the 'aberrant' package and take a look at it.