Zugg Software :: View topic - [205] Deleting Triggers

Newbie Joined: 29 Aug 2005 Posts: 5

Deleting triggers or anything else for that matter ends up deleting much more than you wanted it to. I used the sample from the database.
#TRIGGER {Name: &Item.Name Type: &ItemType} {} identify
#TRIGGER {Cost: &Item.Cost} {} identify
#TRIGGER {Weight: &Item.Weight} {} identify
#TRIGGER {Damage: &Item.Damage} {} identify
#TRIGGER {Hit: &Item.Hit} {} identify
#TRIGGER {Dam: &Item.Dam} {} identify
#TRIGGER {$} {#T- identify;#IF (!%null(@NewItem)) {#NEW @ItemType @Item}} identify

I then tried to delete the one about the weight and the the previous two I editted were deleted. I tried to delete the rest, but then the whole Identify class was gone.

Posted: Thu Oct 11, 2007 9:07 pm

What exactly did you press to do this? Give the entire list of steps you took, as specifically as you can. Using an rclick menu is different to using a keyboard shortcut, too.

Newbie Joined: 29 Aug 2005 Posts: 5

I opened up the editor, under triggers i pasted the following
pattern: asldjfsldfj
scriptpart: a;dfkljas;ldkjf

and then i made a few more jibberish triggers. I left clicked to select one in the tree and rclick to delete setting. It took out all the triggers.

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

Confirmed, something is screwy.
Make a bunch of jibberish triggers and then delete them using the right mouse click menu and you'll lose more than 1 trigger at a time

Posted: Fri Oct 12, 2007 2:03 am

Wow, that's a really nasty one. That's brand new in 2.05 I think...I normally delete triggers all the time and didn't think this was possible, but I confirmed it in 2.05. Not sure what changed to cause this mess, but I'll definitely get it fixed before the 2.06 release. Thanks for the report.