Sectorgame

I have two directives in a mission I'm working on:

DIR: Patrol
>>when
>>>>is-event-true-delay
>>>>>>Waypoints Finished
>>>>>>5
>>do-nothing

DIR: Maintain Stealth
>>when
>>>>and
>>>>>>not
>>>>>>>>is-event-true-delay
>>>>>>>>>>Afterburner Stealth Fail
>>>>>>not
>>>>>>>>is-event-true-delay
>>>>>>>>>>Weapons Stealth Fail
>>>>>>is-event-true-delay
>>>>>>>>Waypoints finished
>>>>>>>>4
>>do-nothing

Thing is, niether of these shows up on the directives list until after they've been completed. Which kind of defeats the purpose of making them objectives. What gives, are there only some types of requirements which will make them show up? Thing as, I think the patrol has shown up before though just once or maybe twice. I don't know what the deal is.

If directive 1 doesn't show up then directive 2 won't so it appears as if your problem is there. Why the 1st one isn't showing up is a mystery to me though.

Hmmn, instead I changed it such that the first waypoint, a nav buoy sits tight throughout the whole patrol and then only leaves when its finished. The directive is now to wait for buoy 1 to leave, so it should show up now I think . . .

Now I have do up the background for the mission, man I don't have the patience for that crap heheh.

Directives won't show if event-true-delay (or other event-related SEXPs, I think) is part of the condition for fulfilling the directive event.

Yeah what I would have done would be to set the directive to "waypoints done" rather than to the first event you posted, so that it would get completed by the check to see if you're near the last waypoint bouy. Though what you've done is hackish, it still has an event trigger something that triggers your directive.

I've noticed a lot of people tend to put directives seperately and thus end up with problems like this. I tend to stick my directives in with the rest of the mission logic. It's pretty easy to spot a directive in the events editor anyway what with it being coloured red and all

Well in that case, I'll probably just nuke the second directive. If the player wasn't reading the dialogue it's his own dumb fault anyway The in-flight chatter should be directive enough for what they should and should not do.