Stormy_Waters: Reading over the posts since finding out about this.
Really interested in the mission goals and mission state problems you were running through back in September. Looked through the rest of the posts and couldn't see an update.
Have you had any progress on this? I'd be really interested in figuring out a solution for this.
We are already at a much better state than original X-Wing ever was concerning the detection of uncompletable goals.
Basically, we detect failed goals at a first depth of dependency.
So, for example, if shuttle Hasti needs to complete mission and it is destroyed, then we detect that as mission failed.
If shuttle Epsilon needs to be boarded and it escapes or it destroyed, we detect that as mission failed.
However, we don't yet detect as mission failed when another object the goal depends of, but not the goal itself, is in a state that leads to an uncompletable mission.
For example, if shuttle Hasti arrives only after identifying a container, but the container is destroyed before it being identified. Even when the container itself doesn't have any goal attached to it, Hasti depends on it for even arriving at the mission. We cannot detect that yet, but I think it shouldn't happen so often.
In TIE Fighter and later games, the mission designers just made sure that all involved objects had a goal attached.
Detecting deep graphs of dependency is something that I will leave for later, as polishing.