Sometimes Acropolis just seems to stop recognizing affliction messages and it uses more than one cure if there is more than one cure. I don't know if it's due to the weird lag I've been getting or if it's a flaw of zmud or the system. Also, anyone else have this problem? It's not always like this. Just occasionally and a reset doesn't seem to help. Thanks.

Some affliction messages have changed, and I believe Larkin didn't update the new messages.

It's not that. They were firing earlier in the spar and stopped later. Course, there was weird lag going on too. And I've changed the affliction messages that I know about unless more have changed in like the last week or so.

Its just not working out for me, I think mine needs uber updating. I don't know where to start...

Yes how you update? I try update bashing part but is not working What I do is put new message and imitate what is done from other script and put as it is cure by diagnose or other thing that cure it

let me see if I remember right.

#trigger {triggerline} {i_aff affliction}

random example:

#trigger {A giant red scorpion jabs his stinger into your body and you burst into flame\!$} {i_aff ablaze}


you might have to do a search for i_aff to figure out what it is that you need to put, but that's the general idea

OKay thanks that's one but when I make new for bashing, I look at other similar script and this I add but it not fire.

#REGEX {^Moving with astounding speed\, a gargantuan ishkynd worm slings his body around} {}
#COND {your legs and squeezes them as hard as he can\. You can hear your bones snap as the} {within|param=1|regex}
#COND {pressure becomes higher and higher\.$} {i_symptommend leg 2} {within|param=1|prompt|regex}

Bashing is on. Those I copy from something similar.

What is wrong please?

No
do this

i_queue i_aff <affliction>

So
(you have to use regex with those assertions)
#REGEX {^A giant red scorpion jabs his stinger into your body and you burst into flame\!$} {i_queue i_aff ablaze}

Edit: Updating acropolis isn't that hard. It's just that for today's standards, it's a sub-standard system. It's good for bashing, and -some- fighting, but against heavy afflicters, unless you diagnose every 5 seconds, it's not so good.

Okay. I get lost in queue things. What is easy structure for make heal queue with easy updating? I look at other tutorial and see many if things then I get dizzy. And to person with knowledge, how do I fix above the bashing thing I post?

It's impossible for me for buy credits OOC and no Vadi because I want learn. I still try and thanks for inputs.

Find the screenwidth 0 version and use that.

To clarify: Making multiline triggers work properly as with a system you don't understand completely is difficult. If you can find the screenwidth 0 version, you don't have to deal with multiline.

Thanks! I think I understand some some. But what is advantage of those screen width things? If screenwidth 0, I don't have to to \n or that #COND thing?

I appreciate help! It makes tweak fun even if I understand only little bit.

Also how is screen width 0 different when it was made? I mean in making it what makes it different? Is there script?

CONFIG SCREENWIDTH 80 or 0.

Refer to Sena's explanation in the other thread.

but what if multiple afflictions? like i am shiver, maybe frozen, and random limbs broken?

#REGEX {^A giant red scorpion jabs his stinger into your body and you burst into flame\!$} {i_queue i_aff ablaze}

Like I said, it's a sub-standard system.

Nobody updates it anymore, and it's been so long since I've looked at it that I couldn't give you a sure-fire answer.

There are two separate issues that you mentioned:

1) I found that I needed to select trigger on trigger for all the triggers or they would randomly stop working until Z/CMud was restarted.

2) The double curing is because it was pre-adding of logic to track what was cured earlier in the code. You can add in a variable to keep track of that and check against that variable before curing it again.