Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
saet
Apprentice


Joined: 12 Jun 2006
Posts: 106

PostPosted: Sat Sep 23, 2006 4:58 am   

[1.07] Trigger Types
 
If you have a trigger set to something other than a pattern and close the session, when you go back in it has reverted back to a pattern trigger. It doesn't affect child triggers.

EDIT: When I changed it back to a GSL trigger, it doesn't work at all. I have to create a new trigger for it to work.

I do like 10 edits a post. Just changed the Subject to be more specific.
Reply with quote
slicertool
Magician


Joined: 09 Oct 2003
Posts: 459
Location: USA

PostPosted: Sat Sep 23, 2006 6:01 am   
 
Confirmed, it's doing the same thing to my oninput triggers.

Addendum: When I change them back after reloading, they still don't appear to be firing even after doing some changes to the code to force it to update the database.
_________________
Ichthus on SWmud: http://www.swmud.org/
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat Sep 23, 2006 6:13 am   
 
Hmm, this is a wierd one. If anyone still has v1.06, let me know if it had the same problem. Otherwise I'll check it myself tomorrow. Just wondering if this bug was in 1.06 or if it's the result of something I did in 1.07.
Reply with quote
slicertool
Magician


Joined: 09 Oct 2003
Posts: 459
Location: USA

PostPosted: Sat Sep 23, 2006 7:02 am   
 
from a quick check, it does not appear to be doing that in 1.06.

in 1.06:
1) I created an oninput trigger
2) checked settings to make sure it was there and configured properly
3) closed everything and exited cmud
4) opened cmud and selected appropriate session
5) checked settings and it was still set to command input.

it appears a fix for 1.07 broke it.
_________________
Ichthus on SWmud: http://www.swmud.org/
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat Sep 23, 2006 4:46 pm   
 
Hmm, I saw something that might be related to this. One of my triggers suddenly stopped working. When debugging this, I found that the Trigger on Newline option had somehow gotten turned off for the trigger. I don't know how this happened, but it prevented the trigger from firing.

So, if you run into triggers that stop working, check the Options tab and see if any of the options have changed. That might help me figure out what is going on with this wierd bug.
Reply with quote
asira
Beginner


Joined: 24 Jun 2002
Posts: 24
Location: United Kingdom

PostPosted: Sun Sep 24, 2006 10:13 am   
 
I've had my autolog triggers stop working because the trigger on prompt has been removed, and other triggers have had the regex option removed, but these all seem to work as long as I put the appropriate option back.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Tue Sep 26, 2006 9:46 pm   
 
OK, this turned out to be a pretty serious bug. Basically, *any* setting is getting it's options reset in v1.07. Not just triggers, but buttons, classes, etc. It was a side effect of one of the performance tweaks that I made in 1.07 and causes CMUD to not fetch the current data from the active database buffer in some situations. This could have all sorts of side effects.

You'll probably see 1.08 a bit earlier than expected this week to fix this.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net