Zugg Software :: View topic

Apprentice Joined: 01 Nov 2006 Posts: 114

Ok this is an output from my mud

Name (Drow Elf)(medium) stands in mid-air here. (paralyzed) (Red Aura)

I want it to read as
====== Paralyzed ======== Name (Drow Elf)(medium) stands in mid-air here. (paralyzed) (Red Aura)

I tried a sub command but it didn't work.

I tried something like this

#trigger (*) ((*)) ((*)) (*) here. (paralyzed) ((*)) {#sub ======= Paralyzed ========== %1 %2 %3 %4 here. (paralyzed) %5}

but it didn't work.

Posted: Thu Apr 24, 2008 2:13 am

~(paralyzed~)

#TR {((%w) ~(Drow Elf~)~(medium~) stands in mid-air here. ~(paralyzed~) ~(Red Aura~))} {#SUB {====<color red>Paralyzed</color>==== %1}}

Posted: Thu Apr 24, 2008 2:21 am

better still

#TR {~(paralyzed~)} {#GAG;#SAY {====Paralyzed=== %line}}

Posted: Thu Apr 24, 2008 6:48 am

Not to mention you needed to escape the parentheses. Shalimar, your second example won't work. First of all, I believe it would be %trigger, not %line, and second of all, it'd loop because the pattern is being displayed again. Heh. I'd write something that works, but I'm on my blackberry, so can't really help out there.

Charneus

Posted: Thu Apr 24, 2008 8:08 am

#SAY doesnt trigger i thought, or is that #SHOW?

Wizard Joined: 17 Jun 2006 Posts: 1201

Both do.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

#Say, #Show, And #Echo all fire a trigger.

%line2 should work %line wouldn't.

%trigger works.

If you play with the %line variables you could find one that works but %trigger is the better choice.

If you anchor the pattern at the beginning it won't repeat itself.

Posted: Thu Apr 24, 2008 4:20 pm

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

See, that's just the problem, when you start messing with sub/show/say the %line number often gets jacked.

I actually tried it out before I stated that. I've had experience with this in the past as well.

%trigger is better in this case because it just works regardless.

Posted: Thu Apr 24, 2008 7:52 pm

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Not that I know of sorry. As far as I can tell, currently if text shows on the screen and it isn't the timestamp.
Then that text affects triggers.

#oninput is needed for text that you entered that shows on the screen of course, but then that is a type of trigger.

#show displays in the default font as if it came from the mud.
#say/#echo have special colors associated with them.