Going to start serious work on my system. I already have (unperfected, but usable) system for writhing and paralysis. I don't get fooled by multiple webs, etc.

However, I have NO afflictions, really, yet. I have logs, tons of logs, just haven't really decided to develop a system. Off tomorrow, so I'll use a few hours to try my hand at it.

First things first: aeon.
Then: sleep (also, a special aeon+sleep). I intend never to be off kafe or insomnia, but just in case.
Then: anorexia.
Then: paralysis.
Then: impatience.
Then: asthma.
Then: stupidity.

Then: herb cure afflictions.
Then: elixir cure afflictions.
Then: salve cure afflictions.
Then: coltsfoot cure afflictions.
Then: rebounding aura.
Then: healing (health, mana, ego/ elixirs and sparkleberry).
Then: defenses.

Anything I'm missing? Also, I intend on there being two primary classes (one of which will be shut off if I'm aeoned or asleep, and turn back on if neither: the actual 'curing' class; the other is the passive logging class).

Finally, the fun part: illusions. Don't think it'll be as difficult as I originally thought.

Oh, and forgot: knights (wounds, etc.)

Edit: forgot some.

I've got some anti-illusion, but I know I can do better.

Some other fun things are the oddities in the cures themselves.

If you're afflicted with something and smoke coltsfoot to cure it, you'll more than likely strip your insomnia first (it is, after all, an affliction). You don't want to get into an infinite loop of smoke/insomnia, right?

Also, if you've got sixth sense up and someone strips it from you, you have to know now that you're blind and deaf and probably no way to see and hear. Eat faeleaf three times instead of just once (no herb balance on it yet, either, the way it seems).

I plan to work on the wounds thing next, personally.

doublepost

I have my anti-aeon and sleeping triggers mapped out, and a basic cure bit mapped out, and finally figured out how to do anti-illusion . (the fact that no Illusionists can dsl or dstab helps that a bit).

Make a super serenguard system someone, and I'll buy it from you. I know how to use them, no idea how to make them. The most basic systems principles are occasionally lost on me.

My system's a Serenguard system, but not sure what you mean by "super serenguard system" exactly. Curing is generic enough, for the most part. Offense is something tailored by and for each individual, isn't it?

I tried making my own system, but after a while I got bored of trying to find out all the lines for afflictions and other stuff.

I have tons of lines, just need to actually code them into a healing system.

Pass them here, please .

There's too many swordmaster and bonecrusher messages to make any system simple. I did something that used the deepwounds diag to decide on healing but it's taken too much time for something that doesn't work too well. My healing balance works brilliantly.

I thought I had web and paralysis figured but spiders in Glomdoring send it loopy for some reason.

For writhing and sleeping, i have multiple states for asleep/waking and bound/writhing to avoid multiple afflictions, it seems to work except for the damn spiders.

Anti-illusions is a distant ambition - I need to do a course in ZMUD.

I spent a journey up to Newcastle going through my logs. The battery ran out before I was 1/2 way through them. I need more than a day off.

I sorta agree with you about the blademaster/bonecrusher affliction messages. It's not the fact that there are so many of them, though. It's the inserting of the name of the person and the type of the weapon that throw off the lengths of the lines that make it hard to trigger. You need to broaden your regular expression for multiple forms or else shorten the text you trigger on and risk catching something else by mistake. Another problem is that some of the messages for these afflictions will use the wrong pronoun or leave the sentence hanging on a connecting verb.

The anti-illusion isn't impossible, but can be tricky. It's always a fun challenge to see what someone tries to illusion and then work your way around it for next time.

Hmm, is there an easy way to trigger for possible new line wraps without using $ for every possibility?

If you know some small part of a message is always going to appear on a particular line (sometimes close to the beginning and sometimes closer to the end), you could do well to use a multistate trigger for the small phrases.

For example, one attack from different people using different weapons:





(Not the best example of this, but a functional one, at least...)

How does the #COND thing work? Is it embedded in the #TRIGGER command or is it separate? I have pasted in a load of multi-state triggers I wrote using examples similar to yours and the #COND commands are not recognised.

The #COND command only works when it follows a #TRIGGER command. Each condition adds a new state to the trigger, so the #TRIGGER is the first state. All of the states can have any valid trigger type, which means you can mix and match things to get some really neat effects.

Another simple example: say you wanted to have a prompt trigger that makes you stand up, but no more than once every second. You could make a prompt trigger to check and see if you're prone and disable itself with a second state that simply waits for one second. (Note: this is not the most efficient way, but simply an example of multi-state triggers.)



When the prompt fires the triggers, the trigger will disable state 0 and enable state 1. State 1 will stay enabled for 1000 milliseconds, as per its properties, and disable itself. Since there is no state 2, the trigger will then reset and enable state 0 again.

You can find lots of useful examples and details in the zMUD help files and on the Zuggsoft forums.