Zugg Software :: View topic

Newbie Joined: 04 Nov 2006 Posts: 3

Ok I just installed cmud last night and was able to convert my old .mud with minimal problem. However I am having one problem with my gags. All of my transferred gags work fine in mud output. However I have several command echos gagged which don't seem to work with cmud. I don't wish to turn off command echo completely but more common commands such as drinking macros I don't wish to see. The gag even for this macro spam is triggering in output, as in if I actually 'say buy liqueur', but not when entered as a command. Any ideas what I'm doing wrong?

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

I don't think so, I have noticed some odities with the #gag command as well.

Posted: Sat Nov 04, 2006 6:01 pm

Actually, I'm not aware of any problems with #GAG, so if anyone is having problems, you need to post the exact trigger and the exact text from the MUD that is supposed to fire the trigger. My guess is that you have a trigger or alias with a syntax error somewhere that isn't running correctly.

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

If you try to gag text that is sent from the command line it will not work unless you are using a trigger of the type command input.
This is a good thing. Unexpected perhaps but a good thing.

But once you set the trigger to command input and put a #gag for the value it will remove the entered text, but leave a blank line where the text used to be.

To get the expected results you need to put #gag 1 instead of #gag.

Now, if you use a macro you can forget it working at all. Yes if you were going to gag text sent from a macro you should have just used the gag IN the macro.
But, the reason it is not working is the %lastinput variable does not get incremented when you send commands to the mud via a macro.

I can understand that MAYBE that is somehow what you would want to happen, but if it was we would need another variable that holds just the commands actually sent to the mud.
We have that %lastcom.
But I don't think it would be a good idea to make an expression trigger that tests to see if %lastcom = whatever to gag that line....

Anyway that's my two cents. I been waiting a while to post this as other more important things needed fixing

Posted: Sat Nov 04, 2006 6:06 pm

OK, I think I understand. Actually, Macros don't currently use the command input or %lastcom stuff, and this should be fixed soon. So then you should be able to use the same command input method. But I'll take a look at the extra line issue.

Newbie Joined: 04 Nov 2006 Posts: 3

Just wanted to reply a thank you to Arminas. I changed the type to command input and it worked fine.

Thanks

Wanderer Joined: 09 Nov 2006 Posts: 55

I'm getting one odd #gag problem
I tried to gag some text with {#gag 2} for 2 lines, when the trigger fires, it creates a trigger for 2 {#gag}
is it just me? I deleted and re-gagged the text and the same thing, anything with 2 in it gets gagged...
I sometimes see a trigger appear for 1 too, but no value in the trigger so I just delete it

Posted: Wed Nov 22, 2006 8:06 pm

Show me the exact trigger definition you are using. I just created a trigger and put

#gag 2

into the script for the trigger and it worked fine. CMUD evaluates the argument for gag, and if it's a number, then it gags multiple lines. If it's not a number, then it uses that for a pattern to create a new trigger. So somehow CMUD doesn't think that your 2 is not a number, and I don't know how that's possible.

Wanderer Joined: 09 Nov 2006 Posts: 55

I tested it just now on 1.16

#tr {gag test} {#gag 2}

#say gag test

and now theres a trigger with pattern 2,
the value in the editor is just #gag

I tried that #say with a few lines of garble and it only gags 1 line as well as creates a trigger {2} {gag} i dont know how or why?

Could a corrupted pkg somehow affect that? you have the corrupted pkg I emailed once. I just converted that corrupted package to a published module and it otherwise works alright. oh, Except the compatibility report freezes and runs 100% processor at about 89% complete...

Posted: Sat Nov 25, 2006 6:37 pm

Posted: Sat Nov 25, 2006 8:27 pm

I suppose this is as good a place to ask as any...

#gag gags the last line in the buffer. #gag -1 gags the line before it (and smaller numbers gag however many lines before the last one). #gag 2 gags it and the next line in the buffer. Is there any way to gag the last line in the buffer and the line (or x lines) before it? The only way I can think to do this at the moment is #gag -1;#gag or #gag;#gag. Is there no neater way to go about this?