Wait a minute.... the Daskha BFReds unlock just shy of two minutes into the mission. Even if you disable the Daskha's engine subsystem, those two beam cannons should still engage and destroy the Warlock no matter what. Unless you have somehow managed to fully disable the Daskha while it's turning, which would be impressive to say the least.
Yes, that was what I did.
That said, I can fix this by slapping a ship-subsystem-guardian on the Daskha's engines.
You're being really creative, I must say. Glad you're testing this, because I never thought of that. OK, I've done two things then:
1. The Daskha is going to be forward beam-free even earlier (you have ~100 seconds, so just after the Daskha completes its turn).
2. I'm putting a guardian on all its subsystems until the beam cannons are destroyed.
AND, the only orders the player can now give the bombers is to destroy the target (i.e. you can't send them after subsystems anymore).
The only concievable way to have the Warlock survive the beginning of this mission now should be to kill the two beam cannons. I hope. Test it out now please.
That works, however I found another creative flaw.
I succeeded in the mission even though the lilith did arrive
.
I managed to destroy both lilith cruisers and win the mission.
How? Quite easy, just do not destroy the "Ragelam" and tell all forces to ignore it and chase the lilith instead. The guardian on the Warlock will protect it from the deathly beams and I have all time to destroy liliths and Parvati, then destroy "Ragelam" and win. Its nice that the mission still somehow works though ...
I think even the destroy order is too much as if I cannot send orders I cannot exploit the above thing as Zeta will destroy Magellan, no matter what ...
Suggestions would be:
clear-goals that you added is good, but please also add the goal to chase both cruisers just in the different orders (M,P; P,M) ...
Even better, directly add both goals to Zeta Wing:
+$AI Goals: ( goals ( ai-chase "Ragelam" 89 ) (ai-chase "Parvati" 89 ) )
And add goal to destroy comm node to Iota wing first:
+$AI Goals: ( goals ( ai-chase "Comm Node" 89 ) )
Then re-task iota as message suggests:
( has-arrived-delay 5 "Parvati" )
( clear-goals "Iota" )
( add-goal
"Iota"
( ai-chase "Parvati" 89 )
)
( add-goal
"Iota"
( ai-chase "Ragelam" 89 )
)
Name: <LGM> New Iota orders
Btw. I liked the "Alpha wing clear out the sentries." message before.
And one small fix still:
"Target the crystal subsystem" should be "core subsystem", which does matter for missiles ...
The last thing that was nerving me was that the secondary objective never gets fullfilled as there are always shivans that just jump out ...
Also sometimes intercept bombers turns red, when they depart ...
Okay, you could argue that you did not do your job if they are able to depart so long into the mission, but still I personally don't like this turning red or white still standing directives if fighters or bombers depart ...
This is a more general thing though ...
cu
Fabian
PS: Perhaps also add a ship-subsys-guardian-threshold on the Warlocks engine and comm as it could be possible that random bombs destroy it and then I guess the warlock might never come into beam range, but that is just speculation ...
