For Zmud, I do. I've never tried to script in the Nexus client.

In Zmud, I would create an afflictions list variable @afflictions.

A affliction add alias using #alias add {afflictions=%1|@afflictions}

A affliction delete alias using #alias del {#delitem afflictions %1}

After that, the trigger messages for diagnose would add their specific affliction, like:

#trigger {ablaze.} {add burning}
#trigger {(whatever the burning cure messages are.)} {del burning}

After that stuff, it's all about priority curing using the afflictions list variable.

That bit took me the most time, and I still have to figure out what order to cure in, but ordering things requires more thought than it requires scripting time.

Hope that helps a bit.

Psh, i'm only calling you out because you're posting like you're a good combatant when indeed you are not.

Back on topic however, one way to make a priority curing is a whole bunch of if statements. IE

#IF (@anorexia = 0 AND @slitthroat = 0 AND @stunned = 0 AND @asleep = 0 AND @herbbalance = 1 AND @throatlock = 0) {#IF (@slickness = 1) {calamus} {#IF (@stupidity = 1) {pennyroyal} {#IF (@recklessness = 1) {horehound}}}}

That's merely an example, you would have to put in a few other bits and pieces to ensure it doesn't spam itself while waiting for the command to go through etc etc. One big extened if statement isn't such a bad way of doing things. It's not slow by any means

Murphy,

What do you think about a system like this.

#if @slickness=1 {eat="outr calamus;eat calamus"}
#if @reckless=1 {eat="outr horehound;eat horehound"}
#if {@anorexia=0 & @sleep=0 & @sap=0 & @aeon=0 & @HS_balance=1} {@eat;HS_balance=1;#alarm "HS_balance" +1.5 {HS_balance=0}}

Instead of the nested IF's it resets the @eat variable, with the afflictions lower on the list taking precedence.

The only thing thats holding me back with systems is a auto sipper belive it or not

ANYONE WHO EXPLAINE TO ME HOW A Sipper great appreicate

>>>>side note trying to do one in Mudmaster .2k6.. I like mud master

so ether going have to figure out how to do one in game or make a mud bot to doit
I had one mud bot working at one time but
now i forgot how to add scripts to it to make it work

REal novice coder but i try ..Lua easyest and the mudmaster

useing mushclient right now mushclient still confuseing to me any help be great

I've seen some epic Necro's, but this is way up there.

Haha I was reading through the thread then I paused a second to get my bearings before looking at the date.

I use a string list to set priority, then loop through it and implement a switch statement within that loop for every applicable affliction and related cure. I like this method because I can change priority on the fly by simply switching that stringlist's order.

A switch statement is really a better option, for a couple of reasons. First, it looks a lot cleaner than nested if statements, which makes debugging and altering easier. Second, it stops executing when it finds a match, which reduces the time it takes to process afflictions.

Plus, It's a bit simpler than what you're trying to do, if I'm gathering what it is you want.

Nested if else statements would also stop processing when you got a match, rather than just a long list of ifs.

True, but that's why I stated that it's cleaner and easier to edit than nested ifs. The other comment was in regards to the suggested idea (a whole bunch of ifs that set a variable).

YOU ARE BOTH RESPONDING TO PEOPLE WHO POSTED THREE YEARS AGO!!!!111!1!1!!!11111

I am tempted to move this to the Quotes.

You're right, I'm sure Murglokh and Murphy will appreciate your system building tips when you get in the Delorian, fix the flux capacitor and join Doc Brown for another adventurous caper through space and time... HELLO? MCFLY?!

There are a few examples around. The main thing is to track your balances and parse the prompt, which has your current health etc.

If one of the three gets below a certain level and you have balance, sip away, lose balance and wait until it says you can drink more bromide or whatever.

Some people have a preset set-point where they sip, some use a percentage and have you set you max. Mine uses percentage and parses the output of QSC. It works ok, except when there is a lot of lag, in which case the watchdog timers fire and I sip twice I might try to track lag to fix the timers one time.

Urgh.

Start a new thread.