|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002088||FSSCP||FRED||public||2010-01-10 03:07||2012-07-03 01:14|
|Assigned To||FSO 4|
|Target Version||Fixed in Version|
|Summary||0002088: is-event-true-delay & chained bug|
|Description||I've discovered a random bug associated to is-event-true-delay and chained.|
If your event tree has sexps that use is-event-true-delay and sexps that are chained, adding sexps and reordering sexp tree might cause is-event-true-delay to use sexp that was previously in the same place as the original sexp.
For example, you have a sexp called "breaking point" that is fifth sexp in the event tree. You add a new sexp called "delay" and place it to fifth, making "breaking point" sexp now sixth sexp in the tree. If the tree also has chained sexps, this confuses sexps that use is-event-true-delay and there's high chance they now point to "delay" sexp, which is the fifth sexp in the tree, instead of the original sexp that is now sixth.
Unfortunately I cannot reproduce this bug reliably. I'm probably missing something. In any case, I classify this as a major bug because this can really break missions if fredder is not careful.
|Tags||No tags attached.|
|This seems to be duplicate of 1961|
|2010-01-10 03:07||Fury||New Issue|
|2010-01-15 05:38||Fury||Note Added: 0011523|
|2010-01-15 05:41||portej05||Relationship added||related to 0001961|
|2012-07-03 01:14||Goober5000||Note Added: 0013808|
|2012-07-03 01:14||Goober5000||Assigned To||=> FSO 4|
|2012-07-03 01:14||Goober5000||Status||new => closed|
|2012-07-03 01:14||Goober5000||Resolution||open => suspended|