Zugg Software :: View topic

Newbie Joined: 20 Feb 2011 Posts: 1

Okay. I have an awful cMUD problem, and I'm at the end of my rope. I should start by mentioning I'm running cMUD 3.33a, Microsoft Windows XP (SP3).

I've troubleshooted this problem with 3-4 other people, most of which are very knowledgeable of cMUD, and they're all as baffled as I am, so I'm at the mercy of the Zuggsoft forums now.

So, prefacing my question with that (I'm not a coder type), I'm having an issue that I can't resolve for the life of me. For lack of a better term, cMUD is misbehaving on some scripts that have worked perfectly fine in the past, and work perfectly fine for other people.

It's impacting multiple scripts across the board, and all of them seem to have to do with the same few variables just not getting "picked up". Random stuff like things not subbing (and therefore not communicating with the rest of the system) are also happening.

1. I've completely uninstalled cMUD from my computer, deleted the cMUD folders in C:/ and My Documents/My Games, and run ccleaner to ensure everything is really "gone."
2. I've tried checking for the problem on two versions of cMUD (3.31 and 3.33a), and both have the issue. I have the issue on my work computer, as well.
3. I've run cMUD without any other settings beyond the curing package (i.e. no other settings could be interfering at this point) and no other settings adjusted minus the word wrap ones I need in order for the package to work.
4. I've imported three different versions of the same settings package (including one from November-ish and one from a friend who runs the same settings).
5. I've tried exporting/importing, and importing as XML.

The problem seemingly just popped up out of nowhere. I'm running packages/settings that are months old, with new errors. I just can't, for the life of me, understand how that happens. I'm using a settings package which works perfectly fine for three other people, but somehow breaks in my hands.

If anyone has any ideas (I'm just about open to anything at this point), pleeeease come forward.

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

Regarding #5, did you create a new package file or just reimport into your existing one? A broken package file that has XML dumped into it will still be broken. You need to delete the original package file, create a new one, and then import it. If you happen to be familiar with the XML you may also find it a good idea to look at it in notepad, looking for stuff that's not formated correctly, missing stuff, or otherwise is recognized as something that should not be there.

Another thing to be aware of is that packages are not the only points of corruption. The layout, the CMud config file, the map database file, and the sessions database, these can all become corrupted. Sometimes even the file that SEEMS to be the broken one, actually isn't. If you are going to do things like #5, take the time to apply it to every single thing you have associated with that session. If you don't, not only could you possibly not fix the problem but it might eventually spread to otherwise fine files.

Once you are reasonably sure it's not corruption or some standard (if obscure) difference in Preferences/mud settings, you can look at the scripts being employed on each system. This will require what will seem like over-the-top levels of detail, but we literally can't effectively help you if you continue writing posts like this one.

Wizard Joined: 22 Mar 2007 Posts: 2320

One other thing to consider is: do you have multiple triggers which manipulate the same variables? Do you use #WAIT or similar commands in any of those triggers? It is possible that you are getting thread collision--multiple triggers trying to work on the same variables at the same time.