Just because im feeling good today

The algo of the code I inserted sometime ago -- This should solve your clotting problem




And also -- you can gag the clotting, bleeding in MUSH.. you can do it in
1. via code or
2. manually by going to MUSH triggers option (shift+ctrl+8), going to the trigger you want gagged, and checking "Omit from output".. presto, no more spam..




I dunno what this means, but if its about color you can configure the color settings in MUSH too (alt+8)

It's what I use it on.

You will need to emulate the trigger add/del/etc code for it to work. The only other thing I just had to change was the functions. The original code has functions as strings whereas I had to use pointers (or whatever the hell they're called).

So instead of
inserter = "PurgativeTrigger",
and the client somehow calling the function called PurgativeTrigger, I had to change it to
inserter = PurgativeTrigger,

It also meant it seemed to be happier if I stuck the tables down the bottom of the script, I assume so the function names are defined.

I'm not sure how you do something like:

** UPDATED 07/22/2008 **

by popular demand two fixes are added:

1. last announce of healing broke the system making it apply until you lose healing potion
2. added some nekotai lines...

please download latest file found at first page

btw: people do know there is a paid version of this system right? *cough*

-- And writing this just for reference ---
nezhmet.txt ( 239.61k ) Number of downloads: 265
README.txt ( 8.1k ) Number of downloads: 194
nezhmet_DOWNLOADTHISPLEASE.zip ( 42.38k ) Number of downloads: 43

then you obviously need to get kafe

Kafe has nothing to do with your health levels - it's a default in the system, whereby it checks if you have the kafe defence up (presumably by prompt) and tries to put it up if you don't. Not sure if you can turn it off.

You cannot turn it off (unless you change the code)
No k in the prompt means its time to eat kafe.

I have a question:
I didn't really like the highlighting of certain things so I deleted the color thing in the triggers, but they are still be highlighted?

Okay, I know Nezha's not promised any updates or scripting help. That's totally fine; he's already made a free script. Maybe someone else can help me out, though, if he won't.

I've usually got the PsyMet bonedensity skill up, which often keeps bones from being broken. Problem is, you get the initial "your arm is getting broken!!" affliction line, and then immediately following you get a "just kidding, your bones vibrate and your arm isn't really broken" unaffliction line. Right now, Nezha's system isn't built to catch that unaffliction, so I apply mending without needing to.

Would it be better to make a static trigger something like "the hardened bones of your (left|right) (arm|leg) begin to vibrate" and then have it run the UnSalveTrigger function, or to have the affliction line create this as a Temporary Trigger instead? (Incidentally, does bonedensity keep nose/chest from breaking too, or only limbs??)

Some scripting guru help me out here; what would be the most effective method?

Some ideas:

1. fastest way would be to insert "just kidding, your bones vibrate and your arm isn't really broken" in the deaffliction line.. youll might still apply mending but it will not do the retry and youll apply only once..

2. Or trigger the line where activate bonedensity, then in SAlveTrigger check if bonedensity is active, and if it is.. ignore the broken affliction

Thing with that is, it stll breaks from time to time, just not as often. It would need to somehow diag, or check to see ifthe limb is broken.

Double post, the one below is complete (this one wasn't).

Rename .lua to .txt (or just open it in notepad or a lua editor anyway). Or you can do this through the mushclient editor. Search for CrippledArm. It should look like this:


Add in, after "The bones in your (left|right) arm mend", another line (still inside brackets). If your above message is correct, it should then look like


Note the comma after the string.

Then just scroll down, add it into the CrippledLeg one as well (changing the message as necessary), save it, open up Mushclient (or recompile). You might need to run the daemon function again, too.

Things like this are part of the reason I created my "queue" system for storing afflictions temporarily before actually adding them on the prompt. You store afflictions in the queue rather than setting them as real afflictions right away. Before the next prompt, you still have a chance to alter the queue for things like BoneDensity or illusions or whatever.

Thanks for the help, all! For whatever reason, I'd not considered having multiple deaffliction lines.

Zarquan, what do you mean by a "queue" system for your afflictions? I'm not sure I understand how storing them temporarily and then adding them at prompt, after things like bonedensity or illusions would have sounded, is more effective than having a bonedensity line unset the affliction. What's better about your method?

If you have a broken arm already, then you get another broken arm (or the same one, which makes more sense) but bonedensity stops it, you don't want to remove the real broken arm aff that you haven't yet healed. Putting the affs into the temporary queue prevents you from removing anything you wanted to keep while still giving you opportunity to catch and remove the current one before the prompt curing fires.

1. I have a broken right arm, not healed because I don't have salve balance or whatever other reason.
2. Someone hits me and breaks my right arm. I add 'broken right arm' to my queue.
3. Bonedensity message tells me that I ignore the affliction, so I remove it from the queue.
4. On the prompt, I take anything from the queue and execute it (or turn it into a real affliction) before checking what to heal.

Replace step 3 with other things that happen after the fact, such as the 'perceive it as an illusion' sort of line.

If you don't use this sort of method, you get into the situation that Thorgal's original system used to, where you're removing afflictions you should be curing, primarily aeon or things that happen while aeoned.

For the record, this system does not work for monks due to the momentum system.

Yeah, free version wasn't updated, but the paid version was within 24 hours.

Unless you alter it to do so.

If only I knew regular expressions.