Zugg Software :: View topic

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Rewriting over a trigger from the command line doesn't delete the conditions. 2 examples hard crash and bug report crash

Esc at char select into blank window

Hard crash example by rewriting and then adding conditional. In the command line type
#TRIGGER "test" {A:(%d)} {}
#COND {B:(%d)} {
#SAY (%1+%t1)
#SAY (%1+%int(%t1))}
#TRIGGER "test" {C:(%d)} {}
#COND {D:(%d)} {
#SAY (%1+%t1)
#SAY (%1+%int(%t1))}

Now in the settings editor click on the "test" trigger and select delete the orignal Cond (B:(%d)) is left clicking on this hard crashes Cmud

Soft Crash Example. In the command line type
#TRIGGER "test" {A:(%d)} {}
#COND {B:(%d)} {
#SAY (%1+%t1)
#SAY (%1+%int(%t1))}
#TRIGGER "test" {C:(%d)} {}

Now in the settings editor click on the "test" trigger and select delete the orignal Cond is left as a phantom, clicking on it crashes cmud to the bug report screen (bug report sent linking this post) you are able to continue cmud but you will keep getting errors in the settings editor

Expected result should be that rewriting over the trigger from the command line deletes all the conditionals that go with it, basicly recreating it from scratch

Posted: Mon Nov 27, 2006 7:37 pm

Well, rewriting a trigger isn't supposed to remove the conditions. It's just supposed to let you change the initial trigger pattern. At least that's what it does in zMUD. If you want to remove the trigger conditions, you need to use #UNTRIG to remove the trigger first.

However, I don't think #UNTRIG removes the conditions either, so I added that to the bug list. And, of course, it shouldn't cause the crashes that you are getting.