Zugg Software :: View topic

Posted: Thu May 26, 2005 11:36 pm

Alright, i am trying to gag out the output, but when it comes on consecutive lines it gets some odd output

This is my trigger:

This is the trigger I am using:

#TRIGGER {<rt>(%d)</rt>} {#GAG;#VAR rt {%1}}

This is the output with the trigger off:

Round Time: 3 seconds.
<rt>3</rt>
<rt>2</rt>
<rt>1</rt>
<rt>0</rt>

And the output with the trigger on:

Round Time: 3 seconds.
><rt>2</rt>
<rt>0</rt>

It only seems to catch it every other line, and it seems to get worse with more consecutive #GAGs

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

triggers with <> cant be inputtet properly like that from the command line...

entered as show the patteren was: rt(%d)/rt
the <> got stripped

after i edited to: #TRIGGER {~<rt>(%d)~</rt>} {#GAG;rt = %1}

and did:
#SHOW Round Time: 5 seconds. ;#SHOW ~<rt>5~<~/rt> ;#SHOW ~<rt>4~<~/rt> ;#SHOW ~<rt>3~<~/rt> ;#SHOW ~<rt>2~<~/rt> ;#SHOW ~<rt>1~<~/rt> ;#SHOW ~<rt>0~<~/rt> ;#SHOW ~<rt>999~<~/rt>

it worked as expected, i saw: Round Time: 6 seconds.
all else was gagged and rt=999.

Posted: Fri May 27, 2005 12:34 am

Yes, Gag works for my fine in other muds, but specifically this issue seems to only happen on this mud. I am unssure what differance would affect the behaviour of GAG, but it is there.

If you wanna see for yourself

www.unwritten.net 6666

Posted: Sat May 28, 2005 7:07 pm

Zugg, or someone else who might be able to figure this out, I would really apprechiate someone looking into this.

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

I went ahead and tested it while connected, so this definitely works on my end. Just to give you a rundown on what it does, it assigns the value between the tags (<rt>9</rt>) to the @RoundTime variable, the same as if you did it via #VARIABLE or the a=b syntax. Then it gags the entire line seamlessly so you don't have to worry about cluttering up your settings file with lots of slow #GAG triggers.

#mxp <!element rt TAG=20 FLAG='set roundtime' OPEN>
#mxp <!tag 20 GAG ENABLE>

Now, I'm not entirely sure if you really need the OPEN for the element command, but that should get you working properly (it does for me, at least).

Some of the spec wasn't all that clear in the element/entity/tag section, in that most of it seemed designed for the MUD sending these two commands and ZMud automatically handling them. Perhaps it should be noted in the helpfile that to create the tags manually the user needs to use BOTH of them to get things working right?

Posted: Sat May 28, 2005 10:31 pm

well, it does manage to gag them all, but its still doing something funky

close eyes
You close your eyes.
open eyes
You open your eyes.
Round Time: 1 second.

close eyes
You close your eyes.
open eyes
You open your eyes.
Round Time: 1 second.

that dead space shouldn't be there between them

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

I'll leave you to refine, but go ahead and use this trigger:

#trigger {^$} {#gag}

Posted: Sun May 29, 2005 10:10 pm

I have a varient of {^%s$} in my settings but currently disabled, it doesnt affect the output here.

whatever the issue i have had this gag issue for well over a year, this is the third thread i have started over it

i play several other muds and have no issue gagging there, its a mud specific issue i just cant figure out

Posted: Sat Jun 04, 2005 6:17 pm

Bumping cause I am still having issues with this

Posted: Sat Jun 04, 2005 6:50 pm

Aha, the coders found the internal problem that was affecting this, or so it seems as my gag issues of over a year are now gone.

GM says "I added some detection for CRLFs, which may have improved performance if your client expected CRLF."