Zugg Software :: Search

The hard disk itself should still be under warranty though. I'd look up the serial number on the manufacturer's website and see if I could send it in for a new one.

Also, how come every time i export my settings as xml and then load it to a default/blank session and save it as a package it's kb worth is less than my previous .pkg file that i exported that xml fro ...

#if (@lefthand != "none")
{
#wait 3200
put @lefthand in hun sack
}

Apologies, I was a little tired when I made the post.
I have corrected the original post by adding '"F1()"' to the correct spot in the test alias.
I have also changed the {""} in the #print command ...

Basically if you call a function that contains an alias using '#call @{"Function()"}' everything within the called function will execute Except any aliases.
In fact I found this bug because I was con ...

Just use the other one. \\\\

All marking the do not enter box does is put a very large number into the room cost box. Wink

Well, if you could give us some examples of the ones that do NOT work, a picture or preferably some code or both maybe someone can help more.

Numwords does have an option to count multiple spaces as a single space now.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<alias name="test" ...

Sounds like your DirectionsDiag class is missing, changed, or disabled.

You mean like maybe how <?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<alias name="Test" copy="yes">
<value>#show {1 ...

Not that I can find, or remember.

It's amazing that I recalled the #QUEUE command.

[[#QUEUE]] Should do what you want.

Experiencing the same behavior with 3.22 both sets of tests were with pro.

Yes I am using a blank session.

Confirmed, but very strange.

If you add the obligatory, to me at least, #noinput to the first line of the oninput trigger it doesn't happen.

It took me a few times running through the steps in m ...

Actually, it used to fail for me sometimes.

IF I recall correctly I made a macro that printed to the screen my aliases would start working again if I hit that macro.
I'm certain that I wrote a bug ...

About the best way you are going to be able to handle that is to actually name your triggers.

Then make a function that either turns on or off the trigger based on its name. Something like the foll ...

Probably so.
You will just need to send them an email asking, all they can do is say no, and they might say yes.

Personally I suggest upgrading to CMud anyway.

Just give the alarm a name. Then use #untrig name.

#ALA testa {5:00} {#show {Fired.}} altest
// Creates an alarm named testa that will fire every 5 minutes with ...

Here is the script altered for testing.
To try it out simply paste it into an empty session and type wintest <xvalue>.

So if you wanted to see the default that he has here of 6 type wintest ...

It looks like then that your @exitdir variable could contain a null value. Before the send command try adding #delitem exitdir "".
#delitem exitdir ""
#send %item(@exitdir, %random( ...

#SHOW %format("&.0n",1000)
#SHOW %format("&.0n",13000)

It is there in the documentation. It just isn't that plain in the example given.

It sounds like you have done one of two things.

1. You accidentally entered a mud specific command to change your prompt.
2. You accidentally created a #substitute trigger that is replacing your p ...

#call is the fast one.
#noop re-compiles each time it is run.

Since this is Zmud we kinda frown on most usages of #wait. But I believe it should work fine here.

#forall {w|w|s|s|s|w|w|w|n|n|w|touch triangle} {#send {%i}}
#wait 10000
#forall {w|w|nw} {#send ...