Okay. After getting some ideas, I think I might have thought of something. I'm making a backup curing system using DIAG, just incase something goes wrong with the Triggers I set up. I created a variable for all possible afflictions that you may have, and I want to sort them out by priority. I think I have a good idea of how to do this. I'm wanting to set it up like:



and you get the idea from there. Do you think it'll work?

-Ryld

Anyone? I just want to know if it works or not... and if it's not too much for Nexus to read.

erm, #blah doesant set it back in time i don't think i'll go check really quick, i'm working on setting a system for nexus to run for everything i'll get back to you

#blah? Where the heck do you see that? And it does work... well, I only cured one thing... heh. But it should work for many more

I understand what you are trying to do, but you are going about it in the wrong way.

Also, never use the #WAIT command ever... it pauses your entire system and causes all sorts of oddities. Use #ALARM instead if anything. Look it up in the help files for the proper syntax.

Which help file are you referring to? When I click the 'Get Nexus Help' button, I can't find #alarm, only #beep.

Aye. There's nothing there!

I agree, use #alarm.

And nominally, you want to reset your afflictions when you diagnose, outside of impales.

To prevent illusion problems, turn off the class, if possible and set a macro to turn the class on, diagnose, and then trigger an alarm to turn the class back off in X seconds.

Alarms work well for resetting failed cure attempts due to amnesia, stupidity, etc.

I.e, have the cure script attempt a herb cure and switch the herb cure balance to false, then set a labelled alarm to turn back on the herb cure balance in 1.5-2 seconds.

If the alarm is named, it will reset the alarm to 1.5-2 seconds if you eat again, to prevent wasted cure attempts.

At least, that's how I did it, and for the life of me I couldn't think of why it would be problematic.

Edit: Grammar.

Still, what the heck is #ALARM? I don't see it in the Help Nexus Thing.

It's a function in Zmud...

Have you considered an outside client? It would be a lot easier on you.

Oh damn, you were referring to nexus, hahah.

Yea, I wasn't quite in my right mind when I posted earlier, so don't mind me.

I still don't see why people use nexus though. An outside client like Zmud or MUSHClient will make your life thousands of times easier. I recommend Zmud over Mushclient, but it's 30 dollars whereas Mushclient is free. Still, if you buy credits, there is no reason to not buy Zmud, as it'll improve your performance far more than any credits would.

Heh. Well, here's the thing. I've tried out all of the others Clients, and I just happen to like Nexus. I've been playing Lusternia (and Achaea before it) with Nexus. I'm used to it, and everything else seems to be a little... too confusing for me to work. I like Nexus' simplicity... even if it doesn't have all the really cool features that zMUD and MUSHclient have... and I wish that it did!

Don't expect to build a good system if you wanna stick with Nexus.

I think your primary setback with using Nexus over MUSHclient or zMud is in processing power, rather than feature variety. I only use Nexus if I'm bashing while away from my computer, so I haven't tried this myself, but a few people have mentioned before that Nexus chokes to death really easily.

I have three seperate triggers that match my prompt in MUSH (although two of them aren't enabled most of the time) and I've never noticed any side effects. From what Shiri has said, trying to trigger something off your prompt with destroy Nexus.

Just for the record, MUSHclient is not free. It's shareware, and I recommend that anyone who uses it purchase it.

Well, I tried out that way (granted, it was only one affliction!) but it still worked. I'm gonna keep going with it, and see if it works on a grand scale. If it does, I'll be sure to post it up somewhere for all to see and check out!

How do you have your normal curing set up? If you'd done like most people you set a variable when you get hit with an affliction for instance...

The Trigger: Sticky strands of webbing spray out at you from....
Result: webwrithe=1

Then you have your main script that evaluates all your afflictions from writhing to toxins to everything else.

Thus, when you diagnose, you simply reset all your afflictions, and then set each "diagnose message" to it's applicable variable.

diagnose:
You have:
bound in ropes
paralyzed

So your system would do
ropewrithe=1
paralyzed=1

and then your main script would evaluate thereafter. That's assuming you've done your curing that way, otherwise you're gonna have a long long long diagnose trigger trying to evaluate everything... so your alarms or wait of 3000 would take literally minutes to finish.

I know. Well, here's the thing.

I set this Diagnosing curing for a backup, since some afflictions caused by Telepaths and the like give you like, 'You rub your temples because you now have a headache' or something like that. An affliction was put on you, but since I don't have a trigger that'll catch it and cure it, I'd have to make something that cures from Diagnosing. I already have that Trigger system set up, so this is just going to help out.

And yes, Riv, I am doing something very much like that. I heard that alarms are better than waits, but since alarms are for zMUD only (I believe. Not quite sure. Someone fill me in on that) I have to use waits.

I tried putting aliases into Nexus for each of the Star-Rays, much easier than typing ASTROCAST SIDIAK RAY AT at high speed, and after 10 aliases, it blew up in my face. Took hours to respond to anything, unless concussion gives you invisible aeon.

If you are gonna do waiting at all for Aeon, make sure you still track your afflictions coming in. Once the waiting period is over, fire salvequeu, herbqueu, so on and so forth. Just make sure the aeon is ACTUALLY gone.