Zugg Software :: Search

I have many different variables with different names and put them into different folders, so I can check them easily.

But after a while I noticed that some of those variables (only 1 or 2 of them) ...

Thanks Zugg. I copied my scripts and deleted all the other files under Cmud folder, and re-installed again. That has fixed the problem.

If it happened again, I'll try your suggestion. Hope not, :P~ ...

I'm using Cmud 3.31 pro.

I was trying to close Cmud, and then a Cmud error message panel poped out. I chose "continue this application". Then I closed the Cmud again.

After a while, I start Cmud ...

Looks like you're using slow walk method, swith it to speed walk.

In my Zmud 7.21, I was using a lot of expression triggers, which gave me lots of hard time.

Now in Cmud all of these wierd things have been fixed, and the multi-thread looks so good. So should I us ...

Thanks a lot!

Just switched to Cmud. If I'm using a command method like:

#TRIG {} ...
#COND {} ...

Yes, I can make a multi-line triggers without problems.

But what if I wanna create this by using the sett ...

Thanks for the 25 views and no reply....

I have tried this in Cmud and it works just as I thought. Those triggers only fire once.

Now i guess it's time for me to move to Cmud....

Yeah, now what I'm doing is: I use path = %pathexpand(%walk(room)) to get the path, then in my room name and exit trigger, I add these:

#TRIG {(*) -}
#COND {The exits are (*)}
{
#TAG NAME ...

what's the difference between pro and regular? SSH surport?

No, that's not the case.

I check the Zmud history log, and it has this bug:

Aborting a Slow walk no longer causes direction to be sent twice when using #OK

which has been claimed to be fixed ...

It is said this bug has been fixed since Version 6.54 15-Mar-03 (BETA version), go ahead check the log:

www.zuggsoft.com/zmud/version.htm

But now I'm using Zmud 7.21, and I tried the f ...

Thanks for reply. The situation here is: I'm going from B to C, but failed, because I have to kill the monster. So it should be #STOP instead of #PAUSE.

And I also tried #PAUSE, as you said, the ne ...

Maybe a little bit more details:

I overided the exit line because the "autoconfigure" doesn't work properly, so here is what I wrote:

#TRIG {here the exit:(%s)$} {#TAG EXIT %1; #CW high,green; ...

I've been using Zmud and Cmud for a while. When I'm trying to use mapper I got a problem:

Say A->B->C there is a monster in room B and you have to kill it to goto C. This is very easy if I ...