Change Details

Queue any waypoint after a "DMISSSED" waypoint and attempt to skip it via waypoint-trigger activation or via scripting commands, neither will result in proper operation. In particular, using setCurrentWaypoint causes the "DISMISSED" waypoint to appear to have completed (it's onActivation gets called) though no subsequent action is taken.

Queue any waypoint after a "DISMISSED" waypoint and attempt to skip it via waypoint-trigger activation or via scripting commands, neither will result in proper operation. In particular, using setCurrentWaypoint causes the "DISMISSED" waypoint to appear to have completed (it's onActivation gets called) though no subsequent action is taken.

Queue any waypoint after a "DMIS"DISMISSED" waypoint and attempt to skip it via waypoint-trigger activation or via scripting commands, neither will result in proper operation. In particular, using setCurrentWaypoint causes the "DISMISSED" waypoint to appear to have completed (it's onActivation gets called) though no subsequent action is taken.