Well, I'm interested in making a system in mush client since my Zmud lags the outa me.. Anyway I have some specific questions on how to code certain things, I'm asking here since someone who knows it well could save me a TON of time sifting through all the crap they've writtin on it..

I am asking specifically how to change Zmud code to Lua:

#var balance {1} {1}

#trigger {^You have recovered balance on all limbs.} {balance=1}

#trigger {^(*) kicks you} {#if %1=@target {stand}}

#alias herbchecker {#if (@aeon=0 and @herbbalance=1) {eat yarrow} {sip sanguine}}

#trigger {that pipe is already lit} {#ga;#sa ----PIPELIT----}

Guess that's all for now, might add some later.
Thanks in advance!

what is lua....

just stick with zmud and speed your system up by reducing triggers.

Lua is a nifty scripting language that can be embedded into a program, so that it doesn't require WSH to execute scripts. I used Lua in MUSHclient for a while, and I found it to be overall pretty good. One of the major benefits of having it embedded is that you can run it under Wine rather nicely. It's also a tiny bit faster than other languages because of its tight integration.

MUSHclient is many times faster than zMUD, though it lacks all the GUI features and a useable mapper. You can optimize your zMUD code to a certain point, but it will still be slower than the equivalent system in MUSHclient. Coding for MUSHclient is considerably harder, especially for the novice or non-programmer.

Zarquan I know you know the answers.. *urge* I don't code, but I think I am fairly adept at learning, so really I just could use a little help to start making top from bottom of all these help files...

I'm sure that if I had the time and energy to work with MUSHclient again, I could translate for you. The thing is that not all of them translate so easily, and MUSHclient is difficult to teach, in my opinion. You're best off browsing the MUSHclient forums, reading the Lua docs, and just experimenting with code to learn the ins and outs.

Ew.... I just wanna know what "y" means that they put in all those triggers really... That's always confused me a lot.

What "y" exactly? I know there are a few options that are saved in the XML that can have a "y" for yes and an "n" for no.

Oh I see, that's what I wanted to know.. if it was a variable or somethin like yes or no
Okay heres a yes or no question.. Can you put the triggers in LUA or do you hve to do em in mushclient's triggers, I also am curious about the same question for aliases.

You have to create the triggers in MUSHclient or in a plugin, and then tie them into your Lua code, either by calling functions in a file or by putting the code right in the trigger value. All of the triggers I had for my system, I coded by hand in XML plugins.