2019-02-16 13:33 EST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001961FSSCPFREDpublic2010-05-19 02:07
Assigned ToFSO 4 
Product Version3.6.11 
Target VersionFixed in Version 
Summary0001961: Reordering events can cause is-event-true and possibly other sexps to reference wrong event.
DescriptionI think this one goes clear back to retail but I finally figured out how to reproduce it reliably. These are the steps I took

-Place ship in FRED
-open event editor and add 2 events (I named them test and test2)
-close event editor
-edit departure cue of the ship to is-event-true test2 (or whatever the second one is)
-change ship back to player ship or exit ship editor
-open event editor
-add new event (don't even have to rename this one)
-drag it ontop of the first event so it falls to the second position
-click chain (although this seems to be optional as I left it out in one test)
-exit event editor
-go back to the ship with the departure cue in the ship editor
-it will now say is-event-true new event

I have seen other weird stuff like this when dealing with the first event in the list but this is the only one I have confirmed.
Additional Information3.6.11 Kara's Diaspora build from 7/7/09 but I'm pretty positive this dates clear back to retail.
TagsNo tags attached.
Attached Files

related to 0002088closedFSO 4 FSSCP is-event-true-delay & chained bug 
related to 0002268closedFSO 4 wxFRED Moving Events around causes conditionals to loose Event's name. 



Tolwyn (reporter)

Use notepad to move events around.


Goober5000 (administrator)

Agreed, this is a retail problem.

Although it's clearly a bug, I'm not really sure how to go about fixing it. Assigning it to FSO 4 for now, as it'll hopefully get reworked in wxFRED.

-Issue History
Date Modified Username Field Change
2009-07-12 01:41 FUBAR-BDHR New Issue
2009-07-13 04:27 Tolwyn Note Added: 0011082
2009-10-01 11:24 Goober5000 Note Added: 0011204
2009-10-01 11:24 Goober5000 Assigned To => FSO 4
2009-10-01 11:24 Goober5000 Status new => assigned
2010-01-15 05:41 portej05 Relationship added related to 0002088
2010-05-19 02:07 Goober5000 Status assigned => closed
2010-05-19 02:07 Goober5000 Resolution open => suspended
2010-11-22 05:09 Goober5000 Relationship added related to 0002268
+Issue History