Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

Did this ever get fixed?

Posted: Thu Aug 16, 2007 2:56 am

Not sure yet. Zugg is tackling several major bugs this week. He'll publish a list of changes and fixes when the next version 2.0 is released.

Posted: Thu Aug 16, 2007 10:05 am

The changelog is here. Just look through the list of versions since Zugg's post and you'll see that the answer is no.

Whether it's fixed in 2.0 is a different matter. Have to wait and see.

Wizard Joined: 17 Jun 2006 Posts: 1201

Okay I have another question...how should #sayp and #echop work?

For example, in one of Urit's posts he made a trigger like:

#regex {^\d+h, \d+m} {#sayp {Prompt}}

This output "Prompt" at the end of the line.

Well every time I use #sayp or #echop it pushes over the next line. I made a test trigger to #sayp TEST and this is what happens.

This is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TESTThis is a test trigger.
TEST

Am I not understanding it or what? I understand the bug yes, but I don't understand how this works. I want TEST to show up directly at the end of the trigger line like below.

This is a test trigger.TEST
This is a test trigger.TEST

???

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

The text your trigger matches on should be a prompt and not a newline, ideally. The test prompt trigger you've posted is a newline trigger, not a prompt trigger, so maybe that's the difference?

Wizard Joined: 17 Jun 2006 Posts: 1201

Wizard Joined: 17 Jun 2006 Posts: 1201

Yes you are right. I had my prompt trigger set for trigger on newline and it always fired every time. When I set it for prompt it skips a bunch, which of course is the point of this thread and the problem. Not to mention the reason I had it set to fire on new line. It works great that way so far? Not sure what else to do. It always captures the data fine.

Posted: Fri Aug 17, 2007 7:02 pm

This is quite an interesting problem. I was originally told it had to do with MCCP because the prompts were grouped, but disabling MCCP doesn't seem to make a difference. It's certainly the case that when a large number of prompts are received at once, the first two will trigger a "trigger on prompt" trigger and the ones in the middle will trigger a "trigger on newline" trigger, but when BOTH are checked, the first and last prompts fire the trigger twice, and the ones in the middle fire it once. Bizarre.

Here's something interesting though. I made a .raw file of the output, and it seems that even though there's no real difference between the actual lines sent, the "trigger on prompt" option only triggers on the last section if an in* - here's the relevant part (I'm just sending 10 invalid commands to the mud with #10):

Posted: Fri Aug 17, 2007 7:10 pm

Yes, the newline is added by CMUD when it processes the codes. The bug is that this doesn't call your prompt triggers. This bug is fixed in v2.0.

Posted: Fri Aug 17, 2007 7:34 pm

Hmm, actually, it's still not fixed. Could someone email me some debug log files for this? I need you to turn OFF MCCP compression. Then type:

#DEBUG eortest.txt eortest.raw

and then do whatever on your MUD to cause multiple prompts to appear that don't fire the prompt triggers. Then exit CMUD and send the two files as email attachments to sales@zuggsoft.com. This will give me more test cases to try with this. Thanks.

Posted: Fri Aug 17, 2007 8:23 pm

My smtp server is broken, so I uploaded the files instead.

txt
raw

Posted: Fri Aug 17, 2007 9:22 pm

Cool, thanks. That helped a lot. I think I've got it working now.

Magician Joined: 17 Apr 2005 Posts: 496

oldguy2: Just in my experience, #sayp and #echop are generally expected to start on a new line. The "prompt" feature (differentiates them from #say and #echo) is that there isn't a newline at the END of whatever text you send.

P.S. How about that #psub bug mentioned in same thread, this post?