I did not try to install it but I would suggest you do full uninstall including removing all packages you use, install the old version again, and then redownload and load your packages. If this process still does not work I have no idea what is wrong.

Second the system will not be stable at all under 2.25. There are multiple issues (cmud bugs) that screw things up. Do not use it under 2.25, spend your time either finding a way to go back to .18 or use a different system until a new version is released.

well I'm probably gonna end up spending credits on a system anyway.. because I've done verything you said twice.. and it still doesn't work, and so far no one's PMed with a different Zip file for 2.18 *shrug*

The system is nice when it works though, I'd admit that... I just can't get the proper version of Cmud to work on my comp...

From my end:
- didn't cure breakchest at the beginning
- didn't cure windpipe lock (I assume it was a lock, or at least slickness and windpipe)
- didn't cure windpipe in aeon
- didn't cure prone/broken leg/windpipe in aeon (could've been a hardlock, in which case you needed a power cure which you might not have)

CMUD 2.25 is actually more stable than 2.18 for most of us. There were multiple issues in versions prior that caused data corruption, however, and since this package was built on an older version of CMUD, you may well see problems just importing the .pkg on 2.25. I recommend someone export it to XML with 2.18 and then try importing that on 2.25 to build the package anew.

No. That is not the problem. And xml export and import does not fix it. There is a specific confirmed bug that is causing the issues.

Well, I know Zugg recently fixed a bug or two with expression triggers, which this system is based upon. So, either your workarounds for the bug (if any) are now undone or he's uncovered something new. May I ask what the bug is exactly? I don't recall any posts on the forums there that would line up with this issue here.

The problem is duplicate variables and cmud creating duplicate variables when it loses track of variables already in existence when a certain set of conditions exist. I'm not sure which issue you're speaking of it lining up with but pretty much everything described by those on 2.25 is linked back to duplicate variables and the system not knowing which one to read from or write to. It is easily replicated in fresh settings in 2.25 and the underlying bug carries through xml transfers. Appreciate the feedback but have a pretty solid handle on what needs doing with the system for 2.25. Thanks!

Ah. Okay. I've seen a few posts on the forums there about duplicate variables, yes. Personally, the only time I've had duplicate variables (and I don't use absolute paths to refer to anything) is when the variable is in another module that isn't "enabled" for the module that's setting the value. I've got a module just for persistence of certain variables and other modules need access to it or they end up making their own local copies of things.

I'm not saying there isn't a bug in CMUD because we all know there are several remaining, but maybe it's something that can be circumvented in the design of the code, too. Anyway, good luck with it! (Sucks when Zugg's either on vacation or burned out, and he's kinda both right now.)

Yeah, the fix for the system isn't dependent on the bug being fixed. It's just time consuming to change the code to not trigger the bug and to be careful in the future to not write the code in a way that will prompt the bug until it gets fixed.

Sadly it doesn't really have anything to do with modules enabled or disabled as it is primarily happening within the same modules. It's also a "new" bug. While duplicate variables popped up here and there in the past and were difficult to track down the cause, this is the first time it's been so rampant with clear steps to reproduce it. Hopefully it's a quick fix for him when he returns as it is a pretty major problem depending on how settings are created and moved around.

I've been running it on 2.25 with very little problem, apart from that caused by me being lazy setting everything up.

Seems like CMUD still has some issues. I've heard of issues with scripts written in v1.34 not working after v2.x Why are there all these random problems?!?

It's a system still somewhat in development. Sure, there's problems. There's also advantages.

Problems of compatility between versions is caused by two (somewhat related) thing: data corruption bugs where packages are rendered useless and script parser bugs that cause all sorts of odd side effects. Zugg has actually fixed a LOT of these in the last few versions (2.22+), so it may be worthwhile to start fresh on 2.25, if you have the time and know-how.

There are still bugs remaining, even ones that cause data corruption (as I've found by having to rebuild my two dozen packages about four times in the last week), and that stems from CMUD being many times more complex than zMUD and Zugg just gets burned out on all the issues he has to handle.

Zugg has reportedly fixed this duplicate variable problem as of version 2.26 so when that version is released, I will release the new package. I've been working with one of the users to try to see if I could get out a reliable 2.25 version but it's a no go and the version I'm creating on 2.25 won't work on 2.18 reliably for other people.

So anyway, big delay between versions I know. But a lot of fixes and reworked mechanics in the next version. Whenever it comes out...

When is 2.26 supposed to launch?

This week

Version 2.6 of the system is uploaded at www.catlss.com. It has all the bugs that have been reported these past two months fixed and will work on CMUD 2.26 (which I recommend downloading as so far it's proving to be more stable than 2.18 is).

This version does include the new collapse nerve affliction from blademasters. Any issues please e-mail at coboarder@comcast.net as I'm not certain how often I'll be checking this thread in then next couple of days.

No idea if this happened to anyone else or not but when I first upgraded nothing was working right. The affect in my case was all of the "Try" variables seeming to not work. So for example if I would sip a health pot, before I regained balance I would try to sip again. This was because the system thought I had health balance back because the "Try" variable was being detected as unset (the "try" stuff is part of the way the system handles things like insanity, and it in general rocks).

I thought there might be a duplicate var issue as it behaved identically to that kind of situation. My debugging made it clear though that there were no obvious duplicates. So I unloaded each package to narrow things down until I found the issue was with my base settings. I deleted a few of them at a time until things started working.

My theory for why deleting some settings worked is because CMUD uses an internal hash to find the "real" variable. As there was a bug with this in earlier versions I suspected that some of the variables in Catarin's system were in fact getting hashed to my own personal variables. By deleting and recreating them this fixed the hash collision and things worked again.

I have no real proof of this beyond a gut feeling, and I can not recreate the original situation.

If you are having problems though you might give it a try. I would suggest creating a new package and moving your classes over to it one by one. Then keep loading Catarin's package and your new package until it stops working. Once you find the group of settings start recreating the variables first, and then move on to other settings if that does not work.

Hope this helps. The system is working flawlessly now for me.

The easier way to recreate your session package in the new version of CMUD is to export it to XML, delete the .pkg, and import the XML back into the newly created package. (There's some sort of XML import bug in 2.26 now, though, so you might want to wait for 2.27 before trying this method.) And, always remember to backup your settings regularly!

2.27 is out! I'd recommend updating as 2.26 had a couple of pretty major bugs in it. Also, I have released version 2.7 of the system. It has the following updates:

Version 2.7 - Released 6/13/2008

*Revamped queues so they work properly every time, yes, even the herb/elixir queues
*Revamped the rebounding script to be more advanced and reliable
*Added in an auto defenses module! Look at the in system help files (cathelp) to learn how to use it
*Corrected a bug with regeneration cures not working (silly unannounced syntax changes)

Obviously the big thing there is the defenses. Read "cathelp autodefenses" in the system and see how to use it. Then come back and read the rest of this.

Currently the defenses available in the system are limited to the ones I have easy access to seeing. Of course you can add your own custom defenses but if you don't feel like doing that yourself or you're feeling generous for other users, you can submit them to me to put in. As the help file says do the following to get defenses added:

E-mail Catarin at coboarder@comcast.net and request the defense to be added into the next version.

You will need to include the following in the e-mail:

Defense Name
Skillset
Pattern when the defense is put up
Pattern for the defense in the output you get when you type "def"
Pattern when the defense goes down (if applicable)
What action you use to put the defense back up (i.e. evoke netzach)
What queue the defense would be in (balance/eq, needs balance/eq but doesn't take it, herb, elixir, salve, id, sub, super, or none).

Enjoy and as always e-mail me with bugs or problems.