I did a simple trigger to do "#say home" on the roomname of one of my manses rooms and it doesn't work, set on trigger on newline and trigger on trigger, and I'm sure it's enabled

I had to make an alias 5 times.. make it, try it, doesn't work, rinse repeat, until some fluke of time and space came together and it worked. My timeout trigger which is simply

You will timeout

look

Just sits there looking at me like it doesn't understand english.

Nobody mentions one awful thing I notice. I don't know if I did something wrong, or all you guys just have fast computers, but it's incredibly, incredibly slow. I mainly mean text output.

I haven't noticed a speed issue, but then I can't get any setting to work so maybe that is why. zmud runs real fast when you have no settings too.

it's normal speed to me, but triggers aren't working at all, and I already send 10+ bugs doing with settings and his docking.

I'm talking text output without any triggers.

ok I found why aliases didn't work, aliases only work in the default package for me. no triggers though

Somethign to try, is to see if you need to save packages, and reload them?

This new version compiles, so maybe check to see if it is indeed compiling?

not sure.

Aliases worked for me, triggers don't work at all (not even a basic trigger I made specifically for testing purposes). Also, #say and #echo have a bug where if you use a . in them anywhere they go KABOOM! As well as not being able to actually submit the bug report when it pops up that window (the "continue" button never ungrays).

ok i got triggers to work by just putting #trigger {stuff} {stuff} in the mud input which sucks because you can't use declared variables in triggers then.

Oh and remember this is just to play with... it's not meant to work perfectly. He'll deal with all the bugs come July after his vacation.

type in your email adress and it will ungrey.

Hm, once upon a time, betas had their user interface done and were just buggy or missing a few minor features. From what I've seen, this isn't the case with the CMud beta.

EDIT: Oh, and it's perfectly justifiable that it's slow. Optimisation should always come last.

Actually, it's not that slow when I don't import my old settings. When I do, it's errors all the time.

From my go at it, and reading the zmud forums it sounds like this is more of a Public Alpha than a beta.

Proabbly going to have to wait till July to get something useable.

For instance, we can't even make get nice button layouts and make GUIs or anything that zmud is really famous for. And you have to make all your triggers and aliases in the command prompt.

IMO best only to get CMUD if you want extra time trying to learn how to optimize your own coding ability. (or if you like helping Zugg and stuff)


Also, CMUD only works on XP and later, 2K is a no go.

It crashes whenever I try to boot it up... Mreh.

CMUD definitely has its problems right now. It's just a beta version, though, and you should remember that if you downloaded it to look at it already that you did have to agree to the beta testing thing. If you don't want to test it and report bugs in detail, then you really shouldn't have purchased it and/or installed it yet.

Many of the problems with people not being able to get triggers/aliases working are a direct result of the new scripting engine and how it's parsing things. A lot of your old code won't work, even some of the simple stuff, because the new compiler is a lot more strict with the syntax.

The system has a lot of potential and there are many more changes under the surface that you may not see when you just look at the pretty interface. It's just unfortunate the Zugg was feeling the financial crunch and starting to get burned out and so decided to release it before further private testing and fixing. This is a rude awakening for him and a real downer for many users. I hope you don't judge it too harshly on these first impressions because this client is not yet finished.

Worst thing about it that I find is how it handles buttons. Nothing sucks more than having your actual screen for lusternia somehow stuck at the BOTTOM of your nice GUI and not being able to play at all.