Zugg Software :: View topic - [2.16] Script debugger still running when turned off

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

A picture is worth a thousand words

It's not showing normal mud output anymore, but it is still showing the results of triggers that contain a #SAY or #SHOW
(Notice also the weird amount of colour codes, but that's already been posted in a separate topic)

Posted: Tue Dec 11, 2007 6:01 pm

Looks like it's just a problem with the 'g' message. I'll add this to the bug list.

Posted: Tue Dec 11, 2007 7:11 pm

Actually, I cannot reproduce this. Can you try this again and expand the Elysium box in the tree on the left so that I can see if you have any other enabled classes. Also, I need to see the exact trigger that you are using that is causing this. The 'g' message is only supposed to be used by the #CW or #SUB commands to show a changed line, so it shouldn't be called by #SAY or #SHOW.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

There weren't any subclasses enabled, I made sure I checked that. Not sure why I said it had a #SAY, I'll look back when I get home, but the trigger is
#TRIGGER {{@whoList}} {#CW gold}