♣_Spiritus_♣
Sep-21-2014, 19:54
So Im making some progress in this and figured I'd share my ideas to see if anyone can see problems. Sorry but I can't test these without the game so I figure I'd ask to make sure Im not going down wrong paths. Im not asking for people to test these just wondering if anyone can see any holes in them.
To "rescue" a downed pilot:
I set the trigger radius to as small as I can get it (around the area of the downed aircraft), but a plane can still fly through it to cause the trigger to fire. To get around this and thus forcing the plane to land and sit for X amount of time, I can add a "timeout" to that trigger. Does anyone see an issue with this workaround? I assume timeouts can work on triggers since they can delay submissions. Am I correct? If so, then if I add a timeout of 20 seconds, it would effectively make flying within that small of a radius impossible, thus forcing the rescue aircraft to land and taxi to the downed aircraft and wait.
I can use the same idea for returning to base and in the briefing take care of which field the plane has to return to. (If someone doesn't bother to read the briefing then thats on them when they don't get the mission success)
To add interest and hinder cheating from either side, I can create 10 different sub-missions which are the same but just change the location of the pilot and randomly pick which submission launches when any aircraft enters a huge radius based trigger.
The hurdles I can't seem to get past are the following:
1) Having the aircraft ID stored so whoever lands and picks up the pilot is the same one that can only fire the second trigger at the friendly airfield.
2) Only allowing Blennies to be the rescuing aircraft. Is there a type of aircraft line I can add to the trigger to only allow the trigger to fire if the proper plane passes through it? I feel if you can delay a trigger this shouldnt be an issue.
3) If the aircraft that rescues the pilot gets shot down going back home, how to reset the trigger to allow for more attempts.
4)Getting all of this to trigger a mission objective based trigger, thus helping to roll the map
If we can get something working for the above four issues I think I can have a working script for this element in December. :P
To "rescue" a downed pilot:
I set the trigger radius to as small as I can get it (around the area of the downed aircraft), but a plane can still fly through it to cause the trigger to fire. To get around this and thus forcing the plane to land and sit for X amount of time, I can add a "timeout" to that trigger. Does anyone see an issue with this workaround? I assume timeouts can work on triggers since they can delay submissions. Am I correct? If so, then if I add a timeout of 20 seconds, it would effectively make flying within that small of a radius impossible, thus forcing the rescue aircraft to land and taxi to the downed aircraft and wait.
I can use the same idea for returning to base and in the briefing take care of which field the plane has to return to. (If someone doesn't bother to read the briefing then thats on them when they don't get the mission success)
To add interest and hinder cheating from either side, I can create 10 different sub-missions which are the same but just change the location of the pilot and randomly pick which submission launches when any aircraft enters a huge radius based trigger.
The hurdles I can't seem to get past are the following:
1) Having the aircraft ID stored so whoever lands and picks up the pilot is the same one that can only fire the second trigger at the friendly airfield.
2) Only allowing Blennies to be the rescuing aircraft. Is there a type of aircraft line I can add to the trigger to only allow the trigger to fire if the proper plane passes through it? I feel if you can delay a trigger this shouldnt be an issue.
3) If the aircraft that rescues the pilot gets shot down going back home, how to reset the trigger to allow for more attempts.
4)Getting all of this to trigger a mission objective based trigger, thus helping to roll the map
If we can get something working for the above four issues I think I can have a working script for this element in December. :P