Source Code Project Mantis - FSSCP
View Issue Details
0002088FSSCPFREDpublic2010-01-10 03:072012-07-03 01:14
ReporterFury 
Assigned ToFSO 4 
PrioritynormalSeveritymajorReproducibilityrandom
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0002088: is-event-true-delay & chained bug
DescriptionI'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.
TagsNo tags attached.
related to 0001961closed FSO 4 Reordering events can cause is-event-true and possibly other sexps to reference wrong event. 
Attached Files

Notes
(0011523)
Fury   
2010-01-15 05:38   
This seems to be duplicate of 1961
(0013808)
Goober5000   
2012-07-03 01:14   
Yup.

Issue History
2010-01-10 03:07FuryNew Issue
2010-01-15 05:38FuryNote Added: 0011523
2010-01-15 05:41portej05Relationship addedrelated to 0001961
2012-07-03 01:14Goober5000Note Added: 0013808
2012-07-03 01:14Goober5000Assigned To => FSO 4
2012-07-03 01:14Goober5000Statusnew => closed
2012-07-03 01:14Goober5000Resolutionopen => suspended