Zugg Software :: View topic

Adept Joined: 24 Aug 2004 Posts: 277

Is there a way to accurately gag a line that MAY or MAY NOT line wrap?

Depending on the monsters name, some lines will have 1 line, some will have 2 lines, but I always want to gag the entire line.

Is there a decent way to accomplish this?

Posted: Fri Nov 01, 2013 9:40 pm

i use something like this...

Adept Joined: 24 Aug 2004 Posts: 277

So I changed the "part you always see" with the common text I'm trying to gag, but it doesn't gag the remaining line wrapped text.

I even tried changing the ^(%w) with ^(*). (basically waiting for a period to end the line, because the monsters name is at the end of the text)

Your fingers glow red as you reach out and drain mental energy from
the text that line wraps.

Your fingers glow red as you reach out and drain mental energy from creature.

that is an example with/without line wrapping of this one specific example, I do have others with completely different text.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

That's what multistate triggers are for.

#trigger "tMentalDrain" {^Your fingers glow red as you reach out and drain mental energy from(*)$} {#if (%ends(%1,".")) {#state tMentalDrain 0};#gagspace}
#condition {^*.$} {#gagspace} {WithinLines|param=1}

Adept Joined: 24 Aug 2004 Posts: 277

Thank you MattLofton, but it still doesn't work fully, I'll explain:

Sometimes this command happens twice in succession, your trigger will block the first line, the line wrapped line, it will let the 3rd line go through(the triggered part) but it will block the 4th line (the 2nd line wrap.

So instead of seeing:

Your fingers glow red as you reach out and drain mental energy from the
monster you are fighting.
Your fingers glow red as you reach out and drain mental energy from the
monster you are fighting.

what I am seeing is

Your fingers glow red as you reach out and drain mental energy from the

So, why is it completely skipping one of the lines? It could potentially be the first and it's gagging the last 3? But I figured that made less sense than it gagging 1, 2 and 4 and letting 3 go through?

Posted: Sun Nov 03, 2013 4:06 pm

My example was a multistate trigger, it was just the XML for it instead of zScriipt

if you happen to get an example that went to three lines, the middle line would not get captured in Matt's because of the period
and there is no error checking (testing that the first word is all lowercase) to ensure that its not a stand alone line

does your game indent the wrapped line? because if so we need to account for the whitespace between the line start and the first word:

^%s(%w)

Adept Joined: 24 Aug 2004 Posts: 277

No, there is no indentation on the 2nd line. All 4 lines of output are on 4 lines, 1 after the other without any type of prompt > or spaces.

Adept Joined: 24 Aug 2004 Posts: 277

I ~THINK~ I may have figured it out.. I used ~. instead of . in the parameter line and it's seems to work flawlessly...

Thanks very much... I'll let you know if it fails. I really appreciate your guys' help!

Adept Joined: 24 Aug 2004 Posts: 277

I spoke too soon.. it failed again..

It's weird, because now when it fails, whatever comes after the gagged text will be completely omitted for a random amount of times... in this case it's gagging my mud attacks and letting the gagged text go through, so I'm getting my hpbar, shouts, tells, guild communication(basically everything) except my mud hits which coincidentally come right after what's triggered...

Strangest thing..

Uh...... I just checked my triggers, and suddenly there are 183 instances of :

<trigger param="1">
<pattern>^*.$</pattern>
<value>#gagspace</value>
</trigger>

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

That would be something you were tampering with. Neither of the triggers we gave you would ever create new triggers. My guess is that you created one trigger using the #TRIGGER part of the code, and then in the script code for that you put the #CONDITION command.

Adept Joined: 24 Aug 2004 Posts: 277

actually I made the entire thing through the editor using new trigger then posted it into script text and edited it... fishing that was the wrong thing to do..

I'll check it tomorrow... sorry and thanks

Adept Joined: 24 Aug 2004 Posts: 277

It's working. That copy/paste worked just fine.

Thanks so much guys!