Zugg Software :: View topic

Posted: Mon Apr 05, 2004 1:57 am

It seems to work fine if its just one line, however when multiple lines get gagged it concatinates the line to give the following output:

[City of Kaezar, Tempest Road at Avanil Way, Crossroads]Sitting in the shadow of the clock tower to the east, a large building occupies the entire side of the block. Extremely rutted from the carts and wagons that traffic to the northern, eastern, western and southern sections of Kaezar City, the road is a quagmire of mud and deep puddles.
Obvious Exits: south, west, north and east.

Where as normaly it would be:

[City of Kaezar, Tempest Road at Avanil Way, Crossroads]
Sitting in the shadow of the clock tower to the east, a large building occupies the entire side of the block. Extremely rutted from the carts and wagons that traffic to the northern, eastern, western and southern sections of Kaezar City, the road is a quagmire of mud and deep puddles.
Obvious Exits: south, west, north and east.
>

Here are my triggers that gag

#TRIGGER {^$} {#GAG}
#TRIGGER {~>} {#GAG} "" {prompt}
#TRIGGER {TICK IN} {#GAG}

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Remove the Newline option from the prompt GAG and see if that helps.
#TRIGGER {~>} {#GAG} "" {prompt|nocr}

Enchanter Joined: 10 Oct 2000 Posts: 656 Location: USA

On a side note, why don't you just turn off the notification of the "tick in x seconds" message on the timer so you don't have to gag this.

Posted: Tue Apr 06, 2004 7:16 pm

That one actually doesnt bother things, being as its like a gagged echo, the problem comes from gagging mud output... i use it as a work around for when i must wait to perform my next action.
The newline bit doesnt seem to matter one way or the other.. at least as far as i ca tell.

Posted: Tue Apr 27, 2004 4:08 pm

oh, the mud in question is Unwritten Legends
www.unwritten.net