 |
Moo
Apprentice
Joined: 10 Apr 2009
Posts: 145
|
 Posted: Sun Jul 26, 2009 8:38 pm
Loop Lines and #echo
|
| Quote: |
*Loop Lines
The parameter will be shown to sets the number of lines to test this trigger. The trigger will be tested each time a line is received from the MUD until the specified number of lines have arrived |
It seems to also test lines that are added using #echo.. Is this the intent? |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4790
Location: Pensacola, FL, USA
|
Posted: Sun Jul 26, 2009 8:58 pm
|
Hmm... echo is normally processed by triggers, so it may be...
have you tried using #PRINT instead, it will not fire triggers. |
|
|
|
|
Moo
Apprentice
Joined: 10 Apr 2009
Posts: 145
|
Posted: Sun Jul 26, 2009 9:31 pm
|
Ahh.. Interesting..
Yep #print doesn't seem to trigger it..
Perhaps the documentation for either #echo, or the loop lines, should be amended to mention this.. Probably the #echo, if it triggers anything that looks at "MUD output", which I wouldn't have expected local display to be counted as..
Thanks  |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Sun Jul 26, 2009 10:34 pm
|
This is intentional, and also the reason why #PRINT was created. There's nothing that really needs to be amended. :P
Charneus |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4790
Location: Pensacola, FL, USA
|
Posted: Mon Jul 27, 2009 12:06 am
|
I think the help documents should be amended.
#SHOW and #ECHO both say they are related to #SAY but the favor is not returned, and #PRINT is out all by its lonesome. |
|
|
|
|
Moo
Apprentice
Joined: 10 Apr 2009
Posts: 145
|
Posted: Sat Aug 29, 2009 12:12 pm
|
Is it the intention that lines #PRINTed are affected by gags?
If so, why? |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sat Aug 29, 2009 4:31 pm
|
Yes, #PRINT lines are still effected by gags. There is no way to avoid this. CMUD can prevent the text from #PRINT from firing a trigger, but it when #GAG tries to remove lines once they are already on the screen, there is no way for #GAG to know which lines were from #PRINT and which lines were from other methods. So this won't change.
The reason the documentation isn't fully linked yet is that #PRINT was introduced in the 3.x beta version and the documentation isn't normally fully updated for beta versions. I clean up the documentation right before a public release. Any documentation that you see on Beta features before a public release was created by the Gurus as a public service. |
|
|
|
|
Moo
Apprentice
Joined: 10 Apr 2009
Posts: 145
|
Posted: Sun Aug 30, 2009 12:13 am
|
Hmm well.. My problem was that I was doing for instance #gag 10, and triggers that were firing during the gagged lines did #print, which didn't appear, but used up the gag lines..
If it's in the middle of a "#gag x" type thing, it wouldn't need to be removing lines that are already there.. Or would it?
Even if it can't avoid hiding the line, it could realize that the line that was just displayed was from #print, and not change the gag counter.. |
|
|
|
|
|
|
|
